Live data from Hacker News

I'm “still afraid to use spaces in file names” years old

twitter.com

11–20 of 817 posts

Re: I'm “still afraid to use spaces in file names” years old

#15
post #5

Slightly off topic but I find myself stuck at being "please for the love of god don't use spaces in git branch names" old. Anno dazumal this might not even have been an issue and I'm just cargo culting.

And on that topic, git branches are case sensitive but windows filesystem API isn't. Git branches are materialized on the filesystem as files and directories.

Re: I'm “still afraid to use spaces in file names” years old

#16

ascii, no spaces for me i still get issues with old one-off scripts, that still work, and I forgot to properly quote stuff... plus the urls are pain in the ass with the %20;s.

[0-9A-Za-z_-]+ for me.

Same here and most of the time it's even just [0-9a-z_]+ It's simple and there are no suprises around the corner

Re: I'm “still afraid to use spaces in file names” years old

#17
I'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 verboten.

Re: I'm “still afraid to use spaces in file names” years old

#18
I don't use spaces because it's so much faster to type filenames out (including with TAB-completion) in the terminal.

I do, however, use Cyrillic (UTF-8) in filenames, and I regularly try out if moving a file into ASCII-path will let some programs open it (half the time it's that when I am having trouble).

Post reply on HN