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

401–410 of 817 posts

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

#401

Post by biryani_chicken »

0des wrote: post #190
323 wrote: post #173

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

You don't even need to rearrange the folders themselves, just show them like that in the file explorer. Same way the windows explorer does.

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

#402

Post by numpad0 »

reaperducer wrote: post #288
echelon wrote: post #231

Earlier quoted context omitted.

Better solution: only allow ASCII, maybe dashes, and up to twelve characters. Problem solved. Enforce this in LDAP. Strict convention is better than flexibility and predicting obscure edge cases that can fail.

only allow ASCII, maybe dashes, and up to twelve characters. Problem solved ...and only hire people from the exact same background as you, who will never have unusual characters or accents in their name. And also make sure not to have any users who aren't exactly like you, and conform to this very narrow requirement. Surely, excluding 90% of the world won't hurt revenue in any way.

UTF-8 strings aren’t reproducible anyways. User ID should be strictly for identification, be alphanumeric random string if necessary.

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

#403

Post by drewzero1 »

emteycz wrote: post #349
db48x wrote: post #348

Earlier quoted context omitted.

Wherever you want. All of the above, or none. It really is up to you.

That's exactly the problem. This leads to mess. The Windows model of C:\Program Files\ is much better.

Okay, but what about ProgramData? I have enough programs that put their junk in there instead of Program Files, and others that make their own directories on the root of the drive (driver installers are really bad about this).

I think the best model I've seen for consistent binary locations is the 'Applications' folder in Mac OS X, but it fails as well by retaining the /usr/bin elsewhere.

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

#404

Post by dang »

throwaway2077 wrote: post #333
reaperducer wrote: post #281

Earlier quoted context omitted.

Or in my case, people for whom English is a second language, or have low education levels. Saying, "who can't understand..." is arrogant, selfish, and an example of why normal people hate people in the SV echo chamber.

SV echo chamber is on your side here - it is very in vogue to denounce anglocentrism. they were defending hieroglyphs and emoji in variable names in that thread about invisible javascript backdoor a day or two ago if you'd like a recent example

Could you please stop posting ideological battle comments to HN? We ban accounts that do that, regardless of their ideology, because it's (a) not what this site is for, and (b) destroys what it is for.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

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

#405

Post by [deleted] »

ridaj wrote: post #195
Izkata wrote: post #162

Earlier quoted context omitted.

> Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space and/or special characters in it. A former co-worker changed his name in our auth system to include an apostrophe, so that whenever we handled names wrong he'd find it.

Áčçëñts hęlp tóø

[deleted]

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

#406

Post by testplzignore »

zz865 wrote: post #187
ur-whale wrote: post #146

Earlier quoted context omitted.

> 2021-01-01 Yes on the date format. Saves you so much time.

Agreed on dates ordering problem but 20210101 is so much easier to type.

Years that end in a 1 are awful when doing this, especially in October and November. We've had 20211001, 20211010, 20211101, 20211110, and now today 20211111.

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

#407

Post by dang »

kingcharles wrote: post #212
TacticalCoder wrote: post #169

Define " space ". Is the Hangul filler we talked about yesterday a spacing character? Is the zero-width non-breaking space a spacing character? What about the typographic spacing characters? You should better be very afraid of using spaces in filenames. You should do everything you can to support them but you have to know you'll invariably encounter countless cases where you'll have this or that tool that won't work…

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

Please don't Zalgo on HN. It's enough to speak its name.

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

#408

Post by ziml77 »

grishka wrote: post #360
dhosek wrote: post #315

Earlier quoted context omitted.

The problem isn't the Cyrillic or the é but the fact that Windows lets you put those characters in file names in non-Unicode encodings which will create sequences of bytes which are invalid UTF-8. It's 2021, FFS, stop using legacy encodings.

All win32 functions that accept or return strings come in two varieties, with A and W suffixes, MessageBoxA/MessageBoxW. The A works with the system default 8-bit encoding (cp1251 in case of Cyrillic), the W works with unicode in wide chars. There shouldn't be much of a problem with string handling if you stick exclusively with W functions.

Using the W functions has been the advice from Microsoft's documentation for ages. But people still use the A functions because they're easier, especially when writing cross-platform software since Windows is the only major OS that made the unfortunate choice of having the base character type 16 bits wide.

Fortunately the future of the Windows API does look better since Microsoft has now added proper UTF-8 support since Win 10 1904. All you have to do is request it in the application manifest and the A functions will accept and return UTF-8.

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

#409

Post by zajio1am »

tambourine_man wrote: post #93
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 go one step further: 2021-11-11_client_project-name.ext 2021-11-11_client_projectName.ext is also OK. But underscore separates fields, hyphens for space replacement.

> But underscore separates fields, hyphens for space replacement

But why not the other way, hyphen-minus for separating fields and underscore for space replacement? That seems to me more consistent with how underscores and dashes are used.

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

#410

Post by NegativeLatency »

memsom wrote: post #237
shane_b wrote: post #220

Earlier quoted context omitted.

My Mac is formatted case sensitive when the default is case insensitive. This will also catch a ton of import related bugs. League of legends doesn’t run until I sed files for instance.

I once returned a printer because the Mac driver and support software expected and enforced case insensitive access and basically couldn't install properly on my case-sensitive HFS+ volume. It half installed and blatantly just didn't work in any way when installed.

Adobe software used to refuse to install on case sensitive file systems back in the not too distant past.
Post reply on HN