Timeline for Is `echo $TEST` expanding an asterisk in the variable a bug? [duplicate]
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2024 at 9:52 | comment | added | MattBianco | Try the set -f (and set +f) options before/after the final echo to disable globbing/wildcard expansion if this behavior is unwanted. | |
| Jun 3, 2019 at 19:09 | history | duplicates list edited | ilkkachu | duplicates list edited from Why does my shell script choke on whitespace or other special characters?, Security implications of forgetting to quote a variable in bash/POSIX shells to When is double-quoting necessary?, Why does my shell script choke on whitespace or other special characters?, Security implications of forgetting to quote a variable in bash/POSIX shells | |
| Jun 3, 2019 at 19:08 | history | closed | muru Scott - Слава Україні ilkkachu bash Users with the bash badge or a synonym can single-handedly close bash questions as duplicates and reopen them as needed. | Duplicate of Why does my shell script choke on whitespace or other special characters?, Security implications of forgetting to quote a variable in bash/POSIX shells | |
| Jun 3, 2019 at 18:00 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 4.0 | edited tags; edited title |
| S Jun 3, 2019 at 16:31 | history | suggested | Maya | CC BY-SA 4.0 | improve title (question on HNQ) |
| Jun 3, 2019 at 15:47 | review | Suggested edits | |||
| S Jun 3, 2019 at 16:31 | |||||
| Jun 3, 2019 at 8:23 | history | became hot network question | |||
| Jun 3, 2019 at 4:28 | comment | added | Roel Van de Paar | @G-Man I did find DannyNiu's answer helpful in terms of the information provided, "just in case". | |
| Jun 3, 2019 at 4:26 | comment | added | G-Man Says 'Reinstate Monica' | @DannyNiu: Your comment is not very practical. Documents like POSIX and the Single Unix Specification do not consist of millions and millions of examples; they contain explanations (with, maybe, a few examples). Those documents are of little help to somebody who doesn’t understand what is happening and why; reading them is like learning to drive by reading a roadmap. And this question isn’t asking what to do. If you want to post a question, “What should I do if I’ve found a bug in a widely used software product?”, and post an answer, go ahead. | |
| Jun 3, 2019 at 1:38 | history | edited | Roel Van de Paar | CC BY-SA 4.0 | The other possible dup questions are long and very detailed. This one gives a quick overview of the input/outcome |
| Jun 3, 2019 at 1:36 | vote | accept | Roel Van de Paar | ||
| Jun 3, 2019 at 1:10 | comment | added | DannyNiu | General procedure when finding bugs in Unix: 1) Check out Single Unix Specification online for relevant definitions and rationales. 2) Submit a bugreport to austingroupbugs.net 3) Submit bugreport to the developer (with a patch if possible). | |
| Jun 3, 2019 at 0:40 | review | Close votes | |||
| Jun 3, 2019 at 19:10 | |||||
| Jun 3, 2019 at 0:22 | history | edited | muru | CC BY-SA 4.0 | edited body |
| Jun 3, 2019 at 0:22 | answer | added | Sparhawk | timeline score: 13 | |
| Jun 3, 2019 at 0:20 | review | First posts | |||
| Jun 3, 2019 at 1:26 | |||||
| Jun 3, 2019 at 0:16 | history | asked | Roel Van de Paar | CC BY-SA 4.0 |