Community
Participate
Working Groups
allow to disable this (very annoying) feature: "Instead of moving the caret back to the first character on the comment line, Home moves directly to start of the actual comment text on that line ." We want a smart home (beginning of text), but not that smart. (3.0m3)
Also allow to disabled this "caret-stop-at-word-in-indentifier" thing. It is very unconfortable and causes a lot of extra typing.
See Window>Preferences>Java>Editor>Typing>Smart cursor positioning in Java names.
This "enhancement" is pure evil and the sort of thing I would put in my enemy's text editor. I find myself cursing Eclipse several times a day because of it. This behavior has the following problems: 1. As I'm writing code, I'm constantly hitting Home to get to the first column of whatever indentation level I'm currently at, especially when I'm about to move up or down to different lines. This no longer works if I'm on a comment line. 2. I want to remove a line and replace it with something else. I used to hit Home, then Shift+End. I then start typing the new line which replaces the selected line leaving the previous line's indentation intact. On a comment line? Out of luck. 3. I want to fix the indentation of a line, probably because I copied code that uses different rules for tab vs. spaces or spaces per indentation. I used to hit Home, then Shift+Home to select all leading white space. I then press Tab the appropriate number of times. On a comment line? If I'm typing fast, I end up killing the comment characters and have to retype them. If I'm typing slow enough to realize that Home disobeyed, I have to stop, hit the left arrow three times to get to the start of the text, then continue pressing Shift+Home, and then some number of Tabs. Oh, wait, that doesn't work either, because the second Home ends up going *backwards* from the expected direction and I end up selecting and deleting *just* the comment characters. "Home" in a text editor should never mean "go somewhere in the *middle* of the text." This is the sort of "enhancement" that sounds good in theory, but just doesn't work in real life. It should be removed, or at least made a setting that defaults to "off."
Agree. I got also trapped by this. Especially it behaves different when on a line with /** ab<caret>c... (caret positioned in front of / and then toggling at 3 different positions) and * ab<caret>c... (caret positioned in front of first character then toggling between line start and first character)
Please assign the PR to me.
Are there any plans to do something with this before 3.0?
Time permitting, yes.
*** Bug 45245 has been marked as a duplicate of this bug. ***
Post 3.0 item.
Should'd it now be later enough? :)
Is it possible that this could be looked at for 3.2? If so, please reopen.
How much later does it need to be for this incident?
See also bug 72957, which would allow to configure this.
*** This bug has been marked as a duplicate of 72957 ***
