Path: ...!feeds.phibee-telecom.net!3.eu.feeder.erje.net!feeder.erje.net!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!cleanfeed2-b.proxad.net!nnrp1-1.free.fr!not-for-mail Newsgroups: comp.os.linux.misc From: =?UTF-8?Q?St=C3=A9phane?= CARPENTIER Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them References: <20250428080014.0000347f@gmail.com> <20250428111242.00007426@gmail.com> Organization: Mulots' Killer User-Agent: slrn/pre1.0.4-9 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Date: 02 May 2025 20:02:43 GMT Lines: 19 Message-ID: <681524e3$0$5192$426a34cc@news.free.fr> NNTP-Posting-Date: 02 May 2025 22:02:43 CEST NNTP-Posting-Host: 78.201.248.7 X-Trace: 1746216163 news-4.free.fr 5192 78.201.248.7:57656 X-Complaints-To: abuse@proxad.net Bytes: 2096 Le 02-05-2025, Borax Man a écrit : > On 2025-05-02, The Natural Philosopher wrote: >> I LOVE spaces in filenames. >> I guess if you use the command line a lot and parse file arguments using >> spaces, its a bit irritating. >> >> But if you uses a GUI its no issue at all > > Yes, I'm a command line kind of guy, and spaces are a bit of a PITA. > Just have to remember to quote, but when you use shell expansions or > globbing, and then things get a bit trickier. I don't see the difficulty with the spaces in my terminal. My bash manages very well the spaces when I'm using my TAB on files which have some spaces in their names. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io