I like vim-packager better than minpac because of its more useful feedback during install and update operations.

It would be nice in my use case to have an equivalent to vim-plug's PlugSnapshot command, which writes a vim buffer with the current plugins and their commit IDs, like so:

" Generated by vim-plug
" Mon 26 Sep 2022 02:36:23 PM MDT
" :source this file in vim to restore the snapshot
" or execute: vim -S snapshot.vim

silent! let g:plugs['base16-vim'].commit = '3be3cd82cd31acfcab9a41bad853d9c68d30478d'
silent! let g:plugs['fzf'].commit = '731daf0f37bcaa45ba6ec6f67f716a76c291ad35'
silent! let g:plugs['fzf.vim'].commit = '9ceac718026fd39498d95ff04fa04d3e40c465d7'
silent! let g:plugs['vim-fugitive'].commit = 'dd8107cabf5fe85df94d5eedcae52415e543f208'
silent! let g:plugs['vim-mkbuild'].commit = '8d497467bb03397587c1ae6364afb56542164484'
silent! let g:plugs['vim-sensible'].commit = '8985da7669bbd73afce85ef0e4a3e1ce2e488595'

PlugUpdate!

I write this to a file that I keep alongside vimrc in my dotfiles.git. If I ever update plugins and things break, I can revert the update by running the above vimscript. With this scheme, I can also revert to any previous version of my vim setup and easily replicate a setup to another computer.

I've encountered an error while using the requires option with a list.

call a:packager.add('tools-life/taskwiki', {'requires': ['vimwiki/vimwiki', {'branch': 'dev'}]})

The above produces this error:

Error detected while processing function <SNR>3_run_cmd[2]..<SNR>2_packager_init[31]..2[1]..pa
ckager#plugin#new[1]..52[45]..3:                                                              
line   14:                                                                                    
E605: Exception not caught: Missing "requires" package name for taskwiki.                     
Error detected while processing function <SNR>3_run_cmd[2]..<SNR>2_packager_init[31]..2[1]..pa
ckager#plugin#new[1]..52:                                                                     
line   45:                                                                                    
E170: Missing :endfor

However, wrapping the 'vimwiki' list in another list works:

call a:packager.add('tools-life/taskwiki', {'requires': [['vimwiki/vimwiki', {'branch': 'dev'}]]})

When running packager#update(), I get this error for already installed packages.

First issue 🎉

Would you consider making keybindings configurable in some way? I use <C-j> and <C-k> to move between windows and having them mapped to move between plugins here always trips me up. I could use some timer hackery to removing the bindings after they're set but that doesn't feel great.

When I run :PackagerUpdate, I get this

Error detected while processing function packager#update[2]..284[19]..308[2]..305[18]..313:
line   13:
E730: using List as a String
E116: Invalid arguments for function get(split(l:ref, '/') -1, '')
Error detected while processing function packager#update[2]..284[19]..308:
line    2:
E714: List required

Also, the plugin window does not show many plugins, and shows an error:

Installing plugins 4 / 33
[======--------------------------------------------]

✗ eunuch — Error (exit status 2) - -abefhkmnptuvxBCHP or -o option
✓ snippets — Already up to date.
✓ matchup — Already up to date.
✓ nvim-yarp — Already up to date.

Here is my vimrc: https://github.com/greg0ire/dotvim/blob/master/vimrc

I have a few questions regarding the value for do in packager#add() function.

1. For nvim-gdb, it requires us to run install.sh script and :UpdateRemotePlugins command after install. Is it possible to combine the two in post update? I can't seem to get it right. For vim-plug, the following would work:

 Plug 'sakhnik/nvim-gdb', { 'do': ':!./install.sh \| UpdateRemotePlugins' }

2. It seems that post-install hooks default to bash command. So for deoplete call packager#add('Shougo/deoplete.nvim', {'do': ':UpdateRemotePlugins'}) works, while call packager#add('Shougo/deoplete.nvim', {'do': 'UpdateRemotePlugins'}) (note that there is no colon before the UpdateRemotePlugins) does not. Is the colon a must?

Thanks for this wonderful plugin. It seems to be even faster than vim-plug. Very promising!

Could add an option to disable default mappings?

