-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid git submodules in Windows hanging on "Hit any key to close this window..." #606
Comments
Actually https://github.com/junegunn/vim-plug/blob/master/plug.vim#L791 Seems like it's not working on Windows, right? I'd like to see a pure Vim script solution to this rather than relying on python interface which is not guaranteed to be available. |
Oh I see. No on my official Windows Vim this still shows the prompt
I will be willing to experiment with fixing this later and I agree I also do as much as possible in VimScript 👍 |
@dezza did you make much progress on this? It would make unattended installations a lot smoother... |
@nzbart I opted for another solution (https://github.com/airblade/voom) I guess it's pretty easy once you find the offending line. |
@dezza thanks; something simple like voom sounds really good... unfortunately, it's not cross-platform, which I need it to be. |
It is for me since I utilize WSL for Windows (shell) and mac already has shell. |
Is this for GVim only? |
@junegunn I can fix this but I need |
@janlazo I believe we can safely replace the code of |
I'm plan on using a batchfile for this but it will take awhile. let g:_plug_bang = (s:is_win && has('gui_running') ? 'silent ' : '').'!'.escape(cmd, '#!%') |
If |
Close junegunn#606 Fix for GVim on Windows.
Close #606 Fix for GVim on Windows.
To make vim-plug completely unattended while installing plugins on Windows it should avoid the "Hit any key to close this window..." for repos with submodules by not using
!
syntax which is used in thes:bang(cmd, ...)
function used ins:update_finish()
Instead it could use the Python Command() class OR
silent !
but that is the unlikely solution - my guess is that there's a good reason it's not silent so you can verify it's not failing - so I guess the Python option is the best choice?Please advice if this could be changed so we can avoid the
cmd.exe
window awaiting ENTER on each submodule.I will submit a commit/pullrequest if you agree.
The text was updated successfully, but these errors were encountered: