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

391–400 of 817 posts

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

#391

Post by terr-dav »

Macha wrote: post #260
Loughla wrote: post #232

Earlier quoted context omitted.

This legitimately made me laugh out loud in my office. The characters reach up off the screen as I reply to this. They overlay the comment above you. Amazing. How?

Interestingly I get different behaviour per browser/OS. Firefox/Linux clips it to the bounding box of the parent element, Firefox/Mac and Safari/Mac clip it to the line height, and only Chrome/Mac lets it extended further.

Firefox and Safari on iOS 15 both render all the glyphs attached to the base character. Vivaldi, Chrome and Firefox on Win10 all render them stacked and overlapping the parent and child comments.

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

#392

Post by SAI_Peregrinus »

branko_d wrote: post #131

I have an uneasy feeling whenever I see a path parameter declared as string. Path is not a string - it's a sequence of path components and should be treated as such by our APIs. A path should be parsed once - on user input - and then used in its "sequence form" throughout the software stack. And "path component" is not an arbitrary string either - e.g. appending a path component to the path should first require conve…

POSIX "Fully portable filenames" allow all characters except 0x2F (/) and 0x00 (NULL). That means file names can include line feeds, backspaces, EOF, etc.

"This is `a

perfectly vali'd.\010! file name\377, despite the weirdness"

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

#393

Post by apricot »

xdennis wrote: post #56
hdjjhhvvhga wrote: post #36

Earlier quoted context omitted.

So how did you deal with it in the 80s/90s?

As you would assume: use ASCII and deduce from context. Many people still do that. That has lead to phantom diacritics: reading letters in unfamiliar words/names based on what you assume they are. For example some pronounce Chirica as Chirică because they assume someone forgot to type the breve in ă.

I call it the habanero trap. There is no ñ in "habanero", yet a lot of people say "habanyero", probably by analogy with "jalapeño".

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

#394

Post by aranchelk »

emteycz wrote: post #339
0des wrote: post #320

Earlier quoted context omitted.

Behold! https://en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standar...

Yeah, except that tells me nothing useful... The question is exactly the same: So where do I install this random binary I downloaded from the internet or compiled myself? Is it /opt, /usr/bin, /usr/local/bin, or /bin? Where do I put the dependencies I compiled for this software - /usr/lib, /usr/local/lib, /lib, /opt/lib, /opt/ /lib, or what?

I was taught /usr/local/bin

/opt is for standalone packages, so if it’s a single file, no.

/bin is only for stuff needed on single user mode, so probably not (unless that’s what the binary is for.

/usr/bin is going to typically contain files installed by your package manager and should probably be left unaltered by human hands.

The deps I would assume /usr/local/lib but it hasn’t ever come up for me.

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

#396

Post by icedchai »

mikepurvis wrote: post #274
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.

Ugh, we have the 15 character Active Directory limit now with hostnames, and a previous IT administration has imposed a convention that every name had to follow [prod|dev]-[ph|vm]-[service]-[nn]. So basically every production service is prod-vm-owtf-01— you get exactly four characters to actually describe what the machine does. Works great when the service is "jira" or "wiki", but there are a lot that are pretty myst…

Do they at least allow you to set up CNAMEs?

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

#397

Post by rsync »

acme.sh - a shell script that I use to create "Let's Encrypt" SSL certificates - creates and maintains directories with asterisks in them:

https://github.com/acmesh-official/acme.sh/issues/1408

This is the sysadmin equivalent of piercing your nose just to make your parents mad.

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

#399

Post by nsv »

emteycz wrote: post #339
0des wrote: post #320

Earlier quoted context omitted.

Behold! https://en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standar...

Yeah, except that tells me nothing useful... The question is exactly the same: So where do I install this random binary I downloaded from the internet or compiled myself? Is it /opt, /usr/bin, /usr/local/bin, or /bin? Where do I put the dependencies I compiled for this software - /usr/lib, /usr/local/lib, /lib, /opt/lib, /opt/ /lib, or what?

To add: when you install software yourself you choose this, when your install software from e.g. a distribution package it is chosen by the package maintainers, and to a larger extent the maintainers of the distribution.

This is one of the big advantages of using a pre-made advantages of using a ready-made Linux distribution: beyond the convenience of having an installer or easy to install packages, you get some assurance that the system as a whole has been thoughtfully put together.

Arch Linux for example symlinks /bin and /sbin to /usr/bin and /lib to /usr/lib among other things.

Post reply on HN