On 16/02/10 12:18, Jean Johner wrote:
On Feb 16, 11:25 am, Tony Mechelynck<[email protected]>
wrote:
in Insert mode, prefix gg or G or G<End> > with a Ctrl-O).>
Hi Tony,
I use Insert mode by default so that Ctrl-O gg represents 4 strokes to
go to top of file!
Ctrl-O G<End> is
also 4 strokes to go to end of file.
Moreover Ctrl-Home, Ctrl-End has become a reflex (this is the standard
for Windows applications).
Besides, the gnome machine on which I work has no gvim and the xterm
fonts are not nice (perhaps I could improve that).
Hm. Well, if your sysadmin plays deaf to your pleas for installing it,
and if you're willing to take the trouble, you should be able to compile
Vim (by setting the installdir to some subdir of your home directory if
you have no admin privileges) -- it isn't that hard, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm , and add the
line
export CONF_ARGS='--prefix=$HOME'
to the configuration script to be sourced by bash before you compile (as
described in my HowTo page linked above). There can be only one
$CONF_ARGS so if you need to pass to configure more than one argument
using it, use a space-separated list, for instance
export CONF_ARGS='--prefix=$HOME --with-vim-name=gvim'
The latter would give the newly-compiled executable the name "gvim",
install its binary in (IIRC) ~/bin and its runtime files (i.e. its
$VIMRUNTIME) in (IIUC) ~/share/vim/vim72/. Sourcing this same bash
script before any (one or more) invocations of the make utility for Vim
will make sure that "make config", "make", "make install", "make -C src
installruntime", etc., will use consistent configure settings, even if
(e.g. because the Makefile has been patched) make decides to restart
configure, maybe even run twice in succession (with Bram's Makefile, it
can happen).
However, this requires you to install the required headers (usually
contained in a -devel or -dev package) for compiling everything you
need, and if your admin isn't willing... well, OTOH maybe you could
compile and package Vim at home (my HowTo doesn't say how to package it
but IIUC the top-level Makefile describes the procedure and has the
targets for it, it ought to be easy), and then just unpack your homemade
.tar.gz into your $HOME directory on that other machine...
Happy to learn that you reproduce the fact that Home and Ctrl-Home are
synonymous with gnome terminal. Is it a choice or a bug? If it is not
a bug, is it possible to change this behaviour?
I don't know. Maybe you could search the Gnome bugzilla (
https://bugzilla.gnome.org/ ) to see if there is a bug report about it,
and if not, file one yourself. And until it's fixed, use konsole if you
have KDE and Gnome libraries on the same machine.
Thank you for your interest.
Best regards,
Jean Johner
Best regards,
Tony.
--
Take my word for it, the silliest woman can manage a clever man, but it
needs a very clever woman to manage a fool.
-- Kipling
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
