Re: lynx-dev what to do with stubborn terminal emulators?

[dickey]

> 
> From: address@hidden 
>  
> >> When however I use my sparc solaris 2.6 and the cde dtwm , I get an 
>  
> >is that using dtterm?  I thought you would be using --enable-default-colors 
>  
> yes, that is the dtterm.  Sorry - my fingers typed one thing while my brain 
> was saying something else. 
>  
> > for that.  (Actually, if you _don't_ do that, and op is using the 37/40 
> > codes, you'll get behaviour like you're reporting -- you'd have to use the 
> > 39/49 codes to get default colors of gray). 
>  
> I am uncertain to what "codes" you refer. 

run infocmp.  look at the value for 'op'.  If it's using op=\E[39;49m (very
likely unless you've got a customized terminfo), then
that tells curses how to reset the foreground/background to the terminal's
original default colors.  But Solaris curses doesn't exploit that in the
same way that ncurses can, with use_default_colors.

If you don't configure lynx to use the feature, it'll paint white
background as you've noted, because that's the color specified in lynx.cfg
or lynx.lss

The configure --enable-default-colors option adds code that asks ncurses to
use the op string to obtain the terminal's default colors (the gray, for
instance).

  
> --  
> Larry W. Virden                 <URL: mailto:address@hidden> 
> <URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems." 
> Unless explicitly stated to the contrary, nothing in this posting should  
> be construed as representing my employer's opinions. 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey