Re: Question marks in local source filenames

On Sun, Feb 13, 2022 at 01:32:34PM +0000, David Woolley wrote:
> On 13/02/2022 04:00, Thorsten Glaser wrote:
> > This is of course a bug, local filenames are unconstrained
> > other than not containing NUL and slash of course.

> That's not true.  They have the same constraints as the path part of any
> URI:

The syntax of "lynx" according to the man page is

 lynx [options] [optional paths or URLs]

so the filename with a '?' character in it is a path, not a URL, and
therefore the RFCs for URIs do not apply.

Besides, Lynx still defaults to plain-text even if you escape the '?'
characters in the filename to %3F.

imc