Improvements to the list command

[denelon]

Description of the new feature/enhancement

We need to build a cache to improve performance for the list command.

We need to record everything installed by the Windows Package Manager explicitly.

Proposed technical implementation details (optional)

[ev-dev]

We need to record everything installed by the Windows Package Manager explicitly.

Hey @denelon glad to see this issue! For me and likely many other users, this is an essential feature needed before adopting winget as a default package manager.

It's a bit more than just an inconvenience because the situation is compounded by the fact that many current winget users also use chocolatey, scoop, or both, and so the ability to list packages installed specifically with winget should be considered a vital operation. I would argue that this issue is worthy of a high priorty 👍

[denelon]

@ev-dev be sure to add your 👍 to the issue. We often sort by most 👍 to find high priority / high value features. We have a large number of Issues in v.Next right now to evaluate for v1.1.

[Karl-WE]

while there is a search option in the consoles of cmd and PowerShell (Ctrl+F) there is no search in Windows Terminal yet.

How about:
The list command (same as search) has an an optional paged output as if you would pipe it to "more"
e.g. get-childitem (ls) | more

just tested winget search / list support piping to more.

examples:

winget list -p / winget list --p
winget search -p / winget list --p

[jypeter]

I have just discovered winget, but the the winget list order makes no sense (at least not to me)

Is there a way to get a list sorted in alphabetical order of the package names? I would use | sort in Linux, but I'm not familiar with PowerShell syntax