From f218532cb79d37a990ad2af76c3aec28663d6405 Mon Sep 17 00:00:00 2001 From: koalaman Date: Fri, 19 Jan 2018 18:10:19 -0800 Subject: [PATCH] Updated SC2209 (markdown) --- SC2209.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/SC2209.md b/SC2209.md index d958bf7..8a28b80 100644 --- a/SC2209.md +++ b/SC2209.md @@ -28,4 +28,9 @@ None. Quoting a single command (as in `PAGER="cat"` above) doesn't change how the script works. It's purely to show shellcheck (and humans) that a literal assignment of a command name is intentional. -This warning triggers generally when a variable is assigned an unquoted command name (from a list of hard coded names). See related warning [[SC2037]] which detects the same kind of error through the patterns `var=value -flag` and `var=value *glob*`. \ No newline at end of file +This warning triggers generally when a variable is assigned an unquoted command name (from a list of hard coded names). See related warning [[SC2037]] which detects the same kind of error through the patterns `var=value -flag` and `var=value *glob*`. + +### Other resources: + +* [BashFaq: How can I store the return value and/or output of a command in a variable?](https://mywiki.wooledge.org/BashFAQ/002) +* [StackOverflow: How to set a variable to the output from a command in Bash](https://stackoverflow.com/questions/4651437/how-to-set-a-variable-to-the-output-from-a-command-in-bash) \ No newline at end of file