Timeline for Why does bash add single quotes to unquoted failed pathname expansions in a command before executing it?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2021 at 12:43 | history | edited | Kusalananda♦ | CC BY-SA 4.0 | Added full list of meta characters that causes quoting. This is taken from current bash sources. |
| Jan 22, 2018 at 22:28 | history | edited | Mark Plotnick | CC BY-SA 3.0 | added 29 characters in body |
| Mar 11, 2014 at 16:14 | history | bounty awarded | CommunityBot | ||
| Mar 7, 2014 at 16:01 | history | edited | Mark Plotnick | CC BY-SA 3.0 | added 24 characters in body |
| Mar 7, 2014 at 7:38 | history | edited | Mark Plotnick | CC BY-SA 3.0 | added 3 characters in body |
| Mar 6, 2014 at 23:27 | vote | accept | CommunityBot | moved from User.Id=44370 by developer User.Id=5973 | |
| Mar 6, 2014 at 23:27 | comment | added | user44370 | Thank you! You read in my desire to figure out in this particular case if the quotes were the result of shell syntax (and nowhere in the bash manual is it said that a word is returned quoted when expansion fails in this context) or of the C program that implements it. A subset of the latter as it turns out. Seems like C will be required reading... | |
| Mar 6, 2014 at 17:04 | history | answered | Mark Plotnick | CC BY-SA 3.0 |