Timeline for find with -exec eval of $0 [duplicate]
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2015 at 19:33 | history | closed | Stéphane Chazelas cuonglm dhag don_crissti Anthon | Duplicate of Bash -c with positional parameters | |
| May 12, 2015 at 18:38 | history | edited | cuonglm | CC BY-SA 3.0 | added 22 characters in body; edited tags |
| May 12, 2015 at 15:48 | review | Close votes | |||
| May 12, 2015 at 19:33 | |||||
| May 12, 2015 at 14:49 | comment | added | Gregg Leventhal | I don't want that behavior, I find this more useful, but I expected the behavior typically found when using $0 in a shell script where $0 represents the script itself. I was curious how it was working, not wishing it worked differently. | |
| May 12, 2015 at 14:47 | vote | accept | Gregg Leventhal | ||
| May 12, 2015 at 14:42 | comment | added | Stéphane Chazelas | I'd understand why you'd want $0 to expand to bash, but not echo. Do you expect rm "$0" to attempt to remove rm? See also unix.stackexchange.com/q/140779 and unix.stackexchange.com/q/152391 | |
| May 12, 2015 at 14:41 | answer | added | Dubu | timeline score: 3 | |
| May 12, 2015 at 14:30 | history | asked | Gregg Leventhal | CC BY-SA 3.0 |