vim do not guess $HOME when unavailable

Ciaran McCreesh ciaranm at
Mon Jan 23 21:45:04 UTC 2006

On Mon, 23 Jan 2006 22:32:20 +0100 Bram Moolenaar <Bram at>
| > Although unfortunately, some of the Gnome stuff to which Vim links
| > ignores $HOME and only uses getpwuid, which means that the Vim build
| > process has to have write access to the real ~/.gnome2* when
| > generating the NLS things or running tests...
| That's weird.  I mean, how would you get the result from getpwuid()
| in a shell script (in a Makefile)?

Vim is invoked via the Makefile for various things, so if you're
building with --with-vim-name=gvim the Gnome code gets called.

| Also note that "~/.gnome2" is short for "$HOME/.gnome2".  At least,
| that's how I have aways seen it.  A simple test confirms it:

Sorry, should've been clearer. I mean that the real (from passwd) home
directory is used, and the environment variable is ignored.

| Perhaps it's better to consider the Gnome stuff to be the problem...

Probably, yes. I only noticed this because Gentoo builds are done in a
sandbox that disallows writes outside of the build directory, and the
usual workaround (setting ${HOME} to a temporary directory) weren't
working. No big deal, since we can selectively allow writes or just hack
the Makefile to make a buildvim -> gvim symlink and use that inside the
Makefile instead...

Ciaran McCreesh : Gentoo Developer (King of all Londinium)
Mail            : ciaranm at
Web             :

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the pkg-vim-maintainers mailing list