| Deutsch English Français Italiano |
|
<vb8ahn$3hhg4$2@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro <ldo@nz.invalid> Newsgroups: comp.unix.programmer Subject: Re: Long filenames in DOS/Windows and Unix/Linux Date: Wed, 4 Sep 2024 00:44:39 -0000 (UTC) Organization: A noiseless patient Spider Lines: 11 Message-ID: <vb8ahn$3hhg4$2@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> <vauknd$uvji$1@dont-email.me> <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> <vb81vo$3g6hb$6@dont-email.me> <87o7541ggd.fsf@nosuchdomain.example.com> <vb87jr$3h6uk$1@dont-email.me> <87bk141cw9.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 02:44:39 +0200 (CEST) Injection-Info: dont-email.me; posting-host="176f5fbfb5d1157be6fd816dae78eee8"; logging-data="3720708"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/4w21lz3yRUH/7mzo++MF3" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:4V94rqL3o11lQa2fMR1zYW5OeaI= Bytes: 1821 On Tue, 03 Sep 2024 17:27:34 -0700, Keith Thompson wrote: > Second attempt: > > IFS='\n' ; for file in * ; do cp -p $file $file.bak ; done > > but that leaves IFS set to its new value in my interactive shell. Which in my experience is no biggie. Next step: what if you wanted to handle newlines in file names as well?