Vim Package - Not added to path

[nmat]

Description of the new feature/enhancement

Installed vim and tried to start gvim and vim from powershell but the path is not added correctly. Using package from website and telling package to use full install would it to path.

Proposed technical implementation details (optional)

Ability to add to path in some way.

[denelon]

This appears to be related either to the installer or switches that should be added to the manifest. Is this problem still occuring?

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

[rylev]

FYI: This problem is still occurring - I can reproduce this with the latest version of winget.

[okmanideep]

Same for Neovim.Neovim as well

[denelon]

Vim's installer for Windows appears to be Nullsoft. I would suggest making an Issue and if you have the time and skill, a contribution to have the path added by the installer.

[denelon]

Neovim's installer for Windows appears to be Wix. I would suggest making an Issue and if you have the time and skill, a contribution to have the path added by the installer.

[metalglove]

I have stumbled upon this issue as well.
I have resolved it using this PowerShell script.

winget install -e --id vim.vim -v 9.0.0009
[Environment]::SetEnvironmentVariable('Path', $env:PATH + ';C:\Program Files\Vim\vim90\',  'User')

[sitiom]

Same for Neovim.Neovim as well

It works for me when I run it in the terminal, but it doesn't work open running it from "Run" (Win + R) due to an excess slash in the path. This should be fixed in neovim/neovim#19485.

[denelon]

Has the path issue with the Vim installer been resolved?

[alexchro93]

@denelon installing the package interactively allows you to configure gvim/vim so that it can be invoked from the command line, assuming C:\Windows is in your path (which I think it is by default).

Running:

winget install --id vim.vim --interactive

Leads to:

[denelon]

@alexchro93 unfortunately, nobody has been able to share switches that work for this in "silent" or "silent with progress" install mode. Thanks for the update though! I'm trying to loop through some of the older issues to see if we can get some traction. I think this is likely to require changes for the Vim installer to be able to work in the default install mode with WinGet.

[AsciiWolf]

Still the same issue.

[yrro]

I have stumbled upon this issue as well. I have resolved it using this PowerShell script.

winget install -e --id vim.vim -v 9.0.0009
[Environment]::SetEnvironmentVariable('Path', $env:PATH + ';C:\Program Files\Vim\vim90\',  'User')

Don't do this! It's a really common way for poorly written installers to screw up a system in a really subtle way that will cause breakage that may only be discovered months or years down the line.

You will permanently expand all environment variable references within HKCU\Environment's PATH value, and change the type from REG_EXPAND_SZ to REG_SZ.

This is a serious bug in .NET that at this point I am assuming will never be fixed.

Instead you should retrieve the data for the value you wish to change:

(Get-Item HKCU:\Environment).getValue("PATH", $null, "DoNotExpandEnvironmentNames")

... then manipulate the data. There are two ways to safely update the PATH value's data:

1. Use Set-ItemProperty HKCU:\Environment PATH $newPath -Type ExpandString
2. Call this overload of RegistryKey.setValue

[microsoft-github-policy-service]

Hello @nmat,

This issue has been identified as requiring a fix from a third party or external repository. Since there has been no recent activity on this issue, it will be automatically closed.

Template: msftbot/noRecentActivity/areaExternal

[microsoft-github-policy-service]

Hello @nmat,

This issue has been identified as requiring a fix from a third party or external repository. Since there has been no recent activity on this issue, it will be automatically closed.

Template: msftbot/noRecentActivity/areaExternal