Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331361

Summary:	[KeyBindings] Make F1 a configurable key binding
Product:	[Eclipse Project] Platform	Reporter:	Frank Baxter <frbaxter>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	dariusz.luksza, pwebster, remy.suen, vincent.lorenzo
Version:	3.5.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	365166

Description Frank Baxter

2010-11-29 12:24:08 EST

Build Identifier: 20100218-1602

A long term Emacs user under Unix, I've grown accustomed to using F1 for my own macro.  I'm able to use this with Eclipse under Linux fine.  However, under Windows (tested under XP), I cannot use F1, it always brings up context sensitive help, which I have no use for at all.  In fact, I can't even use the Shift or Ctrl modifiers, I can only use Alt-F1 as a valid key binding.

Why can't this be customized as is every other key binding in Eclipse?  Under Windows I'd like to make Shift-F1 be context sensitive help to match Linux.

Essentially, I want my editor to work the same way on all platforms and not be tied to any bizarre OS policies.

Reproducible: Always

Steps to Reproduce:
1. Goto Window->Preferences->Keys and add a binding for F1.
2. Eclipse takes the binding fine.
3. Go back to Eclipse and try to use the new F1 binding.
4. Eclipse always brings up context sensitive help.
5. Repeat with ctrl and shift modifiers - same behavior.

Comment 1 Remy Suen

2010-11-29 12:41:03 EST

F1 generates an SWT.Help event on Windows. I think this is unavoidable. See also bug 26772.

SWT, please advise.

Comment 2 Paul Webster

2010-11-29 12:43:59 EST

See also  bug 241892, bug 141217, and bug 154727

PW

Comment 3 Paul Webster

2011-11-29 13:04:49 EST

*** Bug 365066 has been marked as a duplicate of this bug. ***

Comment 4 Vincent Lorenzo

2011-11-30 03:20:30 EST

Do you have a solution for this bug?

Comment 5 Lars Vogel

2019-11-27 07:19:52 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.

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.