Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Nuno Silva <nunojsilva@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Fri, 02 May 2025 00:27:10 +0100
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <vv100f$3nhss$1@dont-email.me>
References: <pan$4068a$3910f4f1$8cbecede$9e42905e@linux.rocks>
	<20250428080014.0000347f@gmail.com> <m79tdsF2bf6U1@mid.individual.net>
	<20250428111242.00007426@gmail.com>
	<pan$c046d$e87ef491$a3427b7a$ac576dbc@linux.rocks>
	<slrn1011nu8.46v.rotflol2@geidiprime.bvh>
	<vurjl9$2pskn$1@dont-email.me>
	<slrn1013t50.1aev.rotflol2@geidiprime.bvh>
	<vAGdnR-Fj9qGS4_1nZ2dnZfqn_udnZ2d@giganews.com>
	<slrn1016uic.2qk.rotflol2@geidiprime.bvh>
	<m7hgt7F8mvgU5@mid.individual.net> <6813f997@news.ausics.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 02 May 2025 01:27:11 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="2f82e80d399c17808b2533e8c8691fbb";
	logging-data="3917724"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18NMH6TtX3XM9YKsogRrq0F"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Cancel-Lock: sha1:gHKT4br9ZPK1dPsN6OSHqIqaNic=
Bytes: 2591

On 2025-05-01, Computer Nerd Kev wrote:

> rbowman <bowman@montana.com> wrote:
>> On Thu, 1 May 2025 13:42:36 -0000 (UTC), Borax Man wrote:
>>> But spaces in filenames cause me *far more* headaches.  They are the
>>> greater evil.
>> 
>> The real evil was the mishmash of DOS and Windows that wound up with 
>> 'Program Files' becoming 'progra~1'. 
>
> I question the wisdom of Torvalds on this topic since he allowed
> ext filesystems to have an even greater evil than either of those:
> newlines in file names! Imagine if the average joe were exposed
> to that capability - we'd have multi-paragraph file names to deal
> with all over the place.

But why should newlines not be allowed in file names? Last I checked
(granted, that was many years ago), there is only one character which
usually needs to be excluded, \0. And then the path element separator is
probably convenient to avoid. Anything else, where and why would you
draw a line? And how would you avoid reaching the Windows situation
where there's a whole group of convenient glyphs that are not allowed?
(Or can that be disabled too in Windows NT?)

-- 
Nuno Silva