Downloads of v


Last Update:

26 May 2016

Package Maintainer(s):

Software Author(s):

  • Neovim contributors


vi vim gvim neovim text editor sublime atom emacs notepad

Neovim - experimental

This is a prerelease version of Neovim - experimental.

  • 1
  • 2
  • 3 | Updated: 26 May 2016



Downloads of v


Software Author(s):

  • Neovim contributors

  • 1
  • 2
  • 3
Neovim - experimental

This is a prerelease version of Neovim - experimental.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install Neovim - experimental, run the following command from the command line or from PowerShell:


To upgrade Neovim - experimental, run the following command from the command line or from PowerShell:


To uninstall Neovim - experimental, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade neovim -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade neovim -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure neovim installed
    name: neovim
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'neovim' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: neovim,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller neovim
   Name     = 'neovim'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'neovim':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install neovim version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

Neovim is a project that seeks to aggressively refactor Vim in order to:

  • Simplify maintenance and encourage contributions
  • Split the work between multiple developers
  • Enable the implementation of new/modern user interfaces without any modifications to the core source
  • Improve extensibility with a new plugin architecture
  • For lots more details, see the wiki!

More powerful plugins

The msgpack API enables structured communication to and from any programming language. Remote plugins run as co-processes that communicate with Neovim safely and asynchronously.

Better out-of-the-box

  • Strong defaults
  • Modern terminal features such as truecolor and bracketed paste
  • Built-in terminal emulator

First-class embedding

GUIs (or TUIs—such as readline) can nvim --embed or communicate via TCP socket using the discoverable msgpack API.

Drop-in replacement for Vim

Neovim is an extension of Vim: feature-parity and backwards compatibility are high priorities. If you are already familiar with Vim, see :help nvim-from-vim to learn about the differences.

Something broke?

You may find some help here!

#Automated installation steps based on the official manual steps at

$ErrorActionPreference = 'Stop'; 

$packageName = 'neovim'
$toolsDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url         = '' 
$url64       = ''
$neovimQtUrl = ""
$noIgnore    = ''
$startBatch  = 'neovim.bat'

$neovimPackageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $url
  url64bit      = $url64
  validExitCodes= @(0) 
  softwareName  = 'Neovim*' 
  checksum      = ''
  checksumType  = 'md5' 
  checksum64    = ''
  checksumType64= 'md5' 
$neovimQtPackageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $neovimQtUrl
  url64bit      = $neovimQtUrl
  validExitCodes= @(0) 
  softwareName  = 'Neovim*' 
  checksum      = ''
  checksumType  = 'md5' 
  checksum64    = ''
  checksumType64= 'md5' 

function MergeApplicationDirectories($neovimDirectory, $neovimQtDirectory) {
  #Get-ChildItem -Path $neovimDirectory\Neovim\bin\* | Move-Item -Destination $neovimQtDirectory -Force
  #Get-ChildItem -Path $neovimDirectory\Neovim\share\nvim\runtime\* | Move-Item -Destination $neovimQtDirectory -Force
  Copy-Item -Path $neovimDirectory\Neovim\bin\* -Destination $neovimQtDirectory -Recurse -Force
  Copy-Item -Path $neovimDirectory\Neovim\share\nvim\runtime\* -Destination $neovimQtDirectory -Recurse -Force

  Remove-Item -Path $neovimDirectory\Neovim -Recurse -Force
  Move-Item -Path $neovimQtDirectory\nvim-qt.exe -Destination $neovimQtDirectory\neovim.exe

function IgnoreToolsExecutables() {
  #Get-ChildItem ".\*" -Force -Include *.exe -Exclude $noIgnore | % { 
  Get-ChildItem ".\*" -Force -Include *.exe | % { 
  '' > "$_.ignore" 
  Write-Debug "$_.ignore file created."

Get-ChildItem "$toolsDir\*.bat" | %{ Install-BinFile -Name $_.BaseName -Path $_ }

Install-ChocolateyZipPackage @neovimQtPackageArgs
Install-ChocolateyZipPackage @neovimPackageArgs
Write-Debug "Install packages ended."

MergeApplicationDirectories "$toolsDir" "$toolsDir"
Write-Debug "Merge packages ended."

Push-Location "$toolsDir" 

$packageName = 'neovim'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Get-ChildItem "$toolsDir\*.bat" | %{ Uninstall-BinFile -Name $_.BaseName -Path $_ }
@echo off

set VIM=%ChocolateyInstall%\lib\neovim\tools

%VIM%\neovim.exe %*

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Neovim 0.6.0-beta 6919 Friday, July 2, 2021 Approved
Neovim 0.5.0 17302 Friday, July 2, 2021 Approved
Neovim 0.5.0-beta 15906 Friday, April 3, 2020 Approved
Neovim 33 Monday, January 18, 2021 Approved
Neovim 0.4.5-beta 64 Thursday, August 13, 2020 Exempted
Neovim 24047 Monday, January 18, 2021 Approved
Neovim 0.4.4 20267 Wednesday, September 9, 2020 Approved
Neovim 0.4.3 26447 Monday, November 18, 2019 Approved

Discussion for the Neovim - experimental Package

Ground Rules:

  • This discussion is only about Neovim - experimental and the Neovim - experimental package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Neovim - experimental, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus