vim-fugitive icon indicating copy to clipboard operation
vim-fugitive copied to clipboard

Windows 10 "Hit any key to close this window"

Open harriott opened this issue 4 years ago • 5 comments

A while ago, Ggrep on Windows 10 worked exactly as on GNU/Linux, but then, for some time now, I get a command window named C:\Program Files (x86)\Vim\vim82\vimrun.exe:

C:\WINDOWS\system32\cmd.exe /c (git --no-pager grep -n --no-color --full-name --column -i searchterm ^>^"C:\Users\jnbh\AppData\Local\Temp\VIB5B0C.tmp^" 2^>^&1)
shell returned 1
Hit any key to close this window...

I've just tried with a stripped-down to nothing vimfiles but vim-fugitive, and still getting this. Would be nice to have this command window be automatically closed so users don't have their workflow interrupted by this.

harriott avatar May 22 '20 21:05 harriott

What is :set guioptions??

tpope avatar Mar 13 '21 08:03 tpope

guioptions=egrL

Including se go+! in my vimrc doesn't stop the undesirable launching of the command window.

harriott avatar Mar 24 '21 06:03 harriott

I could be mistaken but I believe this matches how Vim used to work: Built-ins like :grep and :make would give you a command window that you had to manually dismiss. Regardless of the history, unfortunately I'm not seeing an easy fix here. Moving off :! would resolve it, and that might happen one day, but that's a bit much to do on a whim.

tpope avatar Mar 24 '21 15:03 tpope

I can't quite see how your thoughts relate to this issue appearing recently for gVim on Windows 10, and already no ! in guioptions.

harriott avatar Mar 28 '21 13:03 harriott

I had spaced on that detail, but "appearing recently" and "I believe this matches how Vim used to work" relate perfectly.

Can you reproduce the old, correct behavior? Presumably by running an older version of Vim.

tpope avatar Mar 28 '21 14:03 tpope