Re: lynx-dev url#name is treated the same as url for -dump

[Henry Nelson]

> Philip Webb wrote:
> 031003 Thomas Dickey wrote:
> > On Sat, 4 Oct 2003, Dan Jacobson wrote:
> >> not to start printing at #name.
> >> I don't care about -nolist or -list issues right now,
> >> I just think there is little excuse for not printing to a file
> >> the same thing you are already showing to the screen -- a bug!
> > submit a patch that works & doesn't break existing functionality,
> > and I'll consider it just like any other patch.
[...]
> 
> it's a bug only if the pgm doesn't do what its author(s) intended,
> incl avoidance of dangerous situations, eg buffer overflows.
> otherwise, it's a limitation at worst & then only in the view of critics.
> 
> i have no opinion either way re the limitation under discussion.

As a Web page author, I'll express my _personal_ opinion again.  1) Lynx's
forte is as an interactive-use browser, not as a spider or robot.  Use of
Lynx non-interactively to bypass the wishes of the page/site owners seems
like abuse of the software and disrespect to the owners.  2) If Lynx prints
to a file only the content beginning with the fragment identifier then it
is NOT acting in the same manner as it is in interactive mode.  Lynx renders
the entire content of the URL and _positions_ the rendering on the screen
according to the fragment identifier.  In an interactive session you only
need to press 'b'ack or [Home] to see that it has rendered the entire page
from the "top".  When I insert fragment identifiers in a document it is for
the convenience of the reader; it is not a statement that the content above
any particular fragment identifier should be ignored.

__Henry

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden