Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Wayne Newsgroups: comp.unix.programmer,comp.unix.shell Subject: Re: Long filenames in DOS/Windows and Unix/Linux Date: Tue, 3 Sep 2024 13:56:08 -0400 Organization: A noiseless patient Spider Lines: 23 Message-ID: References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 03 Sep 2024 19:56:09 +0200 (CEST) Injection-Info: dont-email.me; posting-host="dd07c4d3c2216d9bc6571e157523e3c6"; logging-data="3595461"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/XW1YoySC8TCJ8HPsnlKY6S7/INGntCmA=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:84P/w3ckb6uGckjgydMpN/aFFn4= Content-Language: en-US In-Reply-To: Bytes: 2044 On 9/1/2024 3:03 AM, Lawrence D'Oliveiro wrote: > 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. Actually, dollar quotes were added to POSIX as of SUS Issue 8: "2.2.4 Dollar-Single-Quotes A sequence of characters starting with a immediately followed by a single-quote ($') shall preserve the literal value of all characters up to an unescaped terminating single-quote ('), with the exception of certain -escape sequences, as follows: ...." -- Wayne