There are problems with newline characters in the output of Git commands.
When I do, let's say:
:G checkout <hash-commit>
Result should be something like this:
Unfortunately result is:
It happens from 9e5547484956e3e8016ab8447170d63ad58d7568 (tag: v9.2.0224). One commit before (no tag) de10c87bed5a79ed80f1bb428a391faefdff13c9 ("translation: Regenerate desktop files in runtime directory") such problem does not occur.
Initially I thought that maybe there is some problem with newline character in the command, but when I do:
:echo "foo\nbar" there is no problem at all.
Another affected fugitive functionality is log in preview window.
There is no problem with: :G log, but there is problem with :G! log.
Actually: :G! -p log solves this, but before that patch, -p was not needed.
Is this problem in fugitive, or in Vim? Vim patch changes something connected to terminal (term_start()).
I tried this in both Vim versions using my normal configuration and with --clean and effect is same.
There are problems with newline characters in the output of Git commands.
When I do, let's say:
:G checkout <hash-commit>Result should be something like this:
Unfortunately result is:
It happens from
9e5547484956e3e8016ab8447170d63ad58d7568(tag: v9.2.0224). One commit before (no tag)de10c87bed5a79ed80f1bb428a391faefdff13c9("translation: Regenerate desktop files in runtime directory") such problem does not occur.Initially I thought that maybe there is some problem with newline character in the command, but when I do:
:echo "foo\nbar"there is no problem at all.Another affected fugitive functionality is log in preview window.
There is no problem with:
:G log, but there is problem with:G! log.Actually:
:G! -p logsolves this, but before that patch,-pwas not needed.Is this problem in fugitive, or in Vim? Vim patch changes something connected to terminal (
term_start()).I tried this in both Vim versions using my normal configuration and with
--cleanand effect is same.