microsoft / microsoft/winget-command-not-found

Command line aliases not recognized after package install

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
PowerShell
Stars
60
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Image I tried the same thing on a different computer and got the same result

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported behavior from the attached screenshot on a PowerShell 7 installation, comparing command recognition before and after package installation. Review the module's command-detection and package-installation entry points; done means installed package command aliases are recognized on both computers.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.