Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package names are being truncated when searching with empty string #2603

Open
fernandog opened this issue Oct 17, 2022 · 10 comments
Open

Package names are being truncated when searching with empty string #2603

fernandog opened this issue Oct 17, 2022 · 10 comments
Labels
Area-Output Issue related to CLI output Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@fernandog
Copy link

Brief description of your issue

Package name are being truncated (notice the "..." ) when you do a search with empty string: winget search " "

image

This issue doesn't happen when you search by part of the name
winget search visualstudio

image

Using Powershell x86 with maximized window on both commands

Steps to reproduce

search with empty string: winget search " "

Expected behavior

No truncated package names

Actual behavior

Package names are being truncated

Environment

PS C:\WINDOWS\system32> winget --version
v1.3.2691

Windows 11 22H2
@ghost ghost added the Needs-Triage Issue need to be triaged label Oct 17, 2022
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Oct 18, 2022
@denelon
Copy link
Contributor

denelon commented Dec 1, 2022

The output is truncated to fit the terminal width in the CLI. We've got PowerShell modules and cmdlets coming out in the next release which don't truncate the output.

@dong-lufei
Copy link

dong-lufei commented Jan 13, 2023

#2842

I didn't search for empty characters or app names with spaces, the command I used was winget list (and viewed at full screen size).
In the displayed list of downloaded and installed application results, some application names or IDs are truncated and cannot be viewed completely

@Frxhb
Copy link

Frxhb commented Jan 17, 2023

The output is truncated to fit the terminal width in the CLI. We've got PowerShell modules and cmdlets coming out in the next release which don't truncate the output.

is there a plan when this will be released? I joined the Windows Package Manager Insiders Program but It didnt change. Or wasnt it changed yet? Thanks alot.

@denelon
Copy link
Contributor

denelon commented Jan 17, 2023

A preview version of the PowerShell cmdlets is available via the GitHub release.

@Frxhb
Copy link

Frxhb commented Jan 17, 2023

A preview version of the PowerShell cmdlets is available via the GitHub release.

Thanks, I have installed it. Can you tell me how to format the output of winget search """"now better?

@denelon
Copy link
Contributor

denelon commented Jan 17, 2023

Once the module is available, you can just run Find-WinGetPackage and pull the output you need. The default display in the terminal will still show truncated values, but the object contains the names.

@Trenly
Copy link
Contributor

Trenly commented Jun 16, 2023

[Policy] Area-Output

@microsoft-github-policy-service microsoft-github-policy-service bot added the Area-Output Issue related to CLI output label Jun 16, 2023
@RockstarSven
Copy link

A workaround could be to output the results to file, and then review the file:

The default is truncated:

PS> winget list Microsoft.VisualStudio.2019
Name                                Id                                    Version  Available Source
---------------------------------------------------------------------------------------------------
Visual Studio Build Tools 2019      Microsoft.VisualStudio.2019.BuildToo… 16.11.28 16.11.29  winget

I use:

PS> winget list Microsoft.VisualStudio.2019 > foo.txt
PS> cat .\foo.txt

Name                                Id                                       Version  Available Source
------------------------------------------------------------------------------------------------------
Visual Studio Build Tools 2019      Microsoft.VisualStudio.2019.BuildTools   16.11.28 16.11.29  winget

@schittli

This comment was marked as off-topic.

@denelon
Copy link
Contributor

denelon commented Aug 2, 2024

You can use the Microsoft.WinGet.Client PowerShell module and Find-WinGetPackage "" using PowerShell.

@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Issue related to CLI output Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

7 participants