On 30/11/06, Tom Purl <[EMAIL PROTECTED]> wrote:
I'm trying to use Gvim on Windows from a USB thumbdrive. I found and
installed
the GvimPortable project (http://portablegvim.sourceforge.net/), and it works
pretty well.
[snip]
Using this custom directory structure, I hope to protect my custom
vimfiles directory when I upgrade GvimPortable (or any other app on my
thumbdrive).
[snip]
Does anyone know how to fix this?
I'm afraid I don't know anything about gvimportable, but I would
question the benefit of it. For quite a few years, I've had gvim on
my USB stick and I don't know what the benefit of having a "portable"
version is.
On my USB stick is a directory structure thus:
/vim
- /vim70
- /vimfiles
- _gvimrc
- _vimrc
vim70 is the standard vim directory, vimfiles is my vimfiles
directory. Running U:/vim/vim70/gvim70 automatically finds the
vimrc/gvimrc files and the vimfiles directory and upgrading is simply
a case of changing the vim70 directory. In practice, I have _vimrc
and _gvimrc in the format shown below and the real vimrc file in the
vimfiles directory. This allows me to have the entirety of vimfiles
in a subversion repository to keep my USB stick, windows machine
(C:\vim\vimfiles) and Linux PC (~/.vim) synchronised.
What does GvimPortable offer over this sort of arrangement?
Regards,
Al
P.S. If you are interested, I can zip up my U:\vim directory and send
you a copy...
My simple (but probably rather crude) _vimrc:
let s:vrc = globpath(&rtp, "vimrc")
if type(s:vrc) == type("")
exe "source " . s:vrc
elseif type(s:vrc) == type([])
exe "source " . s:vrc[0]
endif
