[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev improper comment bug
|
From: |
David Woolley |
|
Subject: |
Re: lynx-dev improper comment bug |
|
Date: |
Thu, 25 Jan 2001 08:02:37 +0000 (GMT) |
> <! Some uninteresting text >
This doesn't even start a comment. I assume that you you meant
<!-- Some uninteresting text >
> I realise that extensive error-recovery takes a lot of time,
> but the comment in the <HEAD> missing the trailing "--" causes
There are options to close a comment declaration on just >, rather than
requiring paired --'s as well. The problem with doing adaptive
error recovery is that you may have to read in the whole document to
be sure that the > was not simply a > within the comment. Lynx is not
designed for backtracking.
>From lynx.cfg:
# 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.
#
#HISTORICAL_COMMENTS:FALSE
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden