I can play instruments but never thought I could sing outside a range of less than an octave in the baritone range.
When I was 50 we had a singing teacher over at our house for my children. I asked if she could help my range. That day she took my voice to a high C. I am actually a tenor and can sing pretty much all the high parts. I am my in-laws’ favorite opera singer now.
Also I was too timid. Singing is really just controlled shouting.
It's not a completely non special character: for instance in bash it's special inside braces in the syntax where "/{,usr/}bin" expands to "/bin /usr/bin". But the need to start that syntax with the open brace will remind you about the need to escape a literal comma there if you ever want one.
My introduction to RCS was indeed spurred by a command typo!
I was learning Pascal on AT&T 3B2 systems. They were running SVR3. Perfectly normal clustered systems with nifty things like RFS. We were all logged in via dumb terminals, and the machines were sequestered on another floor. I had pictured them as big, really big. But 3B2s were not.
Anyway, our first lessons were how to use the Bourne shell and how to use "vi" to edit our source code.
I had learned to type 4 years previously, so I was already fast and fearsomely accurate. But I still made mistakes.
So one day I typed "ci filename.p" and then I had an hour's worth of sheer horror!
"ci" had not spawned the visual editor as I had hoped, but it did something inexplicable to that file! It had renamed it to "filename.p,v" and had put a bunch of garbage into it!
I can't remember how much "RCS garbage" was inserted, or how much cleanup I needed to do. For some reason, our TA/lab assistants were not available for me to ask! I was in a cold sweat, because all my hard classwork had been utterly mangled by this unfeeling machine, and I didn't know how to effectively undo it.
Eventually I learned about the RCS system, and what those curious "$...$" symbols meant, and I think I worked out a way to "undo" it (which I think consisted of merely "co" to checkout the file again.)
But it was a rude awakening to the fact that simple command-line typos could have some very unintended consequences!
Oh, that might be true, I do remember encountering some escaping issues when creating a more complex POSIX (or bash) script that involved lists and iterating through stuff.
I see Bash only uses commas in Brace expansions:
file{1,2,3}.txt
# file1.txt file2.txt file3.txt
I guess it would only be a problem if you want to expand
I think watching children being butchered or prisoners being tortured to death could be equally or more traumatic. Killing in processing animals is at least socially acceptable and (arguably) necessary for survival.
Because when I’m running a busy site and I can’t figure out what went wrong, I freak out. I don’t know whether the problem will take 2 hours or 2 days to diagnose.
I am pretty forward-thinking but even when I started writing my first web server 30+ years ago I didn’t foresee the day when the phrase “my bookie’s datacenter” might cross my lips.
New fear unlocked
reply