[Package Issue]: GNU.Nano

[Sculas]

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

[Trenly]

I'm not able to reproduce this on my end, and I do see that the manifest has nano as the command which should rename the executable. Are you able to post the log file from when you installed Nano?

[Sculas]

I uninstalled Nano, then followed the steps to reproduce and I'm getting the same issue. Here's the log file:
WinGet-2023-01-31-17-59-21.483.log

[rasa]

On a side note, 2.7.5 is an extremely ancient version, and has not received an update in years.

An up to date Windows port (7.2-10) is available at https://github.com/okibcn/nano-for-windows

[rasa]

There also appears to be an official 6.2.2 (nano-v6.2-2-g93400ec8a19a.exe) here . 2.7.5 is very old, and missing many features and bug fixes. I am not sure why this version is the only version being made available.

[mdanish-kh]

The version already available in WinGet is this standalone exe file nano-git-0d9a7347243.exe from the official source https://nano-editor.org/dist/win32-support/. The other executable you mentioned nano-v6.2-2-g93400ec8a19a.exe does not work for me in PowerShell (has a dependency on another terminal emulator?)

 ~ .\nano-v6.2-2-g93400ec8a19a.exe
Error opening terminal: vt220.

The unofficial alternative you suggested happens to use .7z extension which is not currently supported by WinGet.

[okibcn]

The unofficial alternative you suggested happens to use .7z extension which is not currently supported by WinGet.

From now on it will be delivered also in zip format. The current version is 7.2-13.

[okibcn]

There is now an updated nano v7.2-13.2 for the three Windows architectures in Internet:

• Windows 32 bits
• Windows 64 bits
• Windows on Arm

The exe downloaded by the nano manifest in Winget has several problems:

• it is more than 6 years old, and a lot of functionality was added after that ancient version.
• it lacks any documentation
• it is not an installer, but the raw exe file.

[AsciiWolf]

Still the same issue.

[bfcns]

Also this is what I get in winget list when I install GNU.Nano

Name                                                        Id                    Version Available Source
----------------------------------------------------------------------------------------------------------
GNU Nano                                                    GNU.Emacs             2.7.5   29.1      winget 

[jesjess243]

The version already available in WinGet is this standalone exe file nano-git-0d9a7347243.exe from the official source https://nano-editor.org/dist/win32-support/. The other executable you mentioned nano-v6.2-2-g93400ec8a19a.exe does not work for me in PowerShell (has a dependency on another terminal emulator?)

 ~ .\nano-v6.2-2-g93400ec8a19a.exe
Error opening terminal: vt220.

Still happening for me on the latest version. I cannot find any documentation about these builds to troubleshoot. It seems like we need unofficial ports unless they are patched.

The URL is also currently bugged: ChrisTitusTech/winutil#1490