microsoft / microsoft/winget-pkgs

[Package Issue]: GNU.Nano

Open
#95,161 10 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

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

Winget downloads the nano executable to a folder and then adds the directory to the PATH, but it doesn't rename the executable it just downloaded. I had no idea why nano wasn't found until I realized it has the name nano-git-0d9a7347243.exe.

Steps to reproduce
  1. Run winget install -e --id GNU.Nano -v 2.7.5
  2. Restart Terminal
  3. Run nano, and observe the "command not found" error
  4. Find where the executable is located, I found it by looking at $PATH
  5. Observe that the nano executable is named nano-git-0d9a7347243.exe
Actual behavior

The nano executable is named nano-git-0d9a7347243.exe

Expected behavior

The nano executable should be named nano.exe

Environment
Windows Package Manager (Preview) v1.5.101-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.1194
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.101.0
Screenshots and Logs

No response

Contributor guide

Open the contributing guide

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

Locate the GNU.Nano 2.7.5 package manifest in the repository and inspect how the downloaded executable is declared. Reproduce the installation with winget, then verify that the installed executable is named nano.exe and that running nano succeeds.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.