"Stuart Longland" <[email protected]> wrote:
> On 12/4/20 11:39 am, [email protected] wrote:
>> "Stuart Longland" <[email protected]> wrote:
>>> On 11/4/20 2:30 am, [email protected] wrote:
>>>> https://doomwiki.org/wiki/Absurd texture name in error message
>>
>> No, what I wrote is:
>>
>>> 'https://doomwiki.org/wiki/Absurd texture name in error message'
>>
>> World of difference. To a UNIX guy.
>
> Ohh, I did see the quotes, that's what made me try the URI with spaces
> after seeing the 404 page.
You initially thought that the final component was 'Absurd'? :x
>> Seems like some people eat everything the WWW n00bs emit, right up to
>> and including a turd.
>>
>> What's next? All list messages in quoted-unreadable? C'mon.
>
> doomwiki should not be using such characters in their URIs. I'm not
> blaming you for their presence by the way. Had they done the right
> thing in the first place, the quotes would never have been needed. :-)
Actually, metyped that URL from memory. lynx(1) DTRT's when invoked w/
a (properly-quoted) address w/ space in it, even as it's 'g'oto command
does not (meconsiders the latter a bug).
To me, a file name containing spaces is a natural thing, and thus
meconsiders it absurd to require everyone to expand them to a somewhat
unintuitive 3-character sequence just to quote them. That's why we have
dedicated quoting characters, but the W3C et al. still have to discover
those. After ~50 years.
(The issue could also be solved by giving names a special format (for
example, by underlining them) in order to distinguish them even w/
spaces present. Such an approach has other benefits as well, but has
nothing to do with UNIX-as-we-know-it.)
--zeurkous.
--
Friggin' Machines!
