On 21/02/10 20:02, Tim Chase wrote:
Stjepan wrote:
Once you have the file(s), you can put them in the spell/
directory somewhere in the runtime path as mentioned at
:help spell-load
Thats crazy, I have installed Vim (Gvim) but when i look in
/hom/.vim or /home/gvim they are not here. Stil I can open Vi
and work with it. Strange.
You might look at your 'runtimepath' settings:
:set rtp?
to see where vim & gvim would look for the resource files. Usually there
are system-wide directories such as below (taken from my Debian box):
/home/tim/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,
/usr/share/vim/vim72,/usr/share/vim/vimfiles/after,
/var/lib/vim/addons/after,/home/tim/.vim/after
My system-wide spell directory is in /usr/share/vim/vim72/spell/ and my
local additions are in /home/tim/.vim/spell/
I don't know whether Vim maintains that directory (in which case I
wouldn't go dumping files in there), or if that's available for dumping
your own language files. Debian likely expects to have free reign over
most of those directories, but I'd expect that something like
/var/lib/vim/addons is reserved for local additions. Or you can add to
the 'rtp' setting in your system-wide vimrc to ensure that some other
location (such as /usr/local/share/vim72/) is in your 'rtp' and then
dump your spelling files in a spell/ directory there.
-tim
I guess I should have seen this earlier... but... well... it looks like
I'm not going to have an empty inbox any time soon :-/
The $VIMRUNTIME directory tree is _only_ for files distributed together
with Vim. Any upgrade or bugfix may change anything in that tree without
telling you, possibly overwriting or removing your changes, and at the
next point release (7.3) another $VIMRUNTIME directory will be created
from scratch (normally as $VIM/vim73/), losing any changes you might
have made.
The other 'runtimepath' directory trees (all of which have the same
structure) are for additional files not distributed together with Vim,
as follows, in the order in which they are searched (they don't need to
exist, unless you have something to put in them):
1) $HOME/.vim/ (Unix) or $HOME/vimfiles/ (Windows)
full-fledged scripts, helpfiles, etc., private to one user
2) $VIM/vimfiles/ (on all platforms)
full-fledged scripts, helpfiles, etc., system-wide (common to all users)
3) $VIMRUNTIME/
whatever comes with Vim -- DON'T CHANGE IT! -- and don't add, remove or
change anything in or under it at any depth
4) $VIM/vimfiles/after/
small system-wide tweaks to any of the above
5) $HOME/.vim/after (Unix) or $HOME/vimfiles/after/ (Windows)
small single-user tweaks to any of the above
The executables are normally "not too far" from $VIMRUNTIME: on Windows
vim.exe and/or gvim.exe are usually in $VIMRUNTIME itself; on Unix the
default $VIMRUNTIME for a Vim that you compile yourself (but not for one
compiled by your distro) is /usr/local/share/vim/vim72 (for version 7.2)
in which case the binary (and usually the ex, vi, view, gvimdiff, etc.
softlinks) will be in /usr/local/bin/ i.e. $VIM/../../bin/ or
$VIMRUNTIME/../../../bin/.
see :help 'runtimepath'
Best regards,
Tony.
--
Sex is the poor man's opera.
-- G. B. Shaw
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
To unsubscribe, reply using "remove me" as the subject.
