2021-11-11_I_have_absolutely_no_idea_what_you_are_talking_about.txt
I'm “still afraid to use spaces in file names” years old
301–310 of 817 posts
Re: I'm “still afraid to use spaces in file names” years old
#302I am also that age, and kebab-case is the best case for filenames. 2021-01-01-some-important-document.pdf gives me the warm fuzzies. On the off chance that some more differentiation is needed, throw in an underscore and a whole new world opens up
> 2021-01-01 Yes on the date format. Saves you so much time.
I don't bother with the century or the dashes, saves time...
211111_foobar_v1.txt
I am old enough that I still save before printing. I think it was Lotus 123 that engrained it for me.
Re: I'm “still afraid to use spaces in file names” years old
#303Earlier quoted context omitted.
> And shells and other programs still have problems with perfectly legal characters in filenames too, like '!' or ':'. Without asking you to always quote and escape every file name - what alternative is there? If they tried this you'd probably find you didn't like it.
Not exactly - the problem is mostly when doing variable expansion. The fact that bash treats "$x" and $x as different is a bit of a design flaw. Of course there's still an issue with evaluating dynamically generated code, but that problem is partly solved by working with arrays.
I mean how do you want shells to deal with file names with spaces in? Do you think we should have to quote and escape all file names all the time? If not then how do you think it should work?
Re: I'm “still afraid to use spaces in file names” years old
#304Re: I'm “still afraid to use spaces in file names” years old
#305Heck, I'm still afraid to use caps!
Re: I'm “still afraid to use spaces in file names” years old
#306Earlier quoted context omitted.
Honest question - what the heck are those characters?
It corrupted text or "Zalgo" text, it relies on diacritics. See this answer on stackoverflow: https://stackoverflow.com/questions/1732348/regex-match-open...
I disagree with calling it "corrupted." We're not tricking the browser into trying to render garbage bytes that are actually the middle of a jpeg or something. It's actually valid Unicode. It's an edge-case which is not seen in regular usage, but it's technically following all of the rules.
Re: I'm “still afraid to use spaces in file names” years old
#307Earlier quoted context omitted.
"Documents and Settings" still exists on Windows 10, as a soft link to "Users".
You know, this makes me wonder.. tangentially speaking- I wonder how hard it would be to rearrange the folder structure in linux so that I have something like this: /Users/{root, user0, user1, ... }... /System/{Logs, Apps/{opt, container, ...}, Temp, Conf ...}... /Devices/{Mount, sda, sdb, null ...}... /Boot/...
I mean we're heading there with /usr being your /System. Redhat/Pottering are doing heroic work in this space.
/Users -> /home
/System -> /usr
/Data -> /var
/Config -> /etc
/Boot -> /boot
/Ephemeral Temp -> /run
/Persistent Temp -> /tmp
Re: I'm “still afraid to use spaces in file names” years old
#308But it still breaks in so many situations and becomes a pain in the ass in so many other ones! I HATE people who use spaces in file names. For me it is a sign of a "deeply nontechnical person".
Re: I'm “still afraid to use spaces in file names” years old
#309Earlier quoted context omitted.
"Documents and Settings" still exists on Windows 10, as a soft link to "Users".
You know, this makes me wonder.. tangentially speaking- I wonder how hard it would be to rearrange the folder structure in linux so that I have something like this: /Users/{root, user0, user1, ... }... /System/{Logs, Apps/{opt, container, ...}, Temp, Conf ...}... /Devices/{Mount, sda, sdb, null ...}... /Boot/...
This is what I want from Linux. Sensible & guessable names for newcomers to figure out where to put files and programs.
It's frustrating having to spend time to decide whether I should install a program in /var or /opt or /usr. What do they even mean!
So, I disagree with this convention altogether and use /apps or ~/apps now.
Re: I'm “still afraid to use spaces in file names” years old
#310I'm hardly afraid but I just think it's poor ergonomics. Same as the move from xset m 0 0 to xinput --set-prop 'pointer:Logitech USB Receiver' 'libinput Accel Profile Enabled' 0, 1 Everything seems to be going this way in Linux land. Longer names, harder to type names, camelcase names, spaces... I'm looking forward to an OS that treats command line ergonomics as a first class feature and where camelcase & spaces are…
Well, if you think that's bad, behold the recent trend in network interface names on Linux. We started out with 'eth0', 'eth1', etc. Which adapter was which could change when adding and removing a network card. That was bad, so that prompted the evolution. Now we have 'enp1s0', 'enp0s31f6', 'enp13s0' and many similar variations. These are supposedly more stable across device changes. As it turns out, it wasn't. But w…
Missed the 's', it's: