New issue
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
Trim Final Newlines integrates poorly with EditorConfig for Windows files #94562
Comments
I don't know if my issue is associated with this issue (as I have the macOS version), but I had 3 I closed VS code. Then later, when I examined the files on the command line, they all seemed to end in a single newline character, so I re-opened the project in VS Code, thinking it had inserted carriage returns, and to my surprise, it displayed a single newline at the end of each file. I checked each file for the presence of carriage returns (using a perl one-liner matching Should I create a new issue for this or is this associated with this issue? |
Originally came in via contribution it seems: #33947 |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Overall VSCode does a decent job integrating with EditorConfig. Including the Trim Final Newlines setting once enabled.
However, where final EOLs are disabled (such as for .AHK and other Windows-centric files), then Trim Final Newlines fails to delete final EOLs. How can we make sure that VSCode respects more EditorConfig configurations?
In particular:
VSCode 1.43.2
Windows 10
The text was updated successfully, but these errors were encountered: