Timeline for Escape a variable for use as content of another script
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2024 at 7:42 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | missing quotes around $#. Clarify what the relation to IFS is. |
| Jun 14, 2024 at 2:32 | history | edited | Walf | CC BY-SA 4.0 | Update |
| Nov 21, 2023 at 5:24 | history | edited | Walf | CC BY-SA 4.0 | Point to current solution and add slight improvement |
| Jun 9, 2021 at 2:47 | history | edited | Walf | CC BY-SA 4.0 | mitigate bash version differences |
| Jun 25, 2020 at 4:34 | comment | added | Walf | @portforwardpodcast The plural on the latter version is deliberate because the "$@" is used to expand and escape all arguments passed, unlike the former which only escapes the first argument and drops any others. Your comment did prompt be to check it and it was not separating them properly, so thanks. | |
| Jun 25, 2020 at 4:26 | history | edited | Walf | CC BY-SA 4.0 | Fix unintended concatenation of arguments |
| Jun 24, 2020 at 21:30 | comment | added | benathon | The function should be esc_var and not esc_vars I know it's a small edit, and of course I would edit it myself, but I can't do single character edits | |
| Dec 12, 2019 at 8:32 | history | edited | Walf | CC BY-SA 4.0 | practical example of other solutrion |
| Aug 1, 2018 at 6:06 | history | edited | Walf | CC BY-SA 4.0 | show practical usage |
| Jul 26, 2017 at 1:34 | vote | accept | Walf | ||
| Jun 9, 2021 at 2:59 | |||||
| Jul 18, 2017 at 5:14 | history | answered | Walf | CC BY-SA 3.0 |