I discovered this change today while playing with a “modern” Linux install, and I’m unreasonably upset about it. https://unix.stackexchange.com/questions/258679/why-is-ls-suddenly-wrapping-items-with-spaces-in-single-quotes
Why is 'ls' suddenly wrapping items with spaces in single quotes?

I just noticed that on one of my machines (running Debian Sid) whenever I type ls any file name with spaces has single quotes surrounding it. I immediately checked my aliases, only to find them int...

Unix & Linux Stack Exchange
@siracusa Unpopular opinion: This change is, on balance, good. “Oops I used the output of ls” is a time-honored rake for new unix users to step on.
@njvack @siracusa unpopular opinion: this is why powershell should replace bash

@joeld @njvack @siracusa I second this unpopular opinion, partially because it would make it easier to go cross-platform without needing WSL or anything of that ilk.

But seeing as we are where we are… I’m learning how to parse output from find instead of ls and my life is better for it.

@atomicangel @joeld @siracusa it's bonkers how many awful characters are allowed in posix filenames. Quotes? Globbing characters? Newlines? Have at it.

`find -print0 | xargs -0` is the way