One of the plugins I am using had its github repo removed.
Running PackerSync will now block nvim for minutes (or maybe even forever? I do not have the patience to find out;-), while it is trying to update the repository!
All plugins updated but the one where I can not find the repository anymore. There is a line at the top of the update window, which says Username for 'https://github.com' so git might be waiting for input? I can not find any way to interact with the window and type anything that would let me continue.
Any ideas? I had to kill nvim completely to get out again and that is not nice.
That's odd, this shouldn't happen anymore. Is your packer up-to-date? What version of Git are you on?
git version is 2.30.0.
PackerSync says (among other things):
鉁旓笍 wbthomason/packer.nvim: already up to date
馃寑 saadparwaiz1/vsnippets.nvim: pulling updates...
This is the use statement that draws in the blocking repo:
use {
'norcalli/snippets.nvim',
requires = {{
'saadparwaiz1/vsnippets.nvim',
requires = {
'one-harsh/vscode-cpp-snippets',
'cstrap/python-snippets',
'polypus74/trusty_rusty_snippets',
},
}},
config = function()
local vsnippets = require('vsnippets')
local snippets = require('snippets')
snippets.snippets = {
c = vsnippets.c,
cpp = vsnippets.cpp,
python = vsnippets.python,
rust = vsnippets.rust,
}
vim.cmd [[ augroup snippets_aucmds ]]
vim.cmd [[ au InsertEnter * lua require('snippets').use_suggested_mappings() ]]
vim.cmd [[ augroup END ]]
end,
} -- snippets
Just to double-check, could you manually confirm your packer commit?
Also, what OS are you on? Git 2.30 should hypothetically be recent enough that the fix in #91 should apply.
I am on Arch Linux (fresh install from end of Januar). Git is at version 2.30.0, which seems to be current at this time. Nvim is a nightly snapshot from just now(TM).
packer.nvim is at commit c5b7f23e0b406767c1918d6888962fdb97f95.
Running PackerSync still freezes with only saadparwaiz1/vsnippets.nvim repo not having a little checkbox. I can not find that repo on github anymore.
As a workaround, there exists the frozen key (which I'm now realizing got dropped from the docs at some point) which should cause a plugin to be skipped during updates.
I wonder if the frozen key could be a commit rather than a boolean that way you could specify what it should be frozen _as_
Or even, since branches are just refs to commits, somehow merged with branch? Did not try it but what if you set branch to some commit?
@akinsho: You can use the commit key for that.
I really need to find a better way to surface the various keys and what you can do with them...
Ah - I also should make commit skip even trying to pull if the required commit is already present. Right now, it pulls anyway (because that makes the overall logic cleaner), which is usually fine since we checkout the appropriate commit. However, that won't help in @hunger's case, since the pull is what hangs.
Thanks for the workaround! I just got rid of the plugin:-)