README: Add quoting around brackets #18
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Brackets are shell wildcard special characters and if there are no files `301` or `302` in the current directory, the command `hc 30[12]` will fail if e.g. bash's shell option `failglob` is set: ``` $ hc 30[12] bash: no match: 30[12] ``` Even worse: Independent of that shell option this command will yield different outcomes depending which files or directories exist in the current directory: ``` $ hc 30[12] Status code 301 Message: Moved Permanently Code explanation: Object moved permanently -- see URI list Status code 302 Message: Found Code explanation: Object moved temporarily -- see URI list $ touch 302 $ hc 30[12] Status code 302 Message: Found Code explanation: Object moved temporarily -- see URI list $ ``` The proper fix is to quote the argument containing the brackets.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brackets are shell wildcard special characters and if there are no files
301or302in the current directory, the commandhc 30[12]will fail if e.g. bash's shell optionfailglobis set:Even worse: Independent of that shell option this command will yield different outcomes depending which files or directories exist in the current directory:
The proper fix is to quote the argument containing the brackets.