Timeline for How to prevent bash command substitution output from being escaped?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2016 at 17:24 | history | undeleted | terdon♦ | ||
| Jun 15, 2016 at 12:50 | history | deleted | adonis | via Vote | |
| Oct 15, 2015 at 20:27 | comment | added | asmodean |
That makes a lot of sense now. The redirect tokens generated after the command is parsed don't mean anything special. I won't try to make that mistake again. Thanks for this answer! I feel I have a better understanding of what's going on now (as well as an obscure use-case for the evil eval comand.
|
|
| Oct 15, 2015 at 19:53 | history | edited | adonis | CC BY-SA 3.0 |
added 68 characters in body
|
| Oct 15, 2015 at 19:46 | history | answered | adonis | CC BY-SA 3.0 |