Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

twitter.com

Post reply on HN
Print view View original

261–270 of 817 posts

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

#261

Post by grishka »

hnuser847 wrote: post #227
kingcharles wrote: post #212

Earlier quoted context omitted.

You get all those space characters working and then some jerk comes along and uploads a file like this: ŗ̶̧̢͓̳͍͙͔̳̻̥͉̭͓̫̟͍̞̭͉͓͉̮̹͍͚̳̹̬͉͚̰͈̘̐̊̾̈̀̒͒̀͛̓̋̔͊̏͘̚ę̴̨̛̣͙̤̟̬̩̟͙͖̥̹̱̱̊͑͗̇̇͛̆̈́̃͋̓̀̔̍̍̌̐͊̎̓̅̀̕ͅģ̴̹̜̘͍̱̑͐̉̌̐̄̊͛̎́̐̌̅̈́͂͑̈́̋̔͂̊̊̒̒̔͛͆̚͘̕͠e̶̙͕̫̳̘͐̾́̑͆̓͂̿͊̊̍͛͐̌̆͗̌̅̅̔͊̂͛͗̅̕͝͝͝͝x̵̢̧̦̫͖̝̥̹͓̬͖̤̩͚̝̫̋̃̅̈́̆͋̌͑́̎̈́̊̾͒̀̒̎̓͛͊̿̓͊̀̍͐̆̚͝͝-̴̨̮̯͖͖̠̜̲̪͕̘͈͖̮̈́̓̐̃́̅̄̏́̍̉̐͌́̔̓̄͋͗̐̕͜͝ţ̴̢̧̖̗͖̞̮̫̦̼̝̺̼̱̳͓͉̜̟̤̲͖̻͙́̌̈̌̈͆̾̄͊̿̏̓͗̈́̕͜ͅh̶̽́͊̎͐͌̆̍̎̏̕͝…

Honest question - what the heck are those characters?

Combining diacritic marks.

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

#262

Post by discreteevent »

jonnycomputer wrote: post #197
hardwaresofton wrote: post #87

I 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

I've recently shifted sharply toward the dash from the underscore. I find it more readable, and it doesn't require the shift key. However, I do find it useful to use underscores to create groups, e.g. test-001_2021-10-11.log. Including hours, minutes, seconds is still awkward.

There's a customer for everything. I've just never liked the aesthetics of the underscore. Also if your underscored thing gets put in some document and then underlined the underscores can become invisible.

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

#264

Post by eCa »

kibwen wrote: post #128
ModernMech wrote: post #107

Earlier quoted context omitted.

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.

One glorious day we'll accept programming languages that require spaces around infix arithmetic operators so that we can make kebab case a reality!

Maybe Raku[1] is for you!

[1] https://raku.guide/#_syntax_overview (see section 1.7.1)

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

#265

Post by inanutshellus »

sodapopcan wrote: post #191
jjoonathan wrote: post #140

Earlier quoted context omitted.

> kebab-case I hadn't heard that before and I love it.

If you hadn't heard kebob-case called that before there's a chance you haven't heard SCREAMING_SNAKE_CASE called that before, and I couldn't live myself if I didn't let you know.

that's hilarious, thanks for sharing that.

Perennially relevant xkcd: https://xkcd.com/1053/

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

#266

Post by [deleted] »

Asraelite wrote: post #209
jjoonathan wrote: post #140

Earlier quoted context omitted.

> kebab-case I hadn't heard that before and I love it.

Google considers it too violent apparently. In one of their recent changes to their style guide, they started recommending "dash-case" instead. https://developers.google.com/style/word-list#letter-k

[deleted]

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

#267

Post by philote »

jerf wrote: post #138
ReleaseCandidat wrote: post #95

Still 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 ':'.

Was recently encoding my Stargate: SG-1 DVDs to move them to plex. I was encoding it on a system other than what was serving it, so I had to copy it. It's surprisingly difficult to "scp" a file with a colon in it directly. I also love when you're using bash and you have a file with ! in the name, and you accidentally fail to correctly backslash it, you not only get "bash: !rest_of_filename: event not found", but it a…

Can't you usually just put quotes around the filename and/or path to prevent all those issues?

Edit: nope, just tried it and scp still sees the quoted filename as a host + path

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

#268

Post by Valgrim »

hnuser847 wrote: post #227
kingcharles wrote: post #212

Earlier quoted context omitted.

You get all those space characters working and then some jerk comes along and uploads a file like this: ŗ̶̧̢͓̳͍͙͔̳̻̥͉̭͓̫̟͍̞̭͉͓͉̮̹͍͚̳̹̬͉͚̰͈̘̐̊̾̈̀̒͒̀͛̓̋̔͊̏͘̚ę̴̨̛̣͙̤̟̬̩̟͙͖̥̹̱̱̊͑͗̇̇͛̆̈́̃͋̓̀̔̍̍̌̐͊̎̓̅̀̕ͅģ̴̹̜̘͍̱̑͐̉̌̐̄̊͛̎́̐̌̅̈́͂͑̈́̋̔͂̊̊̒̒̔͛͆̚͘̕͠e̶̙͕̫̳̘͐̾́̑͆̓͂̿͊̊̍͛͐̌̆͗̌̅̅̔͊̂͛͗̅̕͝͝͝͝x̵̢̧̦̫͖̝̥̹͓̬͖̤̩͚̝̫̋̃̅̈́̆͋̌͑́̎̈́̊̾͒̀̒̎̓͛͊̿̓͊̀̍͐̆̚͝͝-̴̨̮̯͖͖̠̜̲̪͕̘͈͖̮̈́̓̐̃́̅̄̏́̍̉̐͌́̔̓̄͋͗̐̕͜͝ţ̴̢̧̖̗͖̞̮̫̦̼̝̺̼̱̳͓͉̜̟̤̲͖̻͙́̌̈̌̈͆̾̄͊̿̏̓͗̈́̕͜ͅh̶̽́͊̎͐͌̆̍̎̏̕͝…

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...

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

#269

Post by Joker_vD »

exciteabletom wrote: post #182
dale_glass wrote: post #158

Earlier quoted context omitted.

Microsoft is in full control of the Windows kernel, so they can make it care about whatever they want to, and one would think better argument passing would be a nice quality of life improvement. Less nonsense for developers to deal with, and less weird bugs on the platform.

Sure, but MS values backwards compatibility a lot. They aren't going to break existing API or bloat the kernel with a bunch of functions that do the same thing.

They can either add a new API which almost nobody would use ― because everyone already learned to use the existing one and either reused or reimplemented the MSVCRT's logic so that most of the software parse the command lines the same way; or they can literally break every single program in existence by breaking the interface of CreateProcess ― which is just as likely as Linux breaking the interface of execve(2).

Giving CreateProcess a new flag so it would to correctly accept "path\\to\\my\\program.exe\0arg_1\0second argument\0argument with literal \" symbol" (with an implicit \0 terminating it) as lpszCmdLine is an easy part; the hard part would be forcing everyone to switch to using it.

Also, I'm pretty certain this processing happens in the user space, and Win32 API is already bloated beyond any belief.

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

#270

Post by reaperducer »

Spaces are still not "permitted" in URLs.

Browsers will take http://example.com/some name.pdf and automagically turn it into http://example.com/some%20name.pdf, and deliver the goods without a problem. But having that space in the URL is still out of spec, and will cause your web page to fail validation, even though it works fine.

Post reply on HN