Open injust opened 1 month ago
Just to add here what the linked "less" issue has, and might be related:
On Windows delta sets the console codepage to UTF8 even when stdout is not a tty, which causes issues when piped to other applications (because it restores the codepage when delta exits, but the other app doesn't know that).
So it might be a general delta issue where the terminal is initialized even when stdout is not a tty - but in such case it shouldn't touch the terminal state.
On Windows delta sets the console codepage to UTF8 even when stdout is not a tty, which causes issues when piped to other applications
Just to clarify: For my problem, stdout is a tty. I am not piping delta to less -- delta is running less by itself. So from delta's perspective, stdout is a tty.
Just to clarify: For my problem, stdout is a tty. I am not piping delta to less -- delta is running less by itself. So from delta's perspective, stdout is a tty.
Oh. But still, depending on how it's implemented, it might still be piping into less. But good point. I didn't realize it's not piped into less "externally".
It seems like there is a race condition between delta and less when setting the terminal raw mode. See details in https://github.com/gwsw/less/issues/579.
Raw diff output: