Bug 66640 - [rulers][key binding] Wrong shortcut Ctrl+1 in vertical ruler context menu on non-error annotations
Summary: [rulers][key binding] Wrong shortcut Ctrl+1 in vertical ruler context menu on...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-11 05:21 EDT by Markus Keller CLA
Modified: 2020-01-25 04:39 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2004-06-11 05:21:38 EDT
200406110010

open context menu in vertical ruler over ...

- Breakpoint or manually created Task -> menu item "Go To Annotation   Ctrl+1":
does nothing, but Ctrl+1 invokes QuickFix

- Bookmark -> menu "Go To Annotation   Ctrl+1":
selects whole line, but Ctrl+1 invokes QuickFix

- Override Indicator -> menu "Open Super Implementation   Ctrl+1":
opens super implementation, but Ctrl+1 invokes QuickFix

=> Ctrl+1 should not be shown on the menu item for non-error annotations. Maybe
it should just never be shown, since it also doesn't tell the truth when the
context menu is opened on another line than the line with the caret.
Comment 1 Dani Megert CLA 2004-07-26 09:11:43 EDT
Reproducible in R3.0
Comment 2 Holger Klene CLA 2012-04-13 20:30:19 EDT
Still reproduceable with Eclipse 4.2M6 I20120315-1300
Comment 3 Stephan Herrmann CLA 2015-09-04 17:15:51 EDT
Still seen in HEAD after Neon M1.
Comment 4 Eclipse Genie CLA 2020-01-25 04:39:58 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.