Timeline for When is double-quoting necessary?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2016 at 3:24 | comment | added | Charles Duffy | As an aside -- all-caps variable names are used by variables with meaning to the operating system and shell; the POSIX specification explicitly advises using lower-case names for application defined variables. (While the specification quoted is specifically focusing on environment variables, environment variables and shell variables share a namespace: Attempting to create a shell variable with a name already used by an environment variable overwrites the latter). See pubs.opengroup.org/onlinepubs/009695399/basedefs/…, fourth paragraph. | |
| Dec 6, 2014 at 16:48 | vote | accept | kjo | ||
| Dec 6, 2014 at 16:46 | history | edited | kjo | CC BY-SA 3.0 | added 2 characters in body |
| Dec 3, 2014 at 22:07 | comment | added | Stéphane Chazelas | See also Security implications of forgetting to quote a variable in bash/POSIX shells | |
| Mar 22, 2013 at 16:05 | history | edited | vonbrand | CC BY-SA 3.0 | Title capitalization |
| Mar 22, 2013 at 0:28 | answer | added | Gilles 'SO- stop being evil' | timeline score: 215 | |
| Mar 21, 2013 at 16:46 | history | tweeted | twitter.com/#!/StackUnix/status/314779944628670464 | ||
| Mar 21, 2013 at 16:28 | history | edited | kjo | CC BY-SA 3.0 | added 7 characters in body |
| Mar 21, 2013 at 15:06 | comment | added | Ulrich Dangel | Your observed behaviour in zsh depends on the settings and is influenced by the SH_WORD_SPLIT option. | |
| Mar 21, 2013 at 14:37 | history | asked | kjo | CC BY-SA 3.0 |