[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev bug? unable to 'g' to #anything
From: |
Klaus Weide |
Subject: |
Re: lynx-dev bug? unable to 'g' to #anything |
Date: |
Tue, 27 Apr 1999 21:50:52 -0500 (CDT) |
On Tue, 27 Apr 1999, Vlad Harchev wrote:
> On Mon, 26 Apr 1999, Philip Webb wrote:
> > 990426 Vlad Harchev wrote:
> > > lynx doesn't accept anchors as 'g' targets.
> > > If you enter '#anything', it jumps to dired of current directory.
It's been behaving like that for a long time. The question is, should it
behave differently? Selecting fragments by hand isn't a very common
occurrence.
This could be seen as a special case of a more general question: should
lynx try to resolve relative Goto URLs (presumably wrt. the currently
loaded document)? I think not, at least for the general case. It would
conflict with what it currently does, trying to guess several ways what a
non-full-URL string might mean.
Even for the '#anything' case - if you have a file named '#anything',
'g' '#anything' will load that file.
> > you can do it by entering G , then adding #anchor to the presented URL,
> > tho' you than have to do ^r to get it to move to that page.
>
> Thanks. Seems that it's ugly enough - going to anchors is useful for large
> documents, and pressing '^r' will reload them.
It shouldn't be too difficult to remove the need for the RELOAD.
Klaus
- Re: lynx-dev bug? unable to 'g' to #anything,
Klaus Weide <=