Thanks for the awesome vim-packager! I switched recently from minpac (https://github.com/k-takata/minpac) to packager and am enjoying your plugin manager very much!

Nevertheless I'm having an issue: while running :PackagerUpdate I'm getting the following error:

Error detected while processing function <lambda>5[1]..35:
line   18:
E117: Unknown function: setbufline

But the updating process seems to work (at least the most recent repository versions are pulled). The other commands (:PackagerStatus, :PackagerInstall) seem to work fine.

The relevant section from my '~/.config/nvim/init.vim' are:

function! PackagerInit() abort
  packadd vim-packager
  call packager#init()
  call packager#add('kristijanhusak/vim-packager', { 'type': 'opt' })

  call packager#add('https://github.com/tpope/vim-vinegar')

  " ...

endfunction

command!        PackagerInstall call    PackagerInit() | call packager#install()
command! -bang  PackagerUpdate  call    PackagerInit() | call packager#update({ 'force_hooks': '<bang>' })
command!        PackagerClean   call    PackagerInit() | call packager#clean()
command!        PackagerStatus  call    PackagerInit() | call packager#status()

I'm using nvim v0.3.4 on a Debian-based OS (PureOS 9.0 amber).

Any ideas?

When I run ":call packager#status()", I always see all updates pulled since the initial installation, instead of only the last updates.
I found that it is solved by running "git checkout master" manually in the repositories of the plugins, but this is not ideal obvisouly.

VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 28 2018 01:38:28)
Included patches: 1-549

Latest version of vim-packager

git version 2.19.2

Not sure if this is an issue or it should work this way by design:

It works the same both for most recent neovim(stable and nightly) and vim(8.1.2410) on Windows 10.

Should it work this way?

I maintain a few git plugins myself. It's not documented, but I tried using [email protected]:... style URLs (as generated by GitHub when you select the 'Clone via SSH' option, and they worked! This is an incredibly useful resource for any plugin author, or anyone who plans to fork and modify a plugin.

I suggest documenting this in the README, perhaps with an example. I'd be happy to send in a pull req if you're interested.

Since commit 234249d I'm getting the following error when trying add my plugins to Packager using packager#add():

Error detected while processing function <SNR>15_packager_init[8]..packager#add[2]..17[1]..packager#plugin#new[1]..37[20]..48[1]..packager#utils#system_async[9]..packager#job#start[1]..<SNR>78_job_start:
line   30:
E903: Process failed to start: too many open files: "sh"

Commit 86be118 is the last one that works without this error. I have 41 plugins. I'm using Neovim on macOS 10.14.6.

If you are installing/updating plugins, move the cursor to another pane, the messages will be printed out in the pane where the cursor is, instead of the message window.

This wincmd p was added in commit 9ad1cd2 but I don't really understand why. Was this change intended? It looks like it might be left over from troubleshooting.

How do I update a single package(or few packages)? Many times I don't want to update all the packages.

Thank you for the great package manager. It's fast and simple and I just love it. I just have one problem when trying to install some plugins as an optional type. One such example is https://github.com/iamcco/markdown-preview.nvim which I added like this:

call packager#add('iamcco/markdown-preview.nvim', {'do': 'sh -c "cd app & yarn install"', 'type': 'opt'})

and then:

augroup packager_filetype
  autocmd!
  autocmd FileType markdown packadd markdown-preview
augroup END

but when I open a markdown file, all the commands for this plugin are missing. I had the same problem with few other plugins with optional type (but not will all) so maybe I am missing something.

through reasons i have yet known, certain plugins like lambdalisue/gina.vim still requires the following to be done manually 🤔

set runtimepath+=~/.config/nvim/pack/packager/start/gina.vim

otherwise it's not recognized

Thanks for the plugin, I think it's the best way to manage vim packages right now. I currently have a shim function that sets the plugins to {'type': 'opt'} by default. I was wondering if there is any interest in incorporating this into the plugin.

I generally only put filetype plugins in 'start', but maybe my usage is not common.

information

OS: Windows 10 1903 build 18362.535
Vim Version: Neovim v0.5.0-240-gbc879dd1f

init.vim

" Load packager only when you need it
function! PackagerInit() abort
  packadd vim-packager
  call packager#init()
  call packager#add('kristijanhusak/vim-packager', { 'type': 'opt' })
  call packager#add('easymotion/vim-easymotion', { 'type': 'opt' })
  call packager#add('neovim/nvim-lsp', { 'type': 'opt'})
endfunction

command! PackagerInstall call PackagerInit() | call packager#install()
command! -bang PackagerUpdate call PackagerInit() | call packager#update({ 'force_hooks': '<bang>' })
command! PackagerClean call PackagerInit() | call packager#clean()
command! PackagerStatus call PackagerInit() | call packager#status()

Detail info

When running :PackagerInstal in nvim, git clone info shows properly at first, and when clone finished (I do found plugins at ~\AppData\Local\nvim\pack\packager\opt) it shows that
Error (exit status 128) - fatal: not a git repository (or any of the parent directories): .git
It shows the same error when i run :PackagerUpdate command.

With the default call packager#init() when calling command :PackagerUpdate it freezes with status “9 of 60 updates”. I had to switch to {'jobs': 0} to get updates working (although, now the command seems unnervingly too fast, I am not sure whether the update actually happened).

