Your message dated Mon, 13 Oct 2008 18:49:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#502111: Vim: cannot find colorscheme default [solved]
has caused the Debian Bug report #502111,
regarding Vim: cannot find colorscheme default [solved]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
502111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502111
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: vim
Version: 1:7.1.314-3+b1
Severity: minor
Kernel: 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 GNU/Linux
Vim claimed it could not find "coloscheme default".
AAMOF the very first line of /etc/vim/vimrc refers to "vim70"
------------- quote ---------
" Configuration file for vim
set
runtimepath=~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/addons,/usr/share/vim/vim70,/usr/share/vim/vimfiles,/usr/share/vim/addons/after,~/.vim/after
------------- unquote -------
whereas the correspondent dir was created as "vim71":
------------- quote -----
total 3
1 addons/ 1 registry/ 0 vimcurrent@ 0 vimrc@
0 gvimrc@ 1 vim71/ 0 vimfiles@
------------- unquote -----
so it'is very simple to correct the error.
Best regards,
Ennio
--
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that. )=(
Do something you aren't good at!" (as Henry Miller used to say) ]
--- End Message ---
--- Begin Message ---
On Mon, Oct 13, 2008 at 06:26:33PM +0200, Ennio Sr wrote:
> Vim claimed it could not find "coloscheme default".
> AAMOF the very first line of /etc/vim/vimrc refers to "vim70"
> ------------- quote ---------
> " Configuration file for vim
> set
> runtimepath=~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/addons,/usr/share/vim/vim70,/usr/share/vim/vimfiles,/usr/share/vim/addons/after,~/.vim/after
> ------------- unquote -------
That line hasn't been in /etc/vim/vimrc for over 2 years (as of
1:6.4+7.0g01-1). It looks like you ignored dpkg when it notified you
that there was a change to the vimrc and simply kept what you had at the
time.
You likely have a couple /etc/vim/vimrc.dpkg-* files laying around.
If one of them starts with the following lines
" All system-wide defaults are set in $VIMRUNTIME/debian.vim (usually just
" /usr/share/vim/vimcurrent/debian.vim) and sourced by the call to :runtime
" you can find below. If you wish to change any of those settings, you should
" do it in this file (/etc/vim/vimrc), since debian.vim will be overwritten
" everytime an upgrade of the vim packages is performed. It is recommended to
" make changes after sourcing debian.vim since it alters the value of the
" 'compatible' option.
then you should replace your current /etc/vim/vimrc with it (modulo any
local changes you may have made to your /etc/vim/vimrc).
If you don't have any of those .dpkg-* files around, the quick fix is to
purge, not just uninstall, your Vim packages (technically only
vim-common is needed, but everything else depends on it) and reinstall
them.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
