commit 94bc89da0fe7083cfda9c1585f3fafb106692769 (tree)
parent 222c9ccbc6eec0fee4ab218b0d0bc13d985bfb7c
Author: Tim Pope <code@tpope.net>
Date: Sat, 10 Apr 2021 21:32:05 -0400
Don't use pty on win32unix
This appears to work fine in some setups, but has the same problems
as regular win32 in others. Most notably, for it to work properly with
the Vim included with Git for Windows, the experimental pseudo console
support must not be enabled. Lacking a method to distinguish between
the two cases, I see no better option than disabling it on all win32unix
installations.
Closes https://github.com/tpope/vim-fugitive/issues/1726
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/autoload/fugitive.vim b/autoload/fugitive.vim
@@ -2883,7 +2883,7 @@ function! fugitive#Command(line1, line2, range, bang, mods, arg) abort
call extend(env, {'COLUMNS': '' . &columns - 1}, 'keep')
endif
if s:RunJobs() && pager isnot# 1
- let state.pty = get(g:, 'fugitive_pty', has('unix') && (has('patch-8.0.0744') || has('nvim')))
+ let state.pty = get(g:, 'fugitive_pty', has('unix') && !has('win32unix') && (has('patch-8.0.0744') || has('nvim')))
if !state.pty
let args = s:AskPassArgs(dir) + args
endif