Earlier quoted context omitted.
They used to. The folder was called `Documents and Settings` until Win7.
"Documents and Settings" still exists on Windows 10, as a soft link to "Users".
I'm “still afraid to use spaces in file names” years old
441–450 of 817 posts
Re: I'm “still afraid to use spaces in file names” years old
#442Re: I'm “still afraid to use spaces in file names” years old
#443I have an overly-aggressive function in my .bashrc to rename all files in the current directory: # Rename all files in a directory rn() { rename "s/ /-/g" * rename "s/_/-/g" * rename "s/–/-/g" * rename "s/://g" * rename "s/\(//g" * rename "s/\)//g" * rename "s/\[//g" * rename "s/\]//g" * rename 's/"//g' * rename "s/'//g" * rename "s/,//g" * rename "y/A-Z/a-z/" * rename "s/---/--/g" * rename "s/---/--/g" * } I use th…
Re: I'm “still afraid to use spaces in file names” years old
#444Earlier quoted context omitted.
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.
But Hacker News should do something about all of the anti-bitcoin and anti-anti-nuclear ideologies running around in here.
I don't really mind it that much but it'd be nice, it's really the only 2 extremisms I've experienced here, all other subjects are discussed in a fair manner.
Re: I'm “still afraid to use spaces in file names” years old
#445Re: I'm “still afraid to use spaces in file names” years old
#446Re: I'm “still afraid to use spaces in file names” years old
#447Re: I'm “still afraid to use spaces in file names” years old
#448Earlier quoted context omitted.
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
"Does foo:bar refer to the local file `foo:bar' (size: 102kB, date: 2021-11-11) or to the file `bar' on host `foo' (FQDN: foo.example.com, IP address: 1.2.3.4)?
1: local file `foo:bar'
2: file `bar' on remote host `foo'
Your selection: "
Re: I'm “still afraid to use spaces in file names” years old
#449Earlier 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?
If you expect other users to be able to execute the program, then you should put it in either `/usr/bin` or `/usr/local/bin`, depending on whether the former is already being used by a package manager. `/opt` is generally for self-contained software that doesn't play nicely with the rest of the system, but might still be installable through the default package manager.