Using neovim from the master branch of the github repo (commit bb24fec33 if it matters).

i use an 80 col terminal, so the side bar is hard to use; could we have an option for a bottom bar?

First of all, thank you for making this great plugin manager. I've been using minpac for a while. I like how minpac works, but I don't really like the interface. That's why I decided to try vim-packager.

While using it, I've noticed that when i changed the plugin type (changed from opt to start) and do an update, vim-packager re-cloning the plugin repo rather than moving the plugin directory from opt directory to start directory. So there are two directories which is basically the same.

For now, what I use is call packager#clean() | call packager#update(<args>) so that there's no double directories of the same plugin. Is there a way to move the plugin directory if the only thing that changed is the plugin type? Like, checking if the plugin directory already in start or opt first before doing the update.

Thank you.

For example , i want to lazy load a autocompletion plugin like nvim-compe on InsertEnter ,what should i do ?
I tried the following, but failed

if &compatible
	set nocompatible
endif

" Load packager only when you need it
function! PackagerInit() abort
	packadd vim-packager
	call packager#init()
	call packager#add('kristijanhusak/vim-packager', { 'type': 'opt' })
	" complete
	call packager#add('neovim/nvim-lspconfig')
	call packager#add('hrsh7th/nvim-compe', { 'type': 'opt' })
	" call packager#add('hrsh7th/nvim-compe')
	" call packager#add('hrsh7th/vim-vsnip-integ', {'requires': ['hrsh7th/vim-vsnip'] })

" ui
call packager#add('bagrat/vim-buffet', { 'type': 'opt' })

endfunction



" These commands are automatically added when using `packager#setup()`
command! -nargs=* -bar PackagerInstall call PackagerInit() | call packager#install(<args>)
command! -nargs=* -bar PackagerUpdate call PackagerInit() | call packager#update(<args>)
command! -bar PackagerClean call PackagerInit() | call packager#clean()
command! -bar PackagerStatus call PackagerInit() | call packager#status()

"Load plugins only for specific filetype
"Note that this should not be done for plugins that handle their loading using ftplugin file.
"More info in :help pack-add
" augroup packager_filetype
"   autocmd!
"   autocmd FileType javascript packadd vim-js-file-import
"   autocmd FileType go packadd vim-go
" augroup END

"Lazy load plugins with a mapping
" nnoremap <silent><Leader>ww :unmap <Leader>ww<BAR>packadd vimwiki<BAR>VimwikiIndex<CR>
set completeopt=menuone,noselect " required
augroup packager_envent
	autocmd!
	autocmd InsertEnter * packadd nvim-compe
	autocmd BufReadPre,BufNewFile * packadd vim-buffet
augroup END

let g:buffet_powerline_separators = 1
let g:buffet_left_trunc_icon = "\uf0a8"
let g:buffet_right_trunc_icon = "\uf0a9"

" compe
let g:compe = {}
let g:compe.enabled = v:true
let g:compe.autocomplete = v:true
let g:compe.debug = v:false
let g:compe.min_length = 0
let g:compe.preselect = 'enable'
let g:compe.throttle_time = 80
let g:compe.source_timeout = 200
let g:compe.incomplete_delay = 400
let g:compe.max_abbr_width = 100
let g:compe.max_kind_width = 100
let g:compe.max_menu_width = 100
let g:compe.documentation = v:true

let g:compe.source = {}
let g:compe.source.path = v:true
let g:compe.source.buffer = v:true
let g:compe.source.calc = v:false
let g:compe.source.nvim_lsp = v:true
let g:compe.source.nvim_lua = v:true
let g:compe.source.vsnip = v:true
highlight link CompeDocumentation NormalFloat
inoremap <silent><expr> <C-Space> compe#complete()
inoremap <silent><expr> <CR>      compe#confirm('<CR>')
inoremap <silent><expr> <C-e>     compe#close('<C-e>')
inoremap <silent><expr> <C-f>     compe#scroll({ 'delta': +4 })
inoremap <silent><expr> <C-d>     compe#scroll({ 'delta': -4 })
" lsp
lua require("lsp_config")

In addition , is there anyway to control a plugin config before/after a lazy load plugin ? Thanks.

vim-packager removes itself when running PackagerClean

I get this:
"Clean up [$MY_HOME]/.config/nvim/pack/packager/opt/vim-packager — Waiting for confirmation..."

This is the part of my config.

function! PackagerInit() abort
  packadd vim-packager
  call packager#init()

  call packager#add(...
endfunction

command! PackagerInstall call PackagerInit() | call packager#install()
command! -bang PackagerUpdate call PackagerInit() | call packager#update({ 'force_hooks': '<bang>' })
command! PackagerClean call PackagerInit() | call packager#clean()
command! PackagerStatus call PackagerInit() | call packager#status()

Hi, this is good plugin with nice UI. I tried this plugin on my Linux server. When I run :call packager#update(), I am seeing Error (exit status 1) for every plugin I try to install. The full error is (using E):

usage: git submodule [--quiet] add [-b <branch>] [-f|--force] [--name <name>] [--reference <repository>] [--] <repository> [<path>]
   or: git submodule [--quiet] status [--cached] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] init [--] [<path>...]
   or: git submodule [--quiet] deinit [-f|--force] [--] <path>...
   or: git submodule [--quiet] update [--init] [--remote] [-N|--no-fetch] [-f|--force] [--checkout|--merge|--rebase] [--reference <re
pository>] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] summary [--cached|--files] [--summary-limit <n>] [commit] [--] [<path>...]
   or: git submodule [--quiet] foreach [--recursive] <command>
   or: git submodule [--quiet] sync [--recursive] [--] [<path>...]                                                                   

I suppose this is somehow related to git command, but I am not sure how to fix it. My git version (git --version): 2.7.4.

My minimal failing config:

packadd vim-packager
let site_path = stdpath('data') . '/site/pack/my_plugins'
call packager#init({'dir': site_path, 'jobs': 16})
call packager#add('prabirshrestha/vim-lsp')

Start with nvim -u minimal.vim and then :call packager#update(), and then I see the error message.

Information

OS: Ubuntu 18.04
Vim Version: Neovim 0.5-dev (nightly)

Commit responsible: "Use async command calls when possible"

I successfully bisected to this commit: 234249d

Command

call PackagerInit() | call packager#update({ 'force_hooks': '<bang>' })

Error

Error detected while processing function PackagerInit[168]..packager#add[2]..26[1]..packager#pl
ugin#new[1]..46[20]..57[1]..packager#utils#system_async[9]..packager#job#start[1]..<SNR>176_job
_start:
line   30:
E903: Process failed to start: too many open files: "sh"

Not an issue per se but an FYI that might suggest a code change.

Deciding if a URL supplied in a packager.add() call is a 'name/repo' for github or not may need to be expanded. Here's a couple of SSH based Git URLs that vim-packager currently misinterprets:

function! s:packager_init(packager) abort
  call a:packager.add('kristijanhusak/vim-packager', { 'type': 'opt' })
  ...
  call a:packager.add('ssh://proj.sporian.com:29418/~smckown/vim-mkbuild.git')
  call a:packager.add('repo.titaniummirror.com:vim-mkbuild.git')
  ...
  call plug#end()
endfunction

My quick and dirty solution is to assume that no valid GitHUb 'name/repo' URL will contain either '@' or ':'.

diff --git i/autoload/packager/plugin.vim w/autoload/packager/plugin.vim
index 73c6425..34040c7 100644
--- i/autoload/packager/plugin.vim
+++ w/autoload/packager/plugin.vim
@@ -27,7 +27,7 @@ function! s:plugin.new(name, opts, packager) abort
     let l:rtp = substitute(l:rtp, '[\\\/]', '__', 'g')
     let l:instance.rtp_dir = printf('%s__%s', l:instance.dir, l:rtp)
   endif
-  let l:instance.url = a:name =~? '^\(http\|git@\).*'
+  let l:instance.url = a:name =~? '\(@\|:\)'
         \ ? a:name
         \ : l:instance.local ? a:name : printf('https://github.com/%s', a:name)
   let l:instance.event_messages = []

Minpack have minpac#getpluglist and minpac#getpluginfo. In very convenient for scripting. Could you add a the same API?

Since vim-packager seems to share lots of things with minpac I assume it's having the same issue also k-takata/minpac#76

In the second init.vim setup example, there is a spelling error of PackagerUpdate

" These commands are automatically added when using packager#setup()
command! -nargs=* -bar PackagerInstall call PackagerInit() | call packager#install()
command! -nargs=* -bar ackagerUpdate call PackagerInit() | call packager#update()

I like the manager. Super light and works great. One question: Is there any way to control load order. For example vim-devicons must load before vim-startify for icons to work.

Thanks again!

This might not be a plugin issue, maybe it's more how my config is set up. But I hope I can find some pointers on how to fix this.

This is my current setup with minpac & plugins#init() is called in init.vim

This is the new setup with vim-packager as you can see nothing much changed, it's a drop-in replacement for minpac.

I'm facing an issue with this line which runs every time I open neovim. With minpac there is nearly no overhead & things are instantaneous but with vim-packager this takes a couple of seconds.

minpac

vim-packager

so it creates 2 symlinks :

• packager/start/name -> ~/plugin/name, which is fine
• ~/plugin/name/name -> ~/plugin/name, which is ... infinite ? :)

really cool pack manager, btw !