Community
Participate
Working Groups
Build Identifier: When I inspect the current key bindings, there is a "when" field that tells under which conditions a certain key binding is effective. "In windows" is cryptic as well as a lot of entries in the "category" column. To keep the list shorter, maybe rows that are identical except for the "when" fields should be collapsed to one row? Having a field that will read as a comma separated list for "when". Then the number of lines can be held down. The same can be done for the "category" column. And back to the point, cannot "in windows" be changed to something that I can understand? Reproducible: Always
(In reply to comment #0) > And back to the point, cannot "in windows" be changed to something that I can > understand? It's been like that for many years so I'm not sure we would suddenly change it. What are you suggesting?
(In reply to comment #1) > (In reply to comment #0) > > And back to the point, cannot "in windows" be changed to something that I can > > understand? > > It's been like that for many years so I'm not sure we would suddenly change it. > What are you suggesting? I was afraid that was the reason. The whole ecplise seems to be abandonware at first sight, because it never changes. "It has been like that for ages". I am suggesting that you remove the "in windows" when-entry and replace it with some more specific places, like the file explorer. For some reason, such a "when" entry is missing. But there are shortcuts that would only make sense in the file explorer. Like SVN Commit. Ok, it would make sense when editing source files as well. But it does only works in the "php explorer" that I use, because I work with PHP Development Tools. I understand that "in windows" means "not in a dialog". But only by researching. It it was called "everywhere except dialogs" it would give me the total clue. Btw, when I want to change the "when" entry for a keybinding, I get a drop down menu with them all, and "in windows" is duplicated.
There is a help page for the dialog which can be reached by using F1. I do agree that labels on the table are a bit cryptic. The problem is always finding a description that is both short and meaningful. As always, patches are welcome, with the caveat, as Remy said in the comment 1, that they have to work for both people familiar with the current state and newcomers.
The fact that you can press F1 is an excuse for everything. As well as the fact that it has "always been like this". Its not an opener for progress. If eclipse is changed to have meaningful names on things and people dont recognize some parts of it, there is still an F1 key, isnt it?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
