Date: Fri, 16 Oct 2020 19:07:41 +0100 From: Jon Schneider <freebsd@jschneider.net> To: Polytropon <freebsd@edvax.de> Cc: Ralf Mardorf <ralf-mardorf@riseup.net>, freebsd-questions@freebsd.org Subject: Re: sh scripting question Message-ID: <69FD7F52-B1D9-4540-9379-CD3122BEDBB6@jschneider.net>
next in thread | raw e-mail | index | archive | help
There=E2=80=99s a YouTube publisher called enderman who shows how how = inconsistently these special CP/M and DOS file names are handled in = Windows. He does things like create install Windows itself into con. I = have found you can total OneNote for Windows users by creating a = notebook called for example =E2=80=9Ccon=E2=80=9D. https://www.youtube.com/watch?v=3DYcAdgcAvTCs&t=3D221s Having watched these I am convinced Microsoft should have simply allowed = them in Windows. Currently there is a horrible mess. As for the original problem the only (and safe and portable way among = all OSs that use C language interfaces) is to assume that the null = character is the only safe separator in file lists. Because of the = underlying C language interfaces. Jon > such as "COM1:". :-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69FD7F52-B1D9-4540-9379-CD3122BEDBB6>