On Mon, Dec 31, 2012 at 12:26:56PM +0200, Moshe Kamensky <[email protected]>
wrote:
> Thank you. I'm still confused, though; urxvt does know, in some sense,
> that this is one character, rather than 6.
No: <1111> is six characters: "<", followed by four "1" characters, followed
by a ">".
These six characters are not the same as the unicode character with code
value 0x1111, which, in an utf-8 locale, would be represented by the three
octets e1 84 91.
There is a difference between the two - urxvt simply displays what it
receives.
> For example, when I access the line from a perl extension, using ROW_t,
> I get just one character.
Sorry, but that's not true.
> I thought that once urxvt knows what character is there, vim would no
> longer be involved in displaying it.
That's true, but you are working on the false premise that urxvt receives
this unicode character, when in fact, it receives 6 ascii characters.
There is no code that expands unicode characters to angle bracket form in
urxvt.
It might be possible that some non-standard extension (like the bidi
extension you use) does this, but it's highly unlikely, because it
wouldn't be able to effectively fake cursor movements. Still possible
though, but that would then be an issue with the bidi plug-in.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
