Community
Participate
Working Groups
Build Identifier: 20110916-0149 See http://stackoverflow.com/questions/3663015/change-hotkey-for-autocomplete-selection In Eclipse, the Enter key is the hotkey that selects an item from the Content Assist list. Tab might be a better selection hotkey since tab is not likely to be hit mid-line. Please add the ability to configure which key(s) select an item from Content Assist. Reproducible: Always
I don't understand your use case: You press CTRL+SPC and bring up the completion popup, and then instead of wanting to chose a proposal from there, you want to press enter to go to a new line. Why did you bring up the completion popup in the first place? If you brought it up by mistake you can always use ESC to close it and then press enter for new line.
For Java, Content Assist is configured to popup up when the user hits Control+Space or a period. If a user presses period and then after a few keystrokes hits enter, then autoselection kicks in. This may or may not be what the user wanted. In my case, I changed the "Auto activation triggers for Java" setting to be ".abcdefghijklmnopqrstuvwxyzABCDEFGHJIKLMNOPQURSTUVWXYZ". Now, Content Assist pops up all the time. It will prompt me with class names, variables, methods, templates and all sorts of things to make my coding faster. Most of the time I only have to type a couple of letters and then hit enter because it selected what I wanted. For example, when typing "ArrayList", all I have to type is "ArL" and hit enter. I don't have to hit Control+Space. I can fly through a complicated line of code using Content Assist every step of the way. The only problem I face is that if I hit Enter because I need to go to the next line, then Content Assist gets in the way. I would like to be able to assign other key(s) or key combination(s) to make a selection.
If the enhancement in Bug 101420 "auto-activation everywhere" is implemented, then this will be a very important feature.
(In reply to comment #2) > In my case, I changed the "Auto activation triggers for Java" setting to be > ".abcdefghijklmnopqrstuvwxyzABCDEFGHJIKLMNOPQURSTUVWXYZ". Ah. That explains it. Moving to Platform/Text for follow up on a key binding.
Workaround: You can also press 'Shift+Enter' to go to a new line when the content assist popup is open.
No plans to change this. 'Enter' is the natural key binding to accept a selection.
> 'Enter' is the natural key binding to accept a selection. I fully agree. The default settings should be left alone. However, this enhancement request isn't about changing the default settings for everyone. This enhancement request is to give users control over what keys Content Assist's autoselection is triggered. Eclipse already gives users control over what keys make Content Assist appear. This enhancement request simply extends the amount of control the user has.
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.
As far as I can tell, the user can not configure a different key to select an item from the Content Assist list.
This is a very legitimate ask and feature request. For me, it is The One thing that got me to leave Eclipse and move over to Intellij instead (even though it's a paid license)
This feature is still requested by a lot of people. It is hard to get used to Eclipse key schema if you can't redefine key/very frequent shortcuts. Is there a tiny chance that it will be reopened?
Still annoying end of 2021 as most IDEs use TAB for this function. The feature to define a custom key binding would be highly appreciated :)
Please reopen this. This is a logic feature request and expected from a lot of people.
(In reply to Minh Quan Pham from comment #13) > Please reopen this. This is a logic feature request and expected from a lot > of people. Please open a new issue in https://github.com/eclipse-platform/eclipse.platform.text
(In reply to Karsten Thoms from comment #14) > (In reply to Minh Quan Pham from comment #13) > > Please reopen this. This is a logic feature request and expected from a lot > > of people. > > Please open a new issue in > https://github.com/eclipse-platform/eclipse.platform.text Thanks. I just open new case in Github repo: https://github.com/eclipse-platform/eclipse.platform.text/issues/147
