Erich,
imapping is immediate, therefore it needs characters that are not likely to be
part
of normal text. Though useful, they are of limited numbers
and difficult to be remembered.
Perhaps I accept that annoying space after bQ and the like and after such a
construct
I space forward for have it
> Perhaps I accept that annoying space after bQ and the like [...]
You don't need to. Do ":help abbreviations" in vim, copy the
function Eatchar (which is given as an example there) to your
.vimrc, and then
:iabbr lQ \[lq]=Eatchar('\s')
:iabbr rQ \[rq]
(The last one assumes you always type
Am Thu, 28 Jan 2010 19:43:29 +0100 (CET)
schrieb Werner LEMBERG :
> > It's a simple pipeline.
>
> You are probably misunderstanding. I was wondering whether the
> internal pipeline in the groff binary (this is, how the -K and -s
> command line option interact) should be changed that way.
Sorry I
Tadziu,
This works like charm, thank you very much.
For the time being I take these two without trying to understand them, but
eventually I'll have to learn more about vim.
So far I only used the old vi subset, but vim seems to be so much more than
that.
There is a line after the Eatchar funct
I use vi/vim and have lots of map commands in my .exrc file,
however, I never used the "ab" abbreviation capability.
I didn't have any wisdom to contribute, but this *did* prod me to
have a look at what "ab" is capable of, and I created several very
useful things for my own work. So thank
