[Top][All Lists]

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

Re: [Lynx-dev] spans (open+close tag) in prettysrc don't close when attr

From: Rado S
Subject: Re: [Lynx-dev] spans (open+close tag) in prettysrc don't close when attribute ends by WHITE
Date: Mon, 9 Jan 2006 16:47:49 +0100
User-agent: Mutt/1.5.6i

[=- Thomas Dickey wrote on Thu  5.Jan'06 at 20:10:54 -0500 -=]

> On Thu, 5 Jan 2006, Rado S wrote:
> >and have
> >in your lynx.cfg, then the "nowrap" will cause the rest of the
> >file to be bold, ignoring all other tags and their prettysrc
> >specs.
> hmm - I do see a problem (the "blub" is miscolored). I suppose
> the symptom depends on the actual colors available.

Oh, I believed it kept bold status in addition to whatever else is
supposed to be set due to the fact that the "WHITE break"s didn't
lead to the required execution of PSRCSTOP, generally, independent
of colors (recursive, nested).
 At least for me _everything_ immediately after an offending
attribute is bold, no matter what other src-directives might apply.

Maybe I misunderstood how lynx handles coloring in general and for
prettysrc in particular.

> >Why not treat prematurely WHITE-ended attribute as "badattr" instead?
> perhaps - I'll have to test that, to see the effect.
> (I recall that making changes to SGML.c isn't always simple).

I know what you mean from my glance at it, that's why I haven't
found a "simple" fix to offer.

What would happen if for the given cases the
        "if (WHITE(c)) break;"
were dropped and the checks for ">" extended for "WHITE" as proposed?
Would that break anything (serious ;)?

© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.

reply via email to

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