Helix doesn't respect Git CRLF-related settings

[nahuakang]

Summary

Hi Helix maintainers!

I have a Windows and a macOS machine. On the Windows machine I have the following Git setting per Git documentation's recommendation:

git config --global core.autocrlf true

On the macOS machine I have the following Git setting:

git config --global core.autocrlf input

Whichever default-line-ending I use doesn't seem to matter:

• Every time I check out a new commit written on the macOS machine on the Windows machine with Helix and simply press :w, it ends up in CRLF with the ^M on git diff.
• Every time I checkout a new commit written on the Windows machine on the macOS machine with Helix and simply press :w, it ends up in LF (basically re-writing the entire file).

The Git gutter also just shows all the changes.

This issue doesn't exist on neovim, Sublime Text, or VS Code on these machines.

Is this the expected behavior? I'd have expected that Helix would behave similarly but sadly it doesn't. And to be honest I really would have preferred to work on Helix but currently it's impossible to do so.

The old quick fix from 2022 doesn't work.

Thanks for your time to read!

Reproduction Steps

I tried this:

1. hx

I expected this to happen:

Instead, this happened:

Helix log

~/.cache/helix/helix.log

please provide a copy of `~/.cache/helix/helix.log` here if possible, you may need to redact some of the lines

Platform

macOS / Windows

Terminal Emulator

Windows Terminal / Ghostty

Installation Method

source / brew

Helix Version

helix 25.01.1 (e7ac2fc)

[RoloEdits]

Hmm, I have worked with all kinds of operating systems and with this setting it worked as I expected with helix.

Did the repos exist before you changed the global setting? You might need to re-normalize the files to update them with the changes.

Perhaps try to run just

git config core.autocrlf input

In the repo. If you don't have any active work, I think you might be able to just nuke the working area and then all the newlines will be "fixed"? I wish I remembered what I did myself to solve this, its been quite a while.