[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] Issue with lynx --source and gopher menus with h gopherty
Re: [Lynx-dev] Issue with lynx --source and gopher menus with h gophertype
Wed, 2 Sep 2020 04:18:59 -0400
On Mon, Aug 31, 2020 at 07:04:01PM -0400, Thomas Dickey wrote:
> On Mon, Aug 31, 2020 at 04:47:56PM -0400, Zachary Lee Andrews wrote:
> > On Sun, 30 Aug 2020, Thomas Dickey wrote:
> > > The short answer is that lynx doesn't recognize the other characters
> > > as being special.
> > >
> > > We're talking about the chunk of code beginning here:
> > >
> > > https://github.com/ThomasDickey/lynx-snapshots/blob/558af4865a2d668cfaaba88477df07d256c1a97c/WWW/Library/Implementation/HTGopher.c#L445
> > >
> > I solved all the issues I was having by removing lines 448 and 449..
> > After making the change, I created a new testcase to see how lynx handles
> > gophermaps with regular HTML files, and weblinks using the old 'GET /'
> > method, the newer 'hURL:' method, and I even put some blatantly wrong
> > examples in there just to see how lynx behaves when encountering them. It
> > does great.
> thanks - will take a look when I'm done putting out a different fire :-)
> In the earlier discussion and example, the "GET" was passed along as "/GET",
> which didn't work...
Here's a gophermap with links for the case you constructed and the
test-case from Tobias Girstmair in April 2019:
In the current code, both test-cases work; removing those lines
makes the "GET" example stop working.
Thomas E. Dickey <email@example.com>
Description: Text document
Description: PGP signature
- Re: [Lynx-dev] Issue with lynx --source and gopher menus with h gophertype,
Thomas Dickey <=