git config commands need double quotes instead of single quotes #221
Conversation
This file contains 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
You might want to test this on other devices/OSs, and if this doesn't work across the board then there should be a note that different quotes are needed based on your OS. I'm on a freshly reformatted Windows 10 Pro, using the classic Windows Command Prompt, and I noticed that when using single quotes, the value gets cut off at whitespace: ```cmd C:\Users\Dean>git config --global user.name 'Jane Doe' C:\Users\Dean>git config --global --list user.name='Jane C:\Users\Dean>git config --global --unset-all user.name C:\Users\Dean>git config --global user.name "Jane Doe" C:\Users\Dean>git config --global --list user.name=Jane Doe ```
|
Interesting! Double is fine with me, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
You might want to test this on other devices/OSs, and if this doesn't work across the board then there should be a note that different quotes are needed based on your OS.
I'm on a freshly reformatted Windows 10 Pro, using the classic Windows Command Prompt, and I noticed that when using single quotes, the value gets cut off at whitespace: