@gardar It's a mistake.
I want to use the version tag in pkgver but it only exists in release branch. In the master branch, git describe returns a very old version tag, so I should specify the branch to be described.
This package is already using release branch, so leave it blank should work.
But there is another package vim-coc-git which uses master branch to compile from source, I need to specify the branch to be described in that package.
Sorry it's my fault, I should do this in vim-coc-git instead of vim-coc-bin-git. It should be fixed now.
Pinned Comments
sainnhe commented on 2021-03-26 11:50 (UTC) (edited on 2023-01-31 13:06 (UTC) by sainnhe)
Note: Execute
:packadd coc.nvimto load coc.nvim.I created 4 packages for coc.nvim, you can install one of them according to your preference:
Note that the development of the release branch often lags behind the master branch.
For feature
workspace_didChangeWatchedFilesto work, you'll need to install watchman, see this wiki page for more information.Coc uses either
npmoryarnto install extensions, so if you want to install coc extensions using:CocInstallprovided by coc, you'll need to install one of them.The
:CocInstallcommand installs extensions to~/.config/cocthat are only available for current user. If you want to install the extensions to/usr/sharethat are available for all users, I created some packages for some popular extensions, you can consider to install them from AUR. By this way, you don't need to installnpmoryarn.Due to my lack of personal time, I only created the development versions of these packages with
-gitpostfix.In addition, I selected some extensions that I think are very basic, you can consider to install them: vim-coc-extras-meta-git
If you need an extension that is not in AUR currently, leave a comment here and I'll try to create a package for it when I have time.