Live data from Hacker News

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

twitter.com

381–390 of 817 posts

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

#381

Earlier quoted context omitted.

That order is not guaranteed consistent across installations, however.

I wonder if code to this effect has ever been written before for (int i = 1; i

For whatever it’s worth, this is a terrible idea, for so many different reasons:

https://web.archive.org/web/20100107184218/http://blogs.msdn...

And so, yes, I’m certain someone must have done it, because it’s clearly bad idea jeans and so Murphy’s Law says it must exist.

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

#382

Earlier quoted context omitted.

Honest question - what the heck are those characters?

In digital typography, combining characters are characters that are intended to modify other characters. The most common combining characters in the Latin script are the combining diacritical marks (including combining accents). https://en.wikipedia.org/wiki/Combining_character

Specifically _Vietnamese_ combining characters. The Vietnamese writing system uses multiple combining characters at a time, and stacks them vertically. Throw in a few that wrap around the character like t҉his, some 𝑎lternatᵉ lꬲttꬲr fᵒrms, disturbing imagery, and perhaps a few other tricks, and you have zalgo. See also https://stackoverflow.com/a/1732454/823846

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

#383

Earlier quoted context omitted.

And that, children, is when marginalia_nu unlocked the seventh circle of the inferno. Tomorrow we'll read the story of how our new demon overlords forced us all back to Windows 3.1.

Win 3.1? on DOS 6.22? Actually, this sounds like heaven. Just don't put it on the public 'tubes.

Or do. Can’t hack a Mac Classic web server!

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

#384

Earlier quoted context omitted.

On POSIX systems file names are not strings, they are sequences of bytes. They might not be UTF-8 or have any meaning. Python3 had to hack around this, they thought they could force everything to Unicode and discovered that doesn't work.

Which makes for fun issues like there's no standard way to display a filename in Unix. A system that's, you know, all about files.

Unix: everything is a file, including file names!

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

#386
That's funny because the first operating system I used (Apple DOS 3.3) was very liberal about file names. There was a 30-character limit which was a lot, and it didn't mind spaces in file names. Even control characters were fair game, which made things fun when you accidentally inserted a ^A in a SAVE command.

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

#387
post #354

Earlier quoted context omitted.

No, it frees you to pick whatever unmessy solution you want. You can do `configure --prefix=/Program\ Files/ ` if you want.

If I am not writing all of my installation scripts by hand, because that would be really intense, then every folder gets filled with random bits of software. Offering too many similar choices leads to mess. There's nothing fundamentally different between using one or more of these options and using the only option, except that in the second case there isn't any opportunity to make mess. > You can do `configure --pref…

> then every folder gets filled with random bits of software.

What does that even mean? When you install something, you put it where you want it.

If you don’t like where your distribution puts files, choose a different one. Not all of them use the same convention.

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

#388

Earlier quoted context omitted.

GoboLinux does exactly that: https://en.m.wikipedia.org/wiki/GoboLinux

How do you deal with lack of being able to just point to "/usr/lib/include" or other things when saying "here's my directory of shared libs"? This is definitely interesting though, and an improvement I would say

GoboLinux symlinks everything into an FHS-ish structure under /System/Index/ so you still have a single place where binaries/libraries/includes/etc. live. (There are also symlinks from /usr/lib, /usr/bin, and others into /System/Index/ for compatibility with programs where those might be hardcoded.)

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

#389

Earlier quoted context omitted.

This goes for most instances of user input. Timestamps is the other common one people get wrong. I've even seen programs that pass around timestamps as strings in multiple formats and as integers (Unix time).

As a programming noob, I'm wondering what would be the better way to pass or return a unix time value as opposed to an integer?

Depends on the language but most high-level languages have a timestamp or datetime abstraction which you should be using.
Post reply on HN