When I run echo "abc" in my shell, the program echo really only "sees" abc as the parameter value, right? Because the double quotes are a shell feature (described in 2.2.3 Double-Quotes for the POSIX shell) and not literals. Is that correct?
@jesse_b Alright thanks! :) I'm taking baby steps here, so I don't make a mistake. So, reading the last paragraph of 2.2.3 Double-Quotes, it says that the backslash can be used as an escape character when followed by a double quote for example. According to 2.2.1, the escape character preserves "the literal value of the following character". So I think in addition to your suggestions, I could also use echo "\"abc\""?
The different between echo \"abc\" and echo "\"abc\"" is that the string "abc" is quoted in the latter example. With this particular string, it makes no difference whether the string is quoted or not.
Okay, so one final question to see if I understand everything now. echo \" will see " and print ", echo "\"" will see " and print ", however echo \\\" (and therefore also echo "\\\"") will see \" and is therefore undefined, yes?
I didn't mean "undefined" like that. I just meant it like "the specific behavior is not written in POSIX because they refer to the implementation manual"
@jesse_b "The swarms were placed at the entrances of the logic gates and encouraged to move by a shadow intended to convince the crabs that there was a predatory bird overhead."
This means it's a shadow-powered computer, not a crab-powered one.
@jesse_b I interact via the input device. I don't run the computer via my keyboard.
I mean, I don't use my fingers to tell the computer to light up individual pixels of the screen in patterns that make up letters that, in turn, make up the new email that just arrived. Making crabs run in certain directions and calling it a computer is like writing "100111001" on a piece of paper and calling it memory.
