LYNX-DEV Re: "missing highlight on active link"

[Klaus Weide]

On Thu, 21 Aug 1997, RamNarayan S wrote:

> Looks atlast the problem for the missing highlight on a active link could be
> traced.
[...]
> 
> The  problem  seems to be in the order in which  the  escape  sequences  are
> called for  highlighting/underlining  in the file LYCurses.c.  It looks like
> for my term, (an xterm and also a vt100), the  underline  attribute  must be
> set before the reverse video attribute.  Otherwise the underlining attribute
> obliterates the reverse video thus blanking out the  highlighting on a vt100
> (Looks  like  vt100s'  can't  display   underlining)   and  just  displaying
> underlining on the xterm.  Looks like they don't seem to coexist.

If your termcap/terminfo says that reverse and underline CAN be used
together, when in reality they can't, then your terminal description is
in error.  If the terminal description says that the terminal doesn't
support underline, but lynx still emits a control sequence for turning
underlining on, then arguably it is an error in lynx or the underlying
curses library.  (With Slang it could also be some default assumption
about a terminal for which no terminal description is available.)

> In the proc  "lynx_start_link_color"  in LYCurses.c the following  seemed to
> cause the problem.
> 
>             if (flag) {
>             /* makes some terminals work wrong because
>              * they can't handle two attributes at the
>              * same time
>              */
>             /* start_bold();  */
>             start_reverse();
>         #if defined(USE_SLANG)
>             if (SLtt_Use_Ansi_Colors)
>                 start_underline ();
>         #endif /* USE_SLANG */
>         #if defined(FANCY_CURSES)
>             start_underline ();
>         #endif /* USE_SLANG */
> 
> If we move  the last  three  lines to  before  the call to  "start_reverse",
> things are fine.

We may just get rid of that start_underline(), possibly only for
non-color, as suggested by Fote.  But the lines below that section
(and elsewhere) may still try to combine bold with underlined.  So you
should still check your terminfo or termcap entry.

> And on the other problem whose dump I had given, there was a typo.  That
> segment has been corrected below.  This works fine in post 2.7.1 versions
> (developmental). 
> 
> >                            From: &#Name1 & Name2"
> 
> The above should be         From: &#034Name1 & Name2"    and not as above.

Ok, but the ac-0.# code does parse the '&#034Name1' as '"Name1', right?


   Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;