Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47029 - [neovim] Does not use Vim's system runtimepath (/usr/share/vim/vimfiles)

Attached to Project: Community Packages
Opened by Daniel Hahler (blueyed) - Tuesday, 10 November 2015, 22:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 27 May 2016, 16:57 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

There are several packages, which install files to /usr/share/vim/vimfiles, e.g.

% pacman -Qo /usr/share/vim/vimfiles
/usr/share/vim/vimfiles/ is owned by cmake 3.3.2-3
/usr/share/vim/vimfiles/ is owned by docker 1:1.9.0-1
/usr/share/vim/vimfiles/ is owned by pacman 4.2.1-4
/usr/share/vim/vimfiles/ is owned by ragel 6.9-1
/usr/share/vim/vimfiles/ is owned by tmux 2.1-1
/usr/share/vim/vimfiles/ is owned by vim-runtime 7.4.884-1

Those are not picked up by Neovim, which does not have it in its &runtimepath by default.

I think that there should either be a symlink installed by Neovim and/or /usr/share/vim/vimfiles/ should be included in Neovim's &rtp, e.g. /usr/share/nvim/site => /usr/share/vim/vimfiles.

The other option, to change all existing packages to also install the files to Neovim's "site" path seems not very elegant.

There might be of course compatibility issues, but then it seems better to address those in a central place, given that Neovim is meant to be quite compatible to Vim.


% vim -u NONE --cmd 'echom &rtp'
/home/user/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim74,/usr/share/vim/vimfiles/after,/home/user/.vim/after

% nvim -u NONE --cmd 'echom &rtp'
/home/user/.config/nvim,/etc/xdg/nvim,/home/user/.local/share/nvim/site,/usr/local/share/nvim/site,/usr/share/nvim/site,/usr/share/nvim/runtime,/usr/share/nvim/site/after,/usr/local/share/nvim/site/after,/home/user/.local/share/nvim/site/after,/etc/xdg/nvim/after,/home/user/.config/nvim/after

Additional info:
* neovim-0.1.0-1-x86_64
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 27 May 2016, 16:57 GMT
Reason for closing:  Won't implement
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 18 November 2015, 05:05 GMT
I'm not sure putting a symlink there would be a proper thing to do. Frankly not sure what the best thing here is. Would appreciate more input on this.
Comment by Doug Newgard (Scimmia) - Wednesday, 18 November 2015, 05:33 GMT
I'm currently using 'set rtp^=/usr/share/vim/vimfiles' in ~/.config/nvim/init.vim; this could work in /etc/nvim/init.vim as well if you want it set by default.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 18 November 2015, 22:03 GMT
Maybe that should be the official suggestion we put in the wiki? I'm not sure a symlink would be well-behaved in all circumstances.
Comment by Miguel de Val-Borro (migueldvb) - Wednesday, 06 April 2016, 16:28 GMT
Adding 'set rtp^=/usr/share/vim/vimfiles/' in ~/.config/nvim/init.vim does not work for me.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 27 May 2016, 14:57 GMT
Can anyone get me up to speed here what the actual issue with this is?
Comment by Doug Newgard (Scimmia) - Friday, 27 May 2016, 16:04 GMT
The issue is that all of the vim addons, syntax definitions, etc install to a path that neovim doesn't look in.

Adding it to rtp did quit working a while ago, but it seems to work from git, so I'm thinking that is just an upstream bug. I haven't looked into it further.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 27 May 2016, 16:57 GMT
I decided to leave it at upstream's default which is not to make it look into that path. My reasoning is that I don't want to introduce unforeseen behavior. Doug, could you please add a section to the wiki instead that makes users aware of the path thing?

Loading...