Skip to content

Conversation

@carlos-zamora
Copy link
Member

Makes the WinGet search more strict in that it only searches for a strict match by command. This removes the blocking calls from various searches, which was the root cause of #24.

This also prevents the scenario where a package is suggested, but the newly installed package doesn't actually fix the issue of a command not being found. In searching only by command, the newly installed package is guaranteed to introduce the missing command unless the WinGet package catalog was wrong.

Additionally, the catch block was updated to remove the known MSIX issue, which has now been fixed. Instead, we display the caught exception. This should help further debug issues like #23.

Closes #13
Closes #24

@carlos-zamora
Copy link
Member Author

Note for me: the Terminal CNF should also be updated

@DHowett
Copy link
Member

DHowett commented Oct 8, 2025

update that Terminal CNF!

@DHowett DHowett merged commit d4c25dd into main Oct 8, 2025
3 checks passed
@carlos-zamora carlos-zamora deleted the dev/cazamor/search-by-cmd branch October 9, 2025 17:31
DHowett pushed a commit to microsoft/terminal that referenced this pull request Oct 9, 2025
## Summary of the Pull Request
Update the WinGet CNF package search to match that of the updated
PowerShell WinGet CNF module. Now, we'll only search for matching
commands instead of by name and moniker.

## References and Relevant Issues
microsoft/winget-command-not-found#29

## Validation Steps Performed
✅ In CMD, type "vim" and vim packages are suggested
DHowett pushed a commit to microsoft/terminal that referenced this pull request Nov 24, 2025
## Summary of the Pull Request
Update the WinGet CNF package search to match that of the updated
PowerShell WinGet CNF module. Now, we'll only search for matching
commands instead of by name and moniker.

## References and Relevant Issues
microsoft/winget-command-not-found#29

## Validation Steps Performed
✅ In CMD, type "vim" and vim packages are suggested

(cherry picked from commit 819987c)
Service-Card-Id: PVTI_lADOAF3p4s4BBcTlzgfuACY
Service-Version: 1.24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Perf regression in the Microsoft.WinGet.CommandNotFound module Feedback should not be searching by package name

3 participants