On Tue 07 Apr 2009 at 12:42:08 +0200, Bram Moolenaar wrote:
This has two advantages:
1. It's backwards compatible.
2. Avoids accidentally typing the wrong number of hex digits.
3. Allows typing a hex digit next as a separate character.
Eh, _three_ advantages.
Nobody expects the spanish
Matt Wozniski wrote:
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Unicode value in strings: I mean, \u and \U still accept no
more than
Tony Mechelynck wrote:
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Unicode value in strings: I mean, \u and \U
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Unicode value in strings: I mean,
