Timeline for Why does the exclamation mark `!` sometimes upset bash?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2021 at 13:28 | history | edited | ilkkachu | CC BY-SA 4.0 | added 47 characters in body |
| Dec 16, 2017 at 11:00 | review | Suggested edits | |||
| Dec 16, 2017 at 11:27 | |||||
| Aug 23, 2011 at 13:30 | comment | added | Peter.O | .. Yes undestood. I was aware of nesting quotes within quotes... My misunderstanding was that I thought that the code within the brackets of the command substitution would be parsed seperately, to what surrounds those brackets; but apparently not.. thanks. | |
| Aug 23, 2011 at 13:24 | vote | accept | Peter.O | ||
| Aug 23, 2011 at 13:12 | comment | added | Caleb | Quoting is confusing enough in bash without it changing in nested strings. As it is, the replacements happen very early on in the process. Consider this example: var=word; echo "test '$var'"; echo 'test "$var"' | |
| Aug 23, 2011 at 13:04 | history | edited | Caleb | CC BY-SA 3.0 | added 734 characters in body |
| Aug 23, 2011 at 13:01 | comment | added | Peter.O | Thanks Caleb.. Another of my pre-conceptions dismissed... I thought that bash parsing was done from the innermost bracket or brace, and then worked outwards... It seems that bash parses differently to my assumption. | |
| Aug 23, 2011 at 12:36 | history | answered | Caleb | CC BY-SA 3.0 |