> There is a line after the Eatchar function:
>
> iabbr if if ()=Eatchar('\s')
>
> Is this a necessary companion of the Eatchar function?
> This seems to be a protection against eating into text, but
> should not this begin with ":" ? And the double "if", isn't
> it suspicious?
No, you don'
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
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
> 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
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
Am Thu, 28 Jan 2010 22:24:21 +1100
schrieb Miklos Somogyi :
> Hello Folks,
>
> This is not a groff question but I suspect that many of you have the
> expertise and experience to solve this riddle.
>
> I bought a diNovo Edge for Mac, the best keyboard I have ever had.
> Except that the function k
