On new plugin install, display gets stuck on "Cloning into..." #340
Comments
|
I am also experiencing the same issue running neovim. The following is where I get stuck in the installation process: |
|
@sts10 & @kennykaye I just want to confirm, you are in fact fully starting neovim then doing a command like If that's the case then I'm not sure what the issue is, ran some trials and neovim installers seems well behaved. for me on Linux @vheon Do you mind testing latest nvim on iterm just to see if its a mac issue? |
|
Not at my machine atm, but I can tell you I'm running OS X (Yosemite I'm pretty sure), and I do not have a Python installer, nor have I installed YouCompleteMe or the necessary Python stuff to do that. I just fire up I'll re-install to latest Neovim version and do this again tonight and see it if it's still happening. Thanks for your response! |
|
I was unable to reproduce the exact problem on nvim 0.1.0 on el capitan (
/cc @tarruda |
|
@junegunn can you see if this issue is related and helps? |
|
@tarruda Yes, it was related and I noticed that nvim installer needed update. Thanks! @sts10 @kennykaye I'm not completely sure if the fix above is related to the issue you're having (it's strange that the installer finished without updating the line starting with |
|
Just checked-- I've got OS X 10.10.5. Just now I ran Then, after firing up Neovim, I ran I started by commenting out I also confirmed that there was no longer a directory for matchit in Back to my After this I used Then, thinking maybe my test was flawed if Lastly (and this may help) I did the test using MacVim (version One thing to note is that these lines with "Cloning" start with a Also I have RVM installed. I know you have to install vim using system Ruby to use vim-plug, so I ran |
|
@sts10 Can you test again with this small patch for debugging? diff --git a/plug.vim b/plug.vim
index aacd369..c639238 100644
--- a/plug.vim
+++ b/plug.vim
@@ -903,6 +903,7 @@ function! s:job_handler(job_id, data, event) abort
endif
if a:event == 'stdout'
+ echom string([self.name, a:data])
let complete = empty(a:data[-1])
let lines = map(filter(a:data, 'len(v:val) > 0'), 'split(v:val, "[\r\n]")[-1]')
call extend(self.lines, lines)
|
|
Cool never done this before. I pasted Should I enter |
|
@sts10 Ah, sorry for not being obvious. Execute the command in the directory where plug.vim is located. Since you're testing neovim, |
|
Got it. Here's the result of running the patch line: And here is I'm happy to do the same process for |
|
@sts10 Thanks, but |
|
Sorry for the delay. I think I did it right and this is Note that before doing this I updated both Neovim and vim-plug. Also my |
|
@sts10 Then, what do you see when you manually execute the following clone command? git clone --depth 1 --no-single-branch --progress --recursive https://github.com/tmhedberg/matchit.git -b master /tmp/matchit |
|
Whoops-- accidentally closed the issue. I'll try that manual git command tonight if I have time. |
|
When I run I get: Sorry this is proving pesky-- hope it's not just something peculiar to my setup! |
|
So the git process does report the progress, but the lines are not passed to vim-plug as shown in the log you posted. This may not be something I can fix, it could be a Neovim issue. |
|
@sts10 Have you considered making an issue directly on neovim/neovim? They would probably be better able to support. Since the job isn't reporting the lines back, it seems likely the issue is with nvim. Still seems weird I've never had this happen though :/ |
|
I can submit an issue to neovim/neovim, but when I saw this issue also happen for me using MacVim, I figured it wasn't specific to neovim, right? |
|
@sts10 MacVim too eh? I missed that bit. Strange. Probably using the ruby installer in that case, means probably not nvim specific. Maybe some shell environmental messing up the capture. I'm assuming in all cases you've been running nvim/vim/MacVim on ITerm. Can you try another shell like bash or zsh? Ensure you isolate your own user configurations (i.e. .zshrc, .bash_aliases, .bashrc) from being sourced to eliminate that as an issue. Then try the GUI/terminal programs a few times to see if you can replicate. Otherwise, not sure what to say. :/ |
|
OK no worries. Thank you so much for your time! I'll keep poking around-- probably some weirdness in Feel free to close or keep open this issue. |
|
Also check if there's anything suspicious in your ~/.gitconfig. |
|
Maybe one of these |
|
I have exactly the same issue on Macvim. But after setting g:plug_threads to 1, the issue is resolved. |
|
I was having this problem on Macvim as well (OSX 10.8.5). The cloning message would remain and Macvim would crash. After setting g:plug_threads to 1, Macvim no longer crashes but the cloning message is still not cleared. |
|
Seems like I have a somewhat related problem. Each time I install a new plugin I see this:
Thankfully all works works well after a retry (R key):
|
|
Actually it's doesn't happen every time. https://github.com/tmhedberg/matchit was installed successfully. But it persists for some plugins, like https://github.com/mybuddymichael/vim-hexhighlight. |
|
@astyagun I can't reproduce the problem with the latest macvim. Do you have anything in your gitconfig that might affect the process? |
|
@junegunn it doesn't seem like it. I've tried cloning with git directly. And then tried reinstalling that plugin from Vim again.
Git alone worked fine, but the glitch is still present in Vim.
|
|
@astyagun What is the |
|
@junegunn It says, that it's the most recent version already. |
|
The |
|
@astyagun Okay, can you check the exit status ( |
|
@astyagun Hmm, then I have no clue, I can't reproduce no matter how many times I try. Please let me know if you find out the reason. |
|
I've spent some time debugging this behavior of Adding this code: diff --git a/plug.vim.orig b/plug.vim
index 7819a5a..75496db 100644
--- a/plug.vim.orig
+++ b/plug.vim
@@ -1150,6 +1150,7 @@ endfunction
function! s:job_exit_cb(self, data) abort
let a:self.running = 0
let a:self.error = a:data != 0
+ echom a:data
call s:reap(a:self.name)
call s:tick()
endfunctionI get the number 128 in |
|
Is this reproducible on |
|
Closing due to inactivity |
I'm running Neovim on iTerm2. Neovim --version gives
NVIM v0.1.0-144-gda9cf04 (compiled Nov 30 2015 20:54:54).When I add a new plugin to my symlinked
.vimrcand run:PlugInstallin Neovim, the new plugin installs successfully, but my displays ends up on the following:Which to me looks like vim-plug got hung up trying to clone vim-repeat.
After running this
:PlugInstallthere is now avim-repeatdirectory in my~/.vim/pluggeddirectory, and if I start Neovim again and run:PlugInstallagain, is says- vim-repeat: Already installed, so I'm assuming it actually installed. But the display saying "Cloning..." that first time is a bit concerning. It feels like it should display something like "Installed successfully" if/when the new plugin is installed?The text was updated successfully, but these errors were encountered: