Eclipse `Ctrl+Shift+C` commenting and tab levels

[noncom]

Eclipse IDE has the default shortcut Ctrl+Shift+C that comments either the selected lines or the current one. When working with Clojure code, the shortcut effectively places the ; comment maker at the beginning of the line. This leads to the situation when such comments break tabbing because the tab level of all lower lines is discarded and they auto-tab to column 0, right where there's the upper ; character.

So, it turns out that either 1) the Ctrl+Shift+C shortcut is mostly useless when dealing with Clojure code, which is a really pity miss, or 2) if I nevertheless use it, I am forced to do lots and lots of manual formatting which kind of defeats its purpose anyway.

Out of the top of my hat, I can propose two solutons: either 1) ignore ; characters of higher lines when reindenting lower lines, or 2) make Ctrl+Shift+C put the ; right before the form, at its correct indent, not at column 0.

UPDATE it may be of interest to see what Eclipse does with Java code edited in the same way and then formatted with Ctrl+Shift+F - it takes the liberty to reformat both the indentation and the amount of space between // and the first character of the following string.

[laurentpetit]

I have been musing about this when doing the feature. In my use cases, Ctrl+Shift+C is generally used to comment out "almost dead code" that I still want to survive as ghost code because I'm not sure I'll definitely kill it yet.
Thus in this use case, I like that it does not respect the indentation and starts grossly at the start of the line.
This helps identifying at a glimpse dead code, and is sufficiently distracting that it tends to make me decide its future faster than if it were just properly aligned with everything else.

Maybe I could add a rule that when finding the right indentation I should:

• either ignore comments at all, all the time? (some times comments span multiple lines on the right, and I don't want the next code to align with those either)
• ignore comments that are lower in indentation ?
• ignore comments starting at the first column ?

@cgrand @arichiardi Do you have any additional thoughts to share about this subject?

[noncom]

A nice find! Now I see and I must agree that in many occasions this shortcut is related to dead code and yes, I see some kind of a subliminal message within the action of it. However, when realizing this, I also realize the other point - I often use it to comment out certain lines, for example, in a complex let while editing and experimenting within the REPL. Such a process may well take from several seconds to a half an hour and this is where this destructive behavior is undesirable, since it hinders the readability and consequently the progress. When I finish, I just remove the comments (or leave some of them for a while if in doubt), so here again - potentially dead code. But this formatting gets in the way of the dynamic work process...

But yes, I can say it too - I often mark the potentially to-be-removed code with it, so I recognize what you're saying... So from your suggestions, I think point 1 is the best, since it covers the most usecases. I cannot imagine a time when I would want the code to align itself with comments at all...