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
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
It would be nice for Windows users, if files could be saved with a "carriage return" character before the "line feed" character. I found out that .http has them, but .css and .js do not. While it doesn't bring much functionality to "Brackets" itself, I think it would be a nice adittion.
The text was updated successfully, but these errors were encountered:
@Rutakate97 Brackets will preserve whatever line endings the file already has, so it you open a file with CRLF (Windows-style) line endings, it should save the file with CRLF line endings too. But if your file already has LF line endings (Max/Linux-style), Brackets won't convert them to CRLF for you. (Someone could write an extension do let you convert it, though).
If you make a new file from scratch in Brackets, it should use whatever line endings are the default on your platform, meaning CRLF if you're on Windows. But due to bug #9179, new Untitled documents will have the wrong line endings on Windows for now. To work around that, you can use right-click > New in the file tree instead.
Closing, since I think that covers it -- but please reopen if you think you're seeing a different problem (e.g. if Brackets is erroneously changing an existing file's line endings).
It would be nice for Windows users, if files could be saved with a "carriage return" character before the "line feed" character. I found out that .http has them, but .css and .js do not. While it doesn't bring much functionality to "Brackets" itself, I think it would be a nice adittion.
The text was updated successfully, but these errors were encountered: