Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connectionsPath: ...!2.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: Sat, 31 Aug 2024 23:34:22 -0000 (UTC) Organization: A noiseless patient Spider Lines: 22 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 01:34:22 +0200 (CEST) Injection-Info: dont-email.me; posting-host="451ad815162a3f3080e1cdc6c6433f29"; logging-data="1247845"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX194vuGmY33cLunyz/M8tERG" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:88eOsKaJzysOfisUBgL9sLFcRPY= Bytes: 2278 On Sat, 31 Aug 2024 09:27:44 +0100, Richard Kettlewell wrote: > (I’ll be disappointed in extreme cases of course, e.g. filesystems that > permit ‘/’ in filenames, but the scale of the problem can be minimized.) The nice thing about Unicode is the alternatives it offers: so you can’t use “/” in a filename, but you can use “∕” instead. > I think the thing that makes it hard is not the spaces as such, but the > tooling that makes it inconvenient to handle them, which primarily means > Bourne shell parsing rules. The problem basically ceases to exist once > you’re outside the shell ecosystem. > > The rest of Unix has evolved substantially since the 1970s but shell is > still stuck in this particular trap. It’s like we’re still making making > arrowheads out of flint but everything else from steel. If you avoid newlines in filenames, Posix shells can cope with anything else if you set “IFS=$'\n'”. If you insist on wanting to accept those as well, then I don’t think Posix is enough, but Bash does have facilities that help you cope.