You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On windows, tldr is unable to execute the commands once selected:
>tldr winget
winget
Windows Package Manager CLI.
More information: <https://docs.microsoft.com/windows/package-manager/winget>.
Search for a package
winget search package
$ package -> terminal
? winget search terminal Yes
exec: "winget": executable file not found in %PATH%
The error message is incorrect since winget is, indeed, in my PATH
The text was updated successfully, but these errors were encountered:
Hmm, I need to test this but in theory it just calls exec.Command and it should be able to run if it's in the PATH, is it only specific to this tool or a general issue?
So far I have this behaviour only for winget, docker and gnu commands installed with MinGW like ls:
> tldr ls
ls
List directory contents.
More information: <https://www.gnu.org/software/coreutils/ls>.
List all files, including hidden files
ls -a
? ls -a Yes
exec: "ls": executable file not found in %PATH%
They are all in the PATH, e.g. winget is installed in ~\AppData\Local\Microsoft\WindowsApps\winget.exe and when I print my PATH I see ~\AppData\Local\Microsoft\WindowsApps in it.
Thanks for the detailed info @LoZeno it seems like we additionally add \c while running such commands, I'll look into this. Or if you prefer adding this feautre (btw, this should only be compiled for windows) feel free to do so.
On windows, tldr is unable to execute the commands once selected:
The error message is incorrect since
winget
is, indeed, in my PATHThe text was updated successfully, but these errors were encountered: