Re: [Lynx-dev] pretty-src coloring breaks

[Rado S]

=- Thomas Dickey wrote on Fri  9.Mar'07 at 10:48:18 -0500 -=

> > (uh, btw, I just noticed in ncurses 5.5 "xterm" != "xterm-new":
> >     key_backspace: '\177', '^H'
> > Why is this different? Why isn't "xterm" ^H, too?)
> 
> It depends on the platform - the BSD people want ^H, and the Linux want ^?.

Hum, heh, why not unite them? Let's stick to BSD variant, ECMA-048
calls it BS, too. ;)

> > In "screen" this is mapped to "flash_screen" so I can't have
> > audio-bell in "screen".
> 
> It's possible that there's some issue with the binary file.
> What does infocmp say?

About what exactly? "flash_screen" ...
screen: =\Eg
xterm-new: ==\E[?5h$<100/>\E[?5l

> > When I use the same lynx in the same color-xterm inside screen
> > (compiled with sun's curses but using ncurses5.5 "xterm-new" data
> > file and ncurses 5.2 datafile for "screen-w"), then lynx' ACS
> > arrows appear as ,,, for <<< and +++ for >>>.
> 
> Those are the default mapping for arrows in Solaris (and
> ncurses): iirc, Linux console has a mapping for that, and if
> you're running in a UTF-8 terminal, ncurses provides a built-in
> mapping for that.

But why does it work fine in xterm directly but not inside "screen"?

("screen" 3.09.10 (FAU) 4-Sep-01 itself is _fairly_ old, but the
terminfo datafiles are new (screen 5.2 and xterm-new 5.5), though
I wasn't aware of such issues before, guess never used ACS stuff
in "screen" before).

-- 
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.