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 Issue]: Helix.Helix doesn't add itself to PATH env variable properly #108595

Open
1 of 2 tasks
MiKom opened this issue Jun 1, 2023 · 5 comments
Open
1 of 2 tasks
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@MiKom
Copy link
Contributor

MiKom commented Jun 1, 2023

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

The path to the package is added to PATH env variable but the actual executable is located inside a directory (helix-23.05-x86_64-windows so the terminal can't find it:
image

@Revnixcad

Steps to reproduce

  1. Install Helix.Helix
  2. Restart shell to have the updated environment variables
  3. Open terminal
  4. type hx

Actual behavior

Command is not found

Expected behavior

Helix editor opens

Environment

Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.2965
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0

Screenshots and Logs

image
screenshot

@MiKom MiKom added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jun 1, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jun 1, 2023
@Trenly
Copy link
Contributor

Trenly commented Jun 1, 2023

This issue should already be resolved in the lastest 1.5-preview version of the Winget client

@MiKom
Copy link
Contributor Author

MiKom commented Jun 1, 2023

Ah sorry then. It looked like a package issue for a newb like me.

@BrandonWanHuanSheng
Copy link
Contributor

BrandonWanHuanSheng commented Jun 1, 2023

I also have some pull request on draft. Some of the pull request was draft waiting for winget v 1.5 stable version to roll up. That issue was merged see microsoft/winget-cli#2909

@BrandonWanHuanSheng
Copy link
Contributor

When there is next update, it will hold off merged until the next stable versions released.

@stephengillie stephengillie removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Jun 1, 2023
@anddam
Copy link

anddam commented Oct 1, 2023

This issue should already be resolved in the lastest 1.5-preview version of the Winget client

I am seeing the same issue on

> winget --version
v1.6.2721

is there some action to perform with winget in order to not manually add the package path(s)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

5 participants