Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin)

On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote:

On Tue, 3 Sep 2024 17:37:21 -0000 (UTC)
Kaz Kylheku <643-408-1753@kylheku.com> wrote:
>

On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote:

On Sat, 31 Aug 2024 08:37:01 -0000 (UTC)
Muttley@dastardlyhq.com wrote:
 

On Sat, 31 Aug 2024 05:57:12 -0000 (UTC)
gazelle@shell.xmission.com (Kenny McCormack) gabbled: 

   2) Spaces in filenames are pretty much a necessity from the
end-user   

 
No they're not. 

>
WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight
or-alternatively-make-liberal-use-of-dashes
or_use_underscores_like_some_deranged_freak 

 
This is a strawman argument; filenamews should not only not have
spaces, but should be reasonably short. (No, not 8.3 short; that's not
"reasonably" and therefore another strawman.)
 
If we use spaces in your examples, the readability improves, but if
you have a directory of just half a dozen such names, you've got a
paragraph to read.

>
I'm unclear on how that qualifies as a straw-man argument...?

Because it is based on a strawman interpretation of the "no spaces"
rule. That strawman interpretation is that there are no other rules
used in combination with the "no spaces" rule, and thus that any
ridiculous name is fine, just as long as it doesn't contain spaces.

And so, look how unreadable is this 100 character name in CamelCase!
Q.E.D. no spaces is a bad recommendation!

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca