Re: Case Insensitive File Systems -- Torvalds Hates Them

On 5/9/25 1:06 AM, Marc Haber wrote:

not@telling.you.invalid (Computer Nerd Kev) wrote:

No, the GNU Find man page says:
"-print0, -fprint0
Always print the exact filename, unchanged, even if the output is
going to a terminal."
>
Which is the same as the default -print if the output isn't to a
terminal, except -print0 uses null instead of newline to separate
filenames because they're a particular problem. Other special
characters aren't as problematic.

 The shell tokenizes at whitespace, and a newline is often treated as
whitespace. -print0 is the canonical protection that makes your script
handle spaces in newlines correctly, and THOSE are rather common in
file names. Look in your music directory for examples.
 You've gotten yourself into something in this discussion. Better take
a step back to stop embarrassing yourself.

   Just a meta-comment .... the length and strength of
   this thread really makes it clear how BAD fundamental
   things like file/dir names and such have been allowed
   to become. Someone up in the aether wasn't paying
   attention. More "Oh THAT sounds cool and nice - the
   complete text of War And Peace as a file name ..."