-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
/usr/share/nano/git.nanorc
uses wrong newlines in Git for Windows 2.24.1
#2429
Comments
This is strange. My local /usr/share/nano/git.nanorc has the same issue. The git.nanorc in git-extra was last modified almost 2 years ago, but the Build agent updated the checksum in pkgbuild 13 days ago. @dscho could you check for an accidental local change that caused this checksum to change in 3638691 and updated the git.nanorc in the git-sdk repos, but not the git.nanorc in build-extra/git-extra? |
Due to a switch to a redesigned Azure Pipeline that builds and publishes our MINGW packages, the `git-extra` package is now built from a checkout that uses the default `core.autoCRLF` setting of Git for Windows. As a consequence, all files that were not marked explicitly with LF-only line endings were changed to CR/LF line endings in the latest `git-extra` package, including `git.nanorc` (and Nano does not like that change, not one bit). Let's just simplify the entire setup and tell Git that all text files within `build-extra` are to have LF line endings. This addresses git-for-windows/git#2429 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Surely you did not mean 3638691, but instead git-for-windows/build-extra@3638691? I can suspect a reason: I switched to a new, more reliable (and most importantly: public) Azure Pipeline to build Now, my guess is that the And obviously I failed to inspect the resulting commits closely, and missed that change of checksums. I pushed some commits that (hopefully) fix this and cross my fingers that https://dev.azure.com/git-for-windows/git/_build/results?buildId=47247 will work. Last time it took 11 minutes to build and publish @ToadKing could I ask you to open a Git Bash as administrator in the meantime and convert the |
yes. That's absolutely what I meant. |
Yes, I've already converted the file and that fixes the issues for me. |
Unfortunately, the Pipeline failed a couple of times, and one of my attempts to fix it broke the final run, after the Pacman packages were published, so I had to fix things manually. The next snapshot should be fixed already. |
I just merged a PR, which kicked of a snapshot build; Once that is complete, can I ask you to test with the new snapshot? |
I've tried the snapshot installer |
|
I'm having the same issue. How to you convert the git.nanorc file? I tried using dos2unix but get a Permission denied error. Is the git.nanorc file the only one that has the problem? |
@bigguiness
I had the same issue and I didn't know dos2unix command. |
@bigguiness alternatively, use the latest snapshot. |
The startup file for GNU nano, which had been included with DOS line endings (and therefore upset `nano`) [is now included with Unix line endings again](git-for-windows/git#2429). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Setup
defaults?
to the issue you're seeing?
No
Details
Bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
No errors to appear.
The message
[ Mistakes in '/usr/share/nano/git.nanorc' ]
appears at the bottom of the nano screen. Upon exiting nano, the following is logged to the console:Upon inspecting the file, it appears it has Windows-style
\r\n
newlines instead of Unix-style\n
newlines. Changing them fixes the issue.The text was updated successfully, but these errors were encountered: