7x31/shellcheck
1
0
Fork 0
mirror of https://github.com/koalaman/shellcheck.git synced 2025-10-03 19:29:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated SC2097 (markdown)

koalaman
2018-01-19 18:49:42 -08:00
parent 0a243b74c1
commit bd16bbdb90
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
SC2097.md

@@ -33,3 +33,8 @@ The solution is to set the variable and export the variable first. If limited sc
### Exceptions ### Exceptions
In the strange and fabricated scenarios where the script and a program uses a variable name for two different purposes, you can ignore this message. This is hard to conceive, since scripts should use lowercase variable names specifically to avoid collisions with the environment. In the strange and fabricated scenarios where the script and a program uses a variable name for two different purposes, you can ignore this message. This is hard to conceive, since scripts should use lowercase variable names specifically to avoid collisions with the environment.
### Related resources:
* [BashFaq: Why doesn't foo=bar echo "$foo" print bar?](https://mywiki.wooledge.org/BashFAQ/104)
* [StackOverflow: Prefixing variable assignment doesn't work with echo](https://stackoverflow.com/questions/36380569/prefixing-variable-assignment-doesnt-work-with-echo?rq=1)