diff options
| author | Enno <Konfekt@users.noreply.github.com> | 2024-05-15 10:26:49 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-15 17:26:49 +0900 |
| commit | 0994d9c881f8380997b96bb0a4a7416b50bc2b0d (patch) | |
| tree | 4bd3fb766017d64dd355a6c31eb1dddd61845620 /src/util | |
| parent | 030428ba43671cf951712de41be6d3bfb84117c3 (diff) | |
Make :FZF work in Vim from Git Bash (#3798)
* make :FZF work in Vim from Git Bash
Despite its title 'Calling fzf#run with a list as source fail (n)vim is used from git bash' the issue in
https://github.com/junegunn/fzf/issues/3777
of running `:FZF` in Vim in Git Bash was apparently only fixed for Neovim in Git Bash on Windows 11, but not for Vim from Git Bash.
In view of this, replacing /C by ///C might be considered a universal fix.
This PR just proposes the patch in https://github.com/junegunn/fzf/issues/1983 that still seems open.
In view of the fourth item in the most recent 2.45.0 https://github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md#known-issues little seems to have changed regarding path conversion of arguments containing forward slashes
* prefer doubling slashed instead of generic env. var
If MSYS_NO_PATHCONV=1 is used, then all arguments are preserved, in particular possibly paths passed in s:command.
Therefore, only avoid converting `/C` from `cmd` to a path.
Diffstat (limited to 'src/util')
0 files changed, 0 insertions, 0 deletions