[Top][All Lists]

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

Re: lynx-dev Bug with "-cfg" flag in lynx 2.8.2

From: Leonid Pauzner
Subject: Re: lynx-dev Bug with "-cfg" flag in lynx 2.8.2
Date: Wed, 20 Oct 1999 21:30:13 +0400 (MSD)

20-Oct-99 11:37 address@hidden wrote:
> To reproduce:

Hmm... indeed. This pehaviour present in current dev version, 2.8.2,
2.8.1 (and probably more early) and have something with

(but see the end of this message).

Try the html in sample below and play with ` and ' ("MINIMAL"/HISTORICAL"
comments toggle) and see "Some text" disappearance...
Even worth, in -prettysrc mode if you switch to source
yuo will see a trancated page,
e.g. <table> will be the last word on the page.

> % ls
> foo.html
> % more foo.html
> <html>
> <head><title>foo</title></head>
> <body>
> <table>
> <!------ a comment -------->
> <td>
> Some text
> </td>
> </tr>
> </table>
> </body>
> </html>
> % touch lynx.cfg
> % ls
> foo.html  lynx.cfg
> %

> Now, if you run "lynx foo.html", Lynx will correctly display the
> phrase "Some text".

> However, if you run "lynx -cfg lynx.cfg foo.html", Lynx will display a
> blank screen.

> If you remove the comment line from the HTML, both commands will
> correctly display "Some text".

> I have no familiarity with the Lynx 2.8.2 code, so I can't really
> speculate on what might cause this bug, but it obviously has something
> to do with comments, and probably something to do with comments inside
> tables.

> -- Rohan.

> I noticed this very bizarre bug while looking at the following URL:

BTW, I recall that MINIMAL_COMMENTS set to TRUE in distribution's lynx.cfg
and that is contrary to compilation default which is FALSE (LYMain.c),
so using another -cfg file which will not include the distribution's one
may be potentially dengerous for user (information lost).
This is something unusual since all the rest statements from lynx.cfg
are defaulted to built in values.

See also quotation below. Have no idea whether we got any success in pushing
Netscape and the world into our side :)

# If HISTORICAL_COMMENTS is TRUE, Lynx will revert to the "Historical"
# behavior of treating any '>' as a terminator for comments, instead of
# seeking a valid '-->' terminator (note that white space can be present
# between the '--' and '>' in valid terminators).  The compilation default
# is FALSE.
# The compilation default, or default defined here, can be toggled via a
# "-historical" command line switch, and via the LYK_HISTORICAL command key.

# If MINIMAL_COMMENTS is TRUE, Lynx will not use Valid comment parsing
# of '--' pairs as serial comments within an overall comment element,
# and instead will seek only a '-->' terminator for the overall comment
# element.  This emulates the Netscape v2.0 comment parsing bug, and
# will help Lynx cope with the use of dashes as "decorations", which
# consequently has become common in so-called "Enhanced for Netscape"
# pages.  Note that setting Historical comments on will override the
# Minimal or Valid setting.
# The compilation default for MINIMAL_COMMENTS is FALSE, but we'll
# set it TRUE here, until Netscape gets its comment parsing right,
# and "decorative" dashes cease to be so common.
# The compilation default, or default defined here, can be toggled via a
# "-minimal" command line switch, and via the LYK_MINIMAL command key.

reply via email to

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