Re: Question marks in local source filenames

Ian Collier dixit:

>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.

Exactly. But lynx d̲o̲e̲s̲ this part correctly (“lynx foo?.htm” is
correctly expanded to file://localhost/home/«me»/foo%3F.htm in ‘V’).

>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:

If called as URI, but in this case I did (I did “g . <Enter>”, went to
the file and pressed → to activate it, so it w̲a̲s̲ urlencoded):

>> so ? is not permitted, unless % encoded

That. Even with this, it’s broken:

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

That.

Also, note how I said “local source filenames”, not URLs. I know all
about urlencoding filenames (having converted the corresponding RFC
to a grouping regex only this year for someone).

bye,
//mirabilos
-- 
<ch> you introduced a merge commit        │<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
<ch> should have cloned into a clean repo      │  fault (core dumped)
<ch> if I rebase that now, it's really ugh     │<mika:#grml> wuahhhhhh