Consider not to suggest quoting HOME, UID, etc.

[forthrin]

For bugs

• Rule Id: SC2086
• My shellcheck version: 0.9.0
• The rule's wiki page does not already cover this (e.g. https://shellcheck.net/wiki/SC2086)
• I tried on https://www.shellcheck.net/ and verified that this is still a problem on the latest commit

Here's a snippet or screenshot that shows the problem:

#!/bin/bash
touch /var/mail/$USER

Here's what shellcheck currently says:

SC2086 Double quote to prevent globbing and word splitting.

Here's what I wanted or expected to see:

Should this check be lenient on standard environment variables that won't have problematic characters in any sane environment? (HOME UID LOGNAME RANDOM COLUMNS LINES, etc.). touch /var/mail/"$USER" seems a bit redundant.

[brother]

$ echo $HOME
/home/brother
$ mkdir "/tmp/apa gnu"
$ unset HOME
$ export HOME=/tmp/apa\ gnu/
$ echo $HOME 
/tmp/apa gnu/
$ cd $HOME
bash: cd: too many arguments
$ pwd
/home/brother
$ cd "$HOME"
$ pwd
/tmp/apa gnu

[forthrin]

Which is exactly why I wrote "sane environment".

[brother]

And the point is that you can not dictate what that is.

[forthrin]

Typiskt svenskt

[Atrate]

If anything, it will get you into the good habit of always quoting variables, and in this case it has no downside.