[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] uxterm vs GNU screen weirdness

From: Thomas Dickey
Subject: Re: [Lynx-dev] uxterm vs GNU screen weirdness
Date: Wed, 01 Oct 2008 19:43:40 -0400
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Sep 30, 2008 at 04:51:31PM +0000, Thorsten Glaser wrote:
> Thomas Dickey dixit:
> >which means those escaped commas.  If xterm's _not_ in UTF-8 mode, then
> >none of the different mappings work, because none of them are 
> >VT100-compatible.
> xterm apparently doesn’t handle them either:
> address@hidden:~ $ print 
> '\033(0++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~'
> ++\,\,--..00◆◆▒▒°°±±␤␤␋␋┘┘┐┐┌┌└└┼┼⎺⎺⎻⎻──⎼⎼⎽⎽├├┤┤┴┴┬┬││≤≤≥≥ππ≠≠££··

Looking again, I see the source of confusion.  There are two ways to get
the alternate character-set codes.  With just a print command as shown,
you'll only get the vt100 set, since xterm supports the shift-out/shift-in
sequences.  Not all terminals do this (support the vt100 controls in UTF-8
mode), and not all of the characters are vt100 codes.  For the other cases,
ncurses has to look in a table for the corresponding UTF-8 codes directly.

That's consistent with what I said before, that vt100's don't do the
left/right arrows.  Here's a screenshot showing uxterm drawing the
various special characters that might appear in the acsc string.
> The only ones working which are not in terminfo are ‘hh’ thusly. Apparently,
> wide ncurses are used for that or something.

Thomas E. Dickey <address@hidden>

Attachment: ncursesw-acs.png
Description: PNG image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]