Bug 116938 - new shortcut for "Show Line Numbers" is enabled only in the currently opened source file
Summary: new shortcut for "Show Line Numbers" is enabled only in the currently opened ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: editor integration (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 127884 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-23 12:09 UTC by Vadym Krevs
Modified: 2008-08-23 22:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vadym Krevs 2005-11-23 12:09:11 UTC
Version:           3.3 (using KDE 3.5.0 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.13-15-smp

Open a C++ source file in a project, go to "Settings->Configure Shortcuts" and define F11 to be the shortcut for "Show Line Numbers". Hit F11 to display line numbers in the currently opened source file, once again to hide line numbers. Everything works as expected.

Now open a second source file and hit F11. Nothing happens. Go to "Settings->Configure Shortcuts", scroll to "Show Line Numbers" and, surprise, there is no shortcut defined at all.
Comment 1 Jens Dagerbo 2006-04-19 00:32:00 UTC
Can't reproduce. Works fine with KDE-3.5.2 and KDevelop-3.4 branch.
Comment 2 Vadym Krevs 2006-04-22 00:06:32 UTC
And still does not work for me on SuSE 10.0 with latest available SuSE-built KDE 3.5.2 and Kdevelop 3.3.2. 
Comment 3 Jens Dagerbo 2006-04-22 15:26:35 UTC
What UI mode do you have KDevelop set to?
Comment 4 Vadym Krevs 2006-04-23 17:12:04 UTC
IDEAl window mode. 

Other settings from the User Interface page:

Use Tabs: Always
Use Close on Hover: Yes
Toolview Tab Layout: Text and icons
Tabbed Browsing: all three checkboxes are checked.
Comment 5 Pieter Dumon 2006-05-04 15:44:01 UTC
I have the same problem (KDevelop 3.3.2, KDE 3.5.2).
Also, when you set the shortcut for "Show Line Numbers" and switch to yet another file, you have to set the shortcut again.
So, it appears as if the shortcut is enabled or disabled on a per-file basis.
Comment 6 Jens Dagerbo 2006-05-25 16:10:51 UTC
*** Bug 127884 has been marked as a duplicate of this bug. ***
Comment 7 Pieter Dumon 2006-06-09 13:38:07 UTC
Still the same problem with KDevelop 3.3.3, KDE 3.5.3
Comment 8 Andreas Pakulat 2007-01-14 04:17:10 UTC
This works for me in KDevelop 3.4, assuming fixed. If you can reproduce with 3.4, please re-open.
Comment 9 Dusan Zatkovsky 2007-10-11 09:50:53 UTC
Still not fixed! I am using self-compiled kdevelop 3.4.1 on debian lenny with kde 3.5.7. I have discovered that when I use for example F10 key, everything works fine ( it shows line numbers in any file by F10 key, it works after closing and re-opening kdevelop too ). But when I use F11 key, it shows line numbers only for currently opened file. It doesn't work on any other file.  There is _no_ shortcut set for "show line numbers" after re-opening shortcut settings in the same kdevelop session.
Comment 10 Andreas Pakulat 2007-10-11 10:12:23 UTC
Indeed this is still a problem in KDevelop3, however I'm not sure it'll be fixed. I don't know the kate-integration code, but it seems we have a separate katepart for each file and the changing of settings is not propagated to the other kateparts. I don't even know wether there's a possibility to do that.
Comment 11 Amilcar do Carmo Lucas 2007-10-11 11:51:27 UTC
We provide KDevelop 3.5.0 binary packages for Debian (and other Linux distros).
Why are you using a "self-compiled kdevelop 3.4.1 on debian" ?
Comment 12 Andreas Pakulat 2007-10-11 13:16:12 UTC
a) there are no lenny packages (aka debian testing) because the buildsystem doesn't support it
b) it doesn't matter, the same problem exists in 3.5.0
Comment 13 Amilcar do Carmo Lucas 2007-10-11 13:35:06 UTC
Apaku you are 100% correct.

But I need to know why people do not use the binaries that we provide. So that I can:
1) correct the reason why people do not use them (lack of information missing MD5sum, or whatever other reasons people might have)
2) If people do not find any problems with them, but still do not use them, then I might stop wasting my time doing them.
Comment 14 Vadym Krevs 2007-10-12 19:23:39 UTC
Hi Amilcar

I do use your binaries. However I almost invariably end up downloading the source rpm as well, patching the sources and rebuilding it - due to something being always broken :-(

Vadym
Comment 15 Andreas Pakulat 2007-12-01 01:28:26 UTC
Hmm, I can't reproduce this anymore.