Benji Fisher wrote:
On Fri, May 19, 2006 at 12:38:26PM +0600, Sanjaya wrote:
In addition...

rpm -qa | grep vi gives ....

system-config-services-0.8.15-1
gtksourceview-1.1.0-4
device-mapper-1.00.19-2
vim-minimal-6.3.035-3
[...]

     As Gerald Lai already said, the problem is that you have only
vim-minimal installed.  Let's see:

$ rpm -qa | grep vim
vim-common-6.2.457-1
vim-enhanced-6.2.457-1
vim-minimal-6.2.457-1
vim-X11-6.2.457-1

(Currently running vim 7.0 compiled myself.)  You probably want to get
some other RPM's.

HTH                                     --Benji Fisher


... or to compile Vim yourself. On Unix, it isn't really hard -- and 6.3 is obsolete anyway (6.4 was "the latest release" until recently; now 7.0 has been released "for general use"):

- Check that you have "development" versions of all your library packages installed. Any package whose development version is not installed cannot be included into newly-compiled programs. - Get and untar the sources (into a separate "development" or "build" directory distinct from where you house your "production" version of Vim); I recommend getting all three of the Unix, Extra and Lang archives even if it's not actually necessary -- this way all patches will succeed. Unneeded source modules won't be compiled anyway.
- Get and apply the patches (aka bugfixes).
- Decide what features you want: I set them by setting environment variables rather than modifying the Makefile; and I set these variables by sourcing a homemade bash script so I can keep track of what I did -- and modify it (followed by cd src && make reconfig) if I don't get what I wanted, or if I change my mind about what I want.
- make (which invokes make config if it hasn't yet been done).
- maybe check that you got a working executable with the right version, patchlevel and featureset. (src/vim --version)
- make install
- Run "which vim" in the shell to make sure that the right version is invoked. Set soft links if needed, e.g. in /usr/local/bin or (for a local install) in ~/bin

If you need more detailed instructions, I can give them; but IMHO they belong on the vim-dev list rather than here.


Best regards,
Tony.

Reply via email to