On Sat, 6 Nov 2010, ZyX wrote:
Reply to message «Re: 7.3 missing File Browser ??»,
sent 19:15:40 06 November 2010, Saturday
by Benjamin R. Haskell:
It shows that netrw is present in the source directory. After
building Vim `./configure ; make`, you should install it into a
different directory via `make install`. If you're not doing that,
you should; most build tools aren't written to support installation
into the source directory. If I try running `vim` from the source
directory without the `make install` step, it can't find its runtime
files (because it's looking for them in the directory where they'd be
installed). And it comes back with the same "is a directory" error.
If you did run the `make install` step, check instead where Vim was
installed, not your source directory.
I do not install vim anywhere and everything works fine. In order to
have it working without installing anywhere I set up an alias:
alias VimBeta="VIMRUNTIME=$HOME/tmp/vim/vim/runtime $HOME/tmp/vim/vim/src/vim"
Mercurial vim repository was cloned into $HOME/tmp/vim/vim and
everything works fine, so do not listen these people.
Just because you *can* do that doesn't mean you should. This is bad
advice, especially if you want to do any development on Vim. It's bad
for the same reason modifying files under VIMRUNTIME is bad: there are
cleaner mechanisms for making local customizations. And it's bad from a
development standpoint because you end up with modified files in the
source directory that the version control system doesn't know *should*
be modified. Both of these can cause problems when you update your
source files (unless you immediately rebuild).
In general, version control systems (in this case Mercurial) and build
systems (in this case autotools) aren't set up to cleanly handle the
case where source, build, and installation directories are the same.
Much better is to simply specify a prefix argument when you run
`configure`, e.g.:
./configure --prefix=$HOME/myvim --whatever-other-features
If you specify a directory to which you can write files, you don't need
root privileges for `make install`.
Also, I'm not saying this is some horrible, forbidden thing for you
(ZyX) to do. You obviously know what you're doing, based on your list
posts here and in vim-dev. I'm just pointing out that it's a bad thing
to suggest in general, because it adds another layer of complexity to
the checkout/build/install process.
--
Best,
Ben
--
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
