Path: ...!feeds.phibee-telecom.net!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.unix.programmer,comp.unix.shell Subject: Re: Long filenames in DOS/Windows and Unix/Linux Date: Sun, 1 Sep 2024 07:03:31 -0000 (UTC) Organization: A noiseless patient Spider Lines: 10 Message-ID: References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 01 Sep 2024 09:03:32 +0200 (CEST) Injection-Info: dont-email.me; posting-host="451ad815162a3f3080e1cdc6c6433f29"; logging-data="1496996"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Vo5O3SjPvx4/ckNorECjs" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:1sF2ha5YF+opzPPQLvguaTyTWfg= Bytes: 1560 I wrote: > If you avoid newlines in filenames, Posix shells can cope with anything > else if you set “IFS=$'\n'”. Sorry, no, it looks like the “$'...'” syntax for string literals is not from Posix, it’s a Bash-ism. I think it’s still possible to assign a newline to $IFS, it just takes a bit more work.