Re: ISO 2022 in terminals

[Timothy Allen]

On Sat, 5 Feb 2011 10:42:37 -0500 (EST)
Thomas Dickey <address@hidden> wrote:
> On Sat, 5 Feb 2011, Keith Winstein wrote:
> 
> > If you run it natively under xterm, it looks fine. If I run it
> > under "LANG=C luit", the first half of each ACS block looks fine
> > but the second half is in ASCII, I think because the shift state
> > isn't being restored.
> 
> something like that (luit's design limits the types of shifts it
> supports, so vttest will probably never look right in that screen).

As I understand it, luit parses out ISO 2022 sequences out of the
output stream and uses them to modify its internal state rather than
passing them on to the terminal emulator.

However, Save Cursor and Restore Cursor are kind of weird sequences
because they affect the ISO 2022 state *and* more traditional terminal
emulation.

Is it possible for luit to parse Save Cursor and Restore Cursor, modify
its character-translation state, and pass those escape sequences
through to the terminal emulator to handle the
non-character-set-related state changes?