On Mon, Apr 4, 2011 at 9:01 PM, Oon-Ee Ng <ngoonee.talk@xxxxxxxxx> wrote: > I installed vim-peaksea from the AUR the other day and couldn't use > it, because it installed in /usr/share/vim/colors/peaksea.vim. This > seems a fairly standard directory, but its not in runtimepath on a > fresh install (AFAIK). > > Checked out some other vim colour-themes on the AUR, the majority seem > to install to the same location. Some choose /usr/share/vim/vim** > instead, but that breaks when vim updates. Perhaps > /usr/share/vim/vimfiles makes more sense (only found one PKGBUILD > using that so far). > > So what's the 'correct' behaviour? The vim split package doesn't seem > to do any patches affecting runtimepath, so probably I assume > runtimepath is an upstream default. In that case, should AUR packages > correct their location? > > Posting to arch-general because it overlaps and isn't solely an AUR issue. > plugins installed into $VIM/vimfiles works. i thought that's the correct place for plugins. /usr/share/vim/vimXX directory should only be used by vim packages that updates along with vim. that's my understanding of the vim directories.
