-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
1.21 broke Linux EOL in code editor #28097
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
Comments
That should not be the behaviour I tested. Do you have a As per my current understanding, the only way you get CRLF is when you have a .editorconfig specifying CRLF for the file or when the file is already predominantly in CRLF. All other cases should get you LF. |
Interesting, so Monaco seems to use OS defaults for files without a dominant ending. I think we should default it to |
) Backport go-gitea#28101 by @lng2020 Reverts go-gitea#27141 close go-gitea#28097 Co-authored-by: Nanguan Lin <[email protected]> (cherry picked from commit a2314ca)
Description
Updated to 1.21 and now any change via web editor always use Windows EOL, quite possibly because the browser itself runs in a Windows PC.
The stupid part is the editor itself successfully detected these are bash scripts, which must be Linux!
I can't find any documentation on how to permanently use Linux EOL so now I'm stuck.
Tried revert back to 1.20 and of course gitea blocked it too.
Gitea Version
1.21
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Gitea docker on Ubuntu.
Browser access on Windows PC.
Database
None
The text was updated successfully, but these errors were encountered: