Timeline for How do I echo a string with multiple spaces in bash "untouched"?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2017 at 13:26 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 | avoid variable data in the format argument to `printf`. Clarifications/corrections |
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| Apr 1, 2016 at 15:10 | history | edited | techraf | CC BY-SA 3.0 | added 224 characters in body |
| Apr 1, 2016 at 14:53 | history | edited | techraf | CC BY-SA 3.0 | added 1 character in body |
| Apr 1, 2016 at 14:51 | comment | added | glenn jackman | printf is "better" if you use it properly: you need to write printf "blah%sblah\n" "$MYCUSTOMTAB" -- if the variable contains any %s, %d, etc, you'll get the wrong output otherwise. | |
| Apr 1, 2016 at 14:50 | comment | added | Wouter Verhelst | While strictly true, the cause here is totally unrelated to the difference between printf and echo. While printf is certainly more portable and has some upsides, its major downside is that it is ugly and unreadable, and way more difficult to understand. | |
| Apr 1, 2016 at 14:46 | history | undeleted | techraf | ||
| Apr 1, 2016 at 14:46 | history | deleted | techraf | via Vote | |
| Apr 1, 2016 at 14:45 | history | answered | techraf | CC BY-SA 3.0 |