Re: [arch-general] New vi/vim/gvim in testing requires intervention

[Magnus Therning]

Dan McGee wrote:

On Mon, May 11, 2009 at 8:40 PM, Dan McGee <dpmc...@gmail.com> wrote:

On Tue, May 5, 2009 at 2:22 AM, Tobias Kieslich <tob...@justdreams.de> wrote:

Hi,
Finally, the new vi* packages are up. There will be a little migration
pain. For optimal results, I recommend to "sudo rm /usr/bin/{view/rview}"
before you run "sudo pacman -Syu"

Any ideas?

dmc...@galway ~
$ vim .vimrc
Error detected while processing /home/dmcgee/.vimrc:
line   64:
E185: Cannot find color scheme inkpot
Press ENTER or type command to continue

dmc...@galway ~
$ locate inkpot
/usr/share/vim/colors/inkpot.vim

For reference, here is some of my .vimrc:

" GUI/NONGUI SETTINGS "
if has("gui_running")
       if has("gui_gtk2")
               set guifont=DejaVu\ Sans\ Mono\ 12
       endif
       colorscheme desert
       set columns=80 lines=40
else
       colorscheme inkpot
endif


And a quick guess, it looks like the new vim package puts its colors here:
/usr/share/vim/vim72/colors/

Any reason the old /usr/share/vim/ shouldn't be on the default runtimepath?

/M

--
Magnus Therning                        (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org          Jabber: magnus＠therning．org
http://therning.org/magnus         identi.ca|twitter: magthe

Looking at other distros it seems using /usr/share/vim/vimX is the place for system-wide configurations. Not saying that's right or wrong.

signature.asc
Description: OpenPGP digital signature