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
Would be nice if the context indentation level would be maintained while editing multi-line strings.
For example:
Vscode
Helix
My guess is that Helix is using the current indent level of the surrounding function, instead of using the string's internal content indentation level.
NOTE: I tried with a new commit as well (4e86d1c), same behavior
Reproduction Steps
Create a multi-line string that have some indentation level, example:
fnmy_function(){let query = r#" SELECT id|<- cursor here FROM table"#}
If you try to add a newline with "open-below" (o), the indentation will match the "let" level instead of the "id".
What happens
fnmy_function(){let query = r#" SELECT id |<- here FROM table"#}
What's expected
fnmy_function(){let query = r#" SELECT id |<- here FROM table"#}
Platform
Linux
Terminal Emulator
alacritty 0.12.2 (9d9982df)
Helix Version
helix 23.05
The text was updated successfully, but these errors were encountered:
leandrobbraga
changed the title
Identation insde a string not aware of content context
Identation inside a multi-line string not aware of surrounding context
Oct 2, 2023
Summary
Would be nice if the context indentation level would be maintained while editing multi-line strings.
For example:
Vscode
Helix
My guess is that Helix is using the current indent level of the surrounding function, instead of using the string's internal content indentation level.
NOTE: I tried with a new commit as well (4e86d1c), same behavior
Reproduction Steps
Create a multi-line string that have some indentation level, example:
If you try to add a newline with "open-below" (
o
), the indentation will match the "let" level instead of the "id".What happens
What's expected
Platform
Linux
Terminal Emulator
alacritty 0.12.2 (9d9982df)
Helix Version
helix 23.05
The text was updated successfully, but these errors were encountered: