You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The enter key cannot be used to commit the auto-complete dialog in a JavaDoc style comment. Instead a newline is inserted. Outside of JavaDoc style comments enter works as expected. The tab key still works inside JavaDoc style comments.
With JavaDoc style comment, I mean this particular style to format comments:
/**
* example text
*/
Steps to reproduce
Open a new document.
Set the syntax to C.
Type SymbolWithAReallyLongName.
Go to a new line and type S.
Press ctrl+space to open the auto-complete window. (It should suggest SymbolWithAReallyLongName).
Press enter. (It should complete SymbolWithAReallyLongName).
Go to a new line and type /** S.
Press ctrl+space to open the auto-complete window. (It should suggest SymbolWithAReallyLongName).
All of these commands apply in the given situation. I assume the javadoc commands take precedence because they appear later in the "Default (Windows).sublime-keymap" file or maybe because they have a bigger / more specific context. It would be nice, if the docs explained how this works.
As a workaround the following commands can be inserted into the user's keymap file:
Description of the bug
The enter key cannot be used to commit the auto-complete dialog in a JavaDoc style comment. Instead a newline is inserted. Outside of JavaDoc style comments enter works as expected. The tab key still works inside JavaDoc style comments.
With JavaDoc style comment, I mean this particular style to format comments:
Steps to reproduce
SymbolWithAReallyLongName
.S
.ctrl+space
to open the auto-complete window. (It should suggestSymbolWithAReallyLongName
).enter
. (It should completeSymbolWithAReallyLongName
)./** S
.ctrl+space
to open the auto-complete window. (It should suggestSymbolWithAReallyLongName
).enter
.Expected behavior
The name is completed as before. Final output:
Actual behavior
A newline is inserted, respecting the comment formatting. Final output:
Sublime Text build number
4189
Operating system & version
Windows 11
(Linux) Desktop environment and/or window manager
No response
Additional information
I do have
"auto_complete": false
in my settings.This is caused by conflicting default keybindings:
All of these commands apply in the given situation. I assume the javadoc commands take precedence because they appear later in the "Default (Windows).sublime-keymap" file or maybe because they have a bigger / more specific context. It would be nice, if the docs explained how this works.
OpenGL context information
The text was updated successfully, but these errors were encountered: