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
Hm... I'm a bit unsure about this one.
Imagine you have the following code block:
fnmain(){// epic commentlet a = 10;}
and you would like to fix the indentation by using >. What I'd do, is selecting the comment and the let line and press >.
Now, with your suggested behaviour, it would result into this:
fnmain(){// epic commentlet a = 10;}
Which is very likely not the wanted outcome.
Hm... maybe a new keybinding can be added where you need to press > + Alt which will only shift text within comments?
Maybe that case could also be addressed with the following heuristic: only use the new behavior when all selected lines are comments.
Then you could select both // epic comment and let a = 10; in your example, before pressing >. That would avoid the need for an override key. Incidentally, this would be consistent with the new behavior for o/O, where (as far as I know?) there isn't really an override key.
Love the latest release! One small tweak would help improve the experience around doc-comments. At the moment if I have something like (in Rust):
and I try to indent the second line with
>
, I getbut I actually want
Apologies if this has already been requested or if there is a simple way around this that I don't know about.
Thanks for helix, it's great!
The text was updated successfully, but these errors were encountered: