I still use the Netbios limitations (15 Characters) when naming servers
I'm “still afraid to use spaces in file names” years old
101–110 of 817 posts
Re: I'm “still afraid to use spaces in file names” years old
#102Earlier quoted context omitted.
I could infer a lot about the second and what those params mean and what they do. The first one is some magical incantation.
Sure. One could also make "move-down-one-line" be the incantation to move the cursor down a line in vi, but I prefer j. Ergonomics isn't all about making everything self-descriptive for someone seeing the thing for the first time. It's about making things comfortable to actually use. If it's so long and complicated that you can't even remember how to do it, it's not very comfortable to use. Even if I could remember,…
> Ergonomics isn't all about making everything self-descriptive for someone seeing the thing for the first time.
We're talking about `xset`. It doesn't make sense to optimize that for usage of more than once a year.
Re: I'm “still afraid to use spaces in file names” years old
#103Somehow the OneDrive clients still refuse to allow leading or trailing spaces in the filenames, along with a few other characters that are not allowed - seems to cause quite a bit of user friction at least with the non-tech guys that I work with who are confused about why OneDrive is one of the few file syncing clients that has these requirements....
I have had to deal with that nightmare multiple times this year! It was a real head scratcher at first.
Re: I'm “still afraid to use spaces in file names” years old
#104Earlier quoted context omitted.
I find this attitude misguided. More descriptive names are more ergonomic for things you only use rarely but they need to be combined with much better autocompletion than most shells provide by default.
You state that as if that were objective.. but that's not my subjective experience at all. Somehow I have a hard time remembering these long names, (is it --conf or --config or --config-file or --config-path? -c would've done it for me. --set or --set-prop or --set-property or --prop or --property?), and I need to look them up in a man page anyway, and I make more typos typing them, and shell completion rarely works…
I'm with you. Terseness is paramount.
I could never overcome my repulsion for Java and ObjC because of that. On the other hand, I fell at home with crazy RegEx that look like line noise to most people.
Re: I'm “still afraid to use spaces in file names” years old
#105Still way too many libraries and programs can't handle spaces in filenames. And shells and other programs still have problems with perfectly legal characters in filenames too, like '!' or ':'.
> 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.
Re: I'm “still afraid to use spaces in file names” years old
#106I work on a complex desktop application, and it's been astounding the number of bugs that have appeared over the years triggered by spaces and other unusual characters in file names. If you do anything with subprocesses or path processing, it's absurdly easy to hit in a thousand different ways, over and over again.
Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space and/or special characters in it.
Forces you to deal with this properly, and immediately ensures that every automated test checks this case without you having to remember every time. Hasn't been particularly inconvenient, since I'm autocompleting it 99% of the time anyway, and I haven't shipped a single path parsing bug since.
Re: I'm “still afraid to use spaces in file names” years old
#107I 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
Kebab case is the often overlooked benefit of prefix notation and semantic white space in programming languages. Honestly the best case of all cases imo.
Re: I'm “still afraid to use spaces in file names” years old
#108If I'm going to use the file in the command line, I won't use spaces, since I don't know what sick bug I might encounter.
[deleted]
Re: I'm “still afraid to use spaces in file names” years old
#109I had a guy in my team use forward slashes in filenames. Terrible idea, caused all sorts of weird issues.
Did you mean backslashes? I don't know if any filesystem/OS supports forward slashes in filenames
Re: I'm “still afraid to use spaces in file names” years old
#110Still way too many libraries and programs can't handle spaces in filenames. And shells and other programs still have problems with perfectly legal characters in filenames too, like '!' or ':'.
> Still way too many libraries and programs can't handle spaces in filenames.
"It's nothing."
"What do you mean?"
"It's nothing... It's empty space. I never taught the computer how to read empty space!"
"I never taught Virgil how to fly."