this post was submitted on 27 Aug 2023
60 points (96.9% liked)
Linux
48224 readers
911 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So you're saying you do not already take the reasonable approach of quoting filenames in your scripts, and the rest of us have to work around your lack of foresight?
Feel free to travel back in time and have a discussion with Ken Thompson in ~1970, whether spaces in file/folder names should be allowed in the first place. I for one use an underscore instead, whenever I have control.
Yeah I try to avoid them as well, but sometimes you have filesystems shared by Windows users who don't know any better. I also process tv show and movie files which always contains spaces in their names, so I just got in the habit of quoting the filenames so there's never any question. One of these days I need to see if those single quotes interfere with the process of renaming files -- do they get pulled in when you read a directory into an array? If so, then when I work with the filenames as strings it would mean that the new filename is incorrect. If they don't get included, then the whole argument of it making it 'easier' to work from the command line is false because now you have inconsistent results depending on how exactly you work with the results from the ls command. As it is, I'll probably have to start including the -N parameter in my scripts just to make sure I always get a known result now and in the future.
It's certainly no bad habit to handle spaces in scripts preemptively, and obviously they do occur in the wild. Quotes from ls output do not get piped to other commands. I had to look that up myself right now, because it has been quite a while since it mattered to me.
Looking through some scripts I wrote back in the day, I seem to like to use
ls -1in scripts. I guess that reduces ambiguity on what the separator is.Using ls -1 certainly helps if you are stripping content from the screen, but in recent years I have always found that using ls within a bash script (like if you use FILES=$((ls)) to get an array) returns a proper list correctly separated. It would not surprise me though if that is a feature of bash 4, I do remember we used to have to use the read command to get the appropriate output. So yeah, if all bash commands were simultaneously updated to strip those single quotes at the same time that it was added to the output of ls then it's probably not an issue. I still find it a completely useless annoyance just seeing them in the output and having to add flags to all of my desktops and servers to strip out content that I never asked for. If somebody wanted this then why not let them add a flag to their machines to include the feature?