You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a snippet or screenshot that shows the problem:
# shellcheck=bash
ping -M do localhost
Here's what shellcheck currently says:
Line 2 SC1010: Use semicolon or linefeed before 'do' (or quote to make it literal).
Here's what I wanted or expected to see:
No error at all, as the 'do' here is a valid hint for ping and should not be interpreted by ShellCheck.
TODO: Describe expected/desired output
This is similar to issues #1801 and #1809.
1801 was not fixed, as that was related to a non-standard utility.
1809 was fixed.
This one is using ping, which is IMO a standard utility. The -M parameter specifies how ping should handle MTU path discovery. It can be passed three possible hints:
do
want
dont
The workaround of quoting the do-HINT does work, but without further explanation, it will not be clear to another developer why that was done, as it doesn't make sense in the context of the parameters to the ping command.
The text was updated successfully, but these errors were encountered:
For bugs
shellcheck --version
or 'online'): onlineFor new checks and feature suggestions
Here's a snippet or screenshot that shows the problem:
Here's what shellcheck currently says:
Here's what I wanted or expected to see:
No error at all, as the 'do' here is a valid hint for ping and should not be interpreted by ShellCheck.
TODO: Describe expected/desired output
This is similar to issues #1801 and #1809.
1801 was not fixed, as that was related to a non-standard utility.
1809 was fixed.
This one is using ping, which is IMO a standard utility. The -M parameter specifies how ping should handle MTU path discovery. It can be passed three possible hints:
do
want
dont
See: https://linux.die.net/man/8/ping
The workaround of quoting the do-HINT does work, but without further explanation, it will not be clear to another developer why that was done, as it doesn't make sense in the context of the parameters to the ping command.
The text was updated successfully, but these errors were encountered: