Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Muttley@dastardlyhq.com
Newsgroups: comp.unix.programmer
Subject: Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin)
Date: Sat, 31 Aug 2024 08:37:01 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <vauknd$uvji$1@dont-email.me>
References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> <ubg6o7$3jrsn$1@news.xmission.com> <ubg853$2ssj8$1@dont-email.me> <ubg8a8$2t20l$1@dont-email.me> <vaubbo$1d324$1@news.xmission.com>
Injection-Date: Sat, 31 Aug 2024 10:37:02 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="505150aa1191500ac8748e59d84a8d4d";
	logging-data="1015410"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/+UUrLwISjMarFYLFZvp3d"
Cancel-Lock: sha1:lfC8Wjo5owKwcG8iuso5MbBJ5m0=
Bytes: 1584

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.

>	    b) The way VFAT does it (and NTFS emulates) - where, for any
>		file with a long name, there is an 8.3 filename (usually
>		with weird characters in the filename) as well, and either
>		filename is usable by programs.  This is one place where I
>		think Windows really gets it right (and Unix could learn
>		from it).

No, just no. The windows "solution" is a hideous hack only required for
backwards compatability.