Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.unix.programmer Subject: Re: Long filenames in DOS/Windows and Unix/Linux Date: Tue, 03 Sep 2024 16:10:42 -0700 Organization: None to speak of Lines: 22 Message-ID: <87o7541ggd.fsf@nosuchdomain.example.com> References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> <20240903084440.0000663d@gmail.com> <20240903103327.395@kylheku.com> <20240903113937.000008a3@gmail.com> <20240903130000.933@kylheku.com> <20240903132547.00000656@gmail.com> <87seug1iyj.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 04 Sep 2024 01:10:43 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0c8cc2609bc8d9fbbbb3d106ce45f413"; logging-data="3698149"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18QcHpam1syD8ibPr5MVXGR" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:a6oZh3hcRXfeggPHlKstMsb2InY= sha1:NfI0G1MzmFupDR80OwvZYuS0dnk= Xref: csiph.com comp.unix.programmer:16272 Lawrence D'Oliveiro writes: > On Tue, 03 Sep 2024 15:16:36 -0700, Keith Thompson wrote: >> For example, I might type something like: >> >> for file in * ; do cp -p $file $file.bak ; done > > It’s quite easy to fix that to work with spaces in file names. I wouldn't call it "quite easy". Certainly it can be done, and I do it when I need to. My point is that there is an advantage in being able to avoid the extra effort when I know it's not needed. How would you do it? > How long > have you been working with *nix shells? A long time. I might consider being more specific later. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */