New version: Microsoft.Edit version 1.1.0

[consvc]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.10 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-61-261303-20250528-1

[DHowett]

FWIW the "executable error" validation response is because we don't write a version message out to stdout when redirected. We should, but failing to detect that is a winget validation issue rather than a product issue.

[Frulfump]

FWIW the "executable error" validation response is because we don't write a version message out to stdout when redirected. We should, but failing to detect that is a winget validation issue rather than a product issue.

Could you add issues for those to winget and Edit respectively?

[DHowett]

Well, good and bad news. I was slightly wrong about what the issue is, and we won't be fixing it in Edit.

edit does not produce an exit code when it's launched with no arguments. Because it is a text editor. 🙂

WinGet validation appears to require--or desire?--that a console subsystem application do so.

To quote johnmcp:

It is generally not great for command line utilities since most of the time they "fail" without any params. We are capturing the output to help diagnose those "failures". But when you are relying on that console stdout handle... that is certainly unique.

[JohnMcPMS]

The issue appears to be that Edit does not like it when it receives a redirected output handle. The process exits with a value of 1 and outputs "Error 0x80070006: The handle is invalid." I can repro locally with edit > err.txt. This is understandable given what it is.

[DHowett]

We can probably make the behavior comprehensible for 1.2, but either way it's gonna just keep running rather than exiting. Vim does that, for example - it just writes the output of the editor screen to the redirected file ;P

[denelon]

Manually validated.

[JohnMcPMS]

We can probably make the behavior comprehensible for 1.2, but either way it's gonna just keep running rather than exiting. Vim does that, for example - it just writes the output of the editor screen to the redirected file ;P

I believe that we are happy as long as the process runs for 10 seconds; the goal is that the package is "functional", not missing static dependencies or the wrong architecture, etc.

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\edit.exe returned exit code: 1

Hex	Dec	Inverted Dec	Symbol	Description
00000001	1	-4294967295	ERROR_INVALID_FUNCTION	Incorrect function.

(Automated response - build 1058.)

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[DHowett]

@wingetbot installationmetadata exe add edit.exe --version

[denelon]

@wingetbot installationmetadata exe add edit.exe --version

[denelon]

@DHowett, only "maintainers" can call wingetbot to do things. It might not work since the PR has already been merged.