Thomas wrote:
> Mapping seems to be buggy with some characters.
> For instance:
>
> :imap ' foo
>
> does not work (the apostrophe is U+2019). If the mapped string
> contains this apostrophe but does not begin with it, there is no
> problem. For instance, this works:
>
> :imap x' foo
>
> But it is impossible to map a string beginning with this apostrophe,
> and the <Char-0x2019> construct does not help. This is weird, because
> there is no problem with mapping the usual apostrophe U+0027. Other
> paradoxes can be found : It is possible to map the no-break space
> (U+00A0) but not its thin version (U+202F), the usual minus sign
> (U+002D) but not the en-dash (U+2013) and the em-dash (U+2014).
>
> I first thought vim had a problem with mapping multibyte characters
> but it actually deals well with most of them. Any explanation, why the
> mapping does not work with some characters?
How can you tell if the mapping works or not?
You can see what a key actually produces with CTRL-V <key> . So when
you type
:imap CTRL-V <key> foo
Where CTRL-V is one key and <key> is the mapped key.
Does the mapping still not work?
--
hundred-and-one symptoms of being an internet addict:
237. You tattoo your email address on your forehead.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
