Clarify Command Prompt support for WinGet configuration - #4049
Open
白瑾 (BaiJin0224) wants to merge 1 commit into
Open
Clarify Command Prompt support for WinGet configuration#4049白瑾 (BaiJin0224) wants to merge 1 commit into
白瑾 (BaiJin0224) wants to merge 1 commit into
Conversation
Contributor
|
白瑾 (@BaiJin0224) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
白瑾 (@BaiJin0224) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit a01f19a: ✅ Validation status: passed
For more details, please refer to the build report. |
4 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Update the WinGet configuration command to use double quotes and clarify that it can be run in either PowerShell or Command Prompt.
Details
The current command uses PowerShell-style single quotes around the configuration file URL. In Command Prompt, the single quotes are passed as part of the file path, causing WinGet to report that the file does not exist.
Double quotes work correctly in both PowerShell and Command Prompt.
Testing
Tested the updated
winget configurecommand in both PowerShell and Command Prompt.