Oggi ho scoperto che il mio .vimrc
non ha avuto effetto. Era ok poche ore fa.
Quando ho lanciato vim con $vim --plugin
, :scriptnames
non ho fatto eco a nulla: il .vimrc
file non era di provenienza. (Nota: è /etc/vimrc
stato rimosso per eseguire il debug di questo problema.)
Poi ho provato a google e ho trovato $VIMINIT
variabili sospette.
Ecco il valore di $VIMINIT
:
$ echo $VIMINIT
set number
Documentazione Vim su VIMINIT
:
c. Four places are searched for initializations. The first that exists
is used, the others are ignored. The $MYVIMRC environment variable is
set to the file that was first found, unless $MYVIMRC was already set.
- The environment variable VIMINIT (see also |compatible-default|) (*)
The value of $VIMINIT is used as an Ex command line.
- The user vimrc file(s):
"$HOME/.vimrc" (for Unix and OS/2) (*)
"s:.vimrc" (for Amiga) (*)
"home:.vimrc" (for Amiga) (*)
"$VIM/.vimrc" (for OS/2 and Amiga) (*)
"$HOME/_vimrc" (for MS-DOS and Win32) (*)
"$VIM/_vimrc" (for MS-DOS and Win32) (*)
Note: For Unix, OS/2 and Amiga, when ".vimrc" does not exist,
"_vimrc" is also tried, in case an MS-DOS compatible file
system is used. For MS-DOS and Win32 ".vimrc" is checked
after "_vimrc", in case long file names are used.
Note: For MS-DOS and Win32, "$HOME" is checked first. If no
"_vimrc" or ".vimrc" is found there, "$VIM" is tried.
See |$VIM| for when $VIM is not set.
- The environment variable EXINIT.
The value of $EXINIT is used as an Ex command line.
- The user exrc file(s). Same as for the user vimrc file, but with
"vimrc" replaced by "exrc". But only one of ".exrc" and "_exrc" is
used, depending on the system. And without the (*)!
Non sono riuscito a comprendere completamente la documentazione di VIM. Sembra che $VIMINIT
possa rovinare l'avvio di vim.
Cancella $VIMINIT
:
$ VIMINIT=
$ echo $VIMINIT
Il problema esiste ancora.
$VIMINIT
ha precedenti su qualsiasi.vimrc
file. E soddisfa la regola del primo arrivato, primo servito. Quindi sì,.vimrc
viene ignorato.