We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using gq to format a block of text inserts windows line endings (CRLF), even though the file is in unix encoding (LF).
gq
Expected behavior is to use the current line ending character.
Related issues: #621 #333
The text was updated successfully, but these errors were encountered:
I can reproduce this bug.
Sorry, something went wrong.
Other operations that attempt, but may fail, to use the correct line endings:
To clarify, this actually works correctly if the line endings are being strictly enforced by an editor config setting.
For example, if there is an applicable EditorConfig configuration file that says:
# Unix-style newlines with a newline ending every file [*] end_of_line = lf insert_final_newline = true
Then the following code will properly set: DefaultOptions.NewLineCharacterOptionId and as a result, VsVim EditorUtil.NewLine will return "\n":
DefaultOptions.NewLineCharacterOptionId
EditorUtil.NewLine
"\n"
ricksladkey
Successfully merging a pull request may close this issue.
Using
gq
to format a block of text inserts windows line endings (CRLF), even though the file is in unix encoding (LF).Expected behavior is to use the current line ending character.
Related issues: #621 #333
The text was updated successfully, but these errors were encountered: