#### Vim

This is not the latest version of Vim available.

8.2.0916 | Updated: 07 Jun 2020

720,122

1,139

Maintainer(s):

Software Author(s):

• Bram Moolenaar
• Vim Community

### All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Vim, run the following command from the command line or from PowerShell:

>

To upgrade Vim, run the following command from the command line or from PowerShell:

>

To uninstall Vim, 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 https://chocolatey.org/api/v2. 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

#### 3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

#### 4. Choose your deployment method:


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


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 vim -y --source="'STEP 3 URL'"
$exitCode =$LASTEXITCODE

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

Exit $exitCode   - name: Ensure vim installed win_chocolatey: name: vim state: present version: 8.2.0916 source: STEP 3 URL  Coming early 2020! Central Managment Reporting available now! More information...  chocolatey_package 'vim' do action :install version '8.2.0916' source 'STEP 3 URL' end   Chocolatey::Ensure-Package ( Name: vim, Version: 8.2.0916, Source: STEP 3 URL );  Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.  cChocoPackageInstaller vim { Name = 'vim' Ensure = 'Present' Version = '8.2.0916' Source = 'STEP 3 URL' }  Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.  package { 'vim': provider => 'chocolatey', ensure => '8.2.0916', source => 'STEP 3 URL', }  Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.  salt '*' chocolatey.install vim version="8.2.0916" source="STEP 3 URL"  #### 5. If applicable - Chocolatey configuration/installation See infrastructure management matrix for Chocolatey configuration elements and examples. This package was approved as a trusted package on 07 Jun 2020. Description Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems. Vim is often called a programmer's editor, and so useful for programming that many consider it an entire IDE. It's not just for programmers, though. Vim is perfect for all kinds of text editing, from composing email to editing configuration files. ## Features • Vim: Vim terminal(CLI) application can be used from Powershell and Command Prompt. • GVim: The GUI version of Vim provides full featured Windows GUI application experience. • Terminal Integration: Batch files are created to provide vim, gvim, evim, view, gview, vimdiff, gvimdiff and vimtutor command on terminal use. • Shell Integration: Vim is added in Open with ... context menu. And by default Edit with Vim context menu is created to open files whose extensions are associated with other applications. ## Package parameters • /InstallDir - Override the installation directory. By default, the software is installed in $ChocolateyToolsLocation, it's default value is C:\tools. You can include spaces. See the example below.
• /RestartExplorer - Restart Explorer to unlock GVimExt.dll used for Edit with Vim context menu feature.
• /NoDefaultVimrc - Don't create default _vimrc file.
• /NoContextmenu - Don't create Edit with Vim context menu.
• /NoDesktopShortcuts - Don't create shortcuts on the desktop.

Example: choco install vim --params "'/NoDesktopShortcuts /InstallDir:C:\path\to\your dir'"

## Notes

• This package uses the ZIP build to install to provide installation parameters.
• All compilation of the software is automated and performed on Appveyor. The building status is open.
• This package provides an official build. Similar package vim-tux is from a well-known unofficial vim building project. Unlike vim-tux, this package can take some installation parameters.

From: https://vimhelp.org/uganda.txt.html

I)  There are no restrictions on distributing unmodified copies of Vim except
that they must include this license text.  You can also distribute
unmodified parts of Vim, likewise unrestricted except that they must
include this license text.  You are also allowed to include executables
that you made from the unmodified Vim sources, plus your own usage
examples and Vim scripts.

II) It is allowed to distribute a modified (or extended) version of Vim,
including executables and/or source code, when the following four
conditions are met:
1) This license text must be included unmodified.
2) The modified Vim must be distributed in one of the following five ways:
a) If you make changes to Vim yourself, you must clearly describe in
the distribution how to contact you.  When the maintainer asks you
(in any way) for a copy of the modified Vim you distributed, you
must make your changes, including source code, available to the
maintainer without fee.  The maintainer reserves the right to
include your changes in the official version of Vim.  What the
maintainer will do with your changes and under what license they
will be distributed is negotiable.  If there has been no negotiation
then this license, or a later version, also applies to your changes.
The current maintainer is Bram Moolenaar <[email protected]>.  If this
changes it will be announced in appropriate places (most likely
vim.sf.net, www.vim.org and/or comp.editors).  When it is completely
impossible to contact the maintainer, the obligation to send him
your changes ceases.  Once the maintainer has confirmed that he has
received your changes they will not have to be sent again.
b) If you have received a modified Vim that was distributed as
mentioned under a) you are allowed to further distribute it
unmodified, as mentioned at I).  If you make additional changes the
text under a) applies to those changes.
c) Provide all the changes, including source code, with every copy of
the modified Vim you distribute.  This may be done in the form of a
context diff.  You can choose what license to use for new code you
add.  The changes and their license must not restrict others from
making their own changes to the official version of Vim.
d) When you have a modified Vim which includes changes as mentioned
under c), you can distribute it without the source code for the
changes if the following three conditions are met:
- The license that applies to the changes permits you to distribute
the changes to the Vim maintainer without fee or restriction, and
permits the Vim maintainer to include the changes in the official
version of Vim without fee or restriction.
- You keep the changes for at least three years after last
distributing the corresponding modified Vim.  When the maintainer
or someone who you distributed the modified Vim to asks you (in
any way) for the changes within this period, you must make them
available to him.
- You clearly describe in the distribution how to contact you.  This
contact information must remain valid for at least three years
after last distributing the corresponding modified Vim, or as long
as possible.
e) When the GNU General Public License (GPL) applies to the changes,
you can distribute the modified Vim under the GNU GPL version 2 or
any later version.
3) A message must be added, at least in the output of the ":version"
command and in the intro screen, such that the user of the modified Vim
is able to see that it was modified.  When distributing as mentioned
under 2)e) adding the message is only required for as far as this does
not conflict with the license used for the changes.
4) The contact information as required under 2)a) and 2)d) must not be
removed or changed, except that the person himself can make
corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
the Vim license for your changes and make them available to the
maintainer, including the source code.  The preferred way to do this is
by e-mail or by uploading the files to a server and e-mailing the URL.
If the number of changes is small (e.g., a modified Makefile) e-mailing a
context diff will do.  The e-mail address to be used is
<[email protected]>

IV)  It is not allowed to remove this license from the distribution of the Vim
sources, parts of it or from a modified version.  You may use this
license for previous Vim releases instead of the license that they came
with, at your option.

legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from GitHub and can be verified like this:

2. You can use one of the following methods to obtain the SHA256 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'

checksum32: 0160333ED1EB0E7C7877FC456595250B74F415DDD615E28E1F31BD6844DEBF09
checksum64: EAB527F20286C8015C348E6EFA80263B1A7005B57C7ED681CA76F0B060DDCD0C

tools\chocolateybeforemodify.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"$installDir = Get-Content "$toolsDir\installDir"$shortversion = '82'
try {
# Is dlls locked?
Remove-Item "$installDir\vim\vim$shortversion\GvimExt32\gvimext.dll", "$installDir\vim\vim$shortversion\GvimExt64\gvimext.dll" -ErrorAction Stop
} catch {
# Restart explorer to unlock dlls
Write-Debug 'Restarting explorer.'
Get-Process explorer | Stop-Process -Force
}

tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';$toolsDir = "$(Split-Path -parent$MyInvocation.MyCommand.Definition)"
$shortversion = '82'$pp = Get-PackageParameters

. $toolsDir\helpers.ps1$installDir = Get-InstallDir

$packageArgs = @{ packageName =$env:ChocolateyPackageName
unzipLocation = $installDir file = "$toolsDir\gvim_8.2.0916_x86.zip"
file64        = "$toolsDir\gvim_8.2.0916_x64.zip" }$installArgs = @{
statement = Get-Statement
exeToRun  = "$installDir\vim\vim$shortversion\install.exe"
}

'$installDir', ($installDir | Out-String), '$packageArgs', ($packageArgs | Out-String), '$installArgs', ($installArgs | Out-String) | ForEach-Object { Write-Debug $_ } Install-ChocolateyZipPackage @packageArgs Start-ChocolateyProcessAsAdmin @installArgs Copy-Item -Path "$installDir\vim\vim$shortversion\vimtutor.bat" -Destination$env:windir
Set-Content -Path "$toolsDir\installDir" -Value$installDir

tools\chocolateyuninstall.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"$installDir = Get-Content "$toolsDir\installDir"$shortversion = '82'
$statement = '-nsis'$exeToRun  = "$installDir\vim\vim$shortversion\uninstall.exe"
# From vim-tux.install.  Make input.
Set-Content -Path "$env:TEMP\vimuninstallinput" -Value 'y' Start-Process -FilePath$exeToRun -ArgumentList $statement -RedirectStandardInput "$env:TEMP\vimuninstallinput" -Wait -WindowStyle Hidden
Remove-Item "$env:TEMP\vimuninstallinput" Remove-Item "$env:windir\vimtutor.bat"
Remove-Item "$installDir\vim" -Recurse -Force  tools\gvim_8.2.0916_x64.zip md5: 60507858F2E3B550C01F08CA1BE898C2 | sha1: B04CCCF5D404836133D629A896592F16D1BA42B6 | sha256: EAB527F20286C8015C348E6EFA80263B1A7005B57C7ED681CA76F0B060DDCD0C | sha512: B7329447D7C2318E517E4C22D790A812F2C88350477229331DE5B51F55BC1E778EEDBA763400DF3CC1770CDCF30E555BF779243FCF30BACF03F4F527ACBAC33C tools\gvim_8.2.0916_x86.zip md5: BF6BA73088D0454BB83720DD5C6EC6BF | sha1: 354D7A6A01BF8E69084ADB5A25472592BAFA67CB | sha256: 0160333ED1EB0E7C7877FC456595250B74F415DDD615E28E1F31BD6844DEBF09 | sha512: 53A201DF8D47D85AEA5B4154E378219A747217F8D4FAF272C2478E837D61A5B6C7EE2824D7E14D77FCB4100C704B7FB8198872F75CA809BEFFC9A864A19B4FC4 tools\helpers.ps1 function Get-InstallDir() { if ($pp['InstallDir']) {
Write-Debug '/InstallDir found.'
return $pp['InstallDir'] } return Get-ToolsLocation } function Get-Statement() {$options      = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff -install-openwith -add-start-menu'
$createvimrc = '-create-vimrc -vimrc-remap no -vimrc-behave default -vimrc-compat all'$installpopup = '-install-popup'
$installicons = '-install-icons' if ($pp['RestartExplorer'] -eq 'true') {
Write-Debug '/RestartExplorer found.'
Get-Process explorer | Stop-Process -Force
}
if ($pp['NoDefaultVimrc'] -eq 'true') { Write-Debug '/NoDefaultVimrc found.'$createvimrc = ''
}
if ($pp['NoContextmenu'] -eq 'true') { Write-Debug '/NoContextmenu found.'$installpopup = ''
}
if ($pp['NoDesktopShortcuts'] -eq 'true') { Write-Debug '/NoDesktopShortcuts found.'$installicons = ''
}
return $options,$createvimrc, $installpopup,$installicons -join ' '
}
# Replace old ver dir with symlink
# Use mklink because New-Item -ItemType SymbolicLink doesn't work in test-env
# Use rmdir because Powershell cannot unlink directory symlink
{
Get-ChildItem -Path "$installDir\vim" -Exclude "vim$shortversion" -Attributes Directory+!ReparsePoint | ForEach-Object { Remove-Item $_ -Recurse ; New-Item -Path$_ -ItemType Directory }
Get-ChildItem -Path "$installDir\vim" -Exclude "vim$shortversion" -Attributes Directory | ForEach-Object { $_.Name } | ForEach-Object { cmd /c rmdir "$installDir\vim\$_" ; cmd /c mklink /d "$installDir\vim\$_" "$installDir\vim\vim\$shortversion" }
}


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.

Vim 8.2.1119 1808 Friday, July 3, 2020 Approved
Vim 8.2.1114 1386 Thursday, July 2, 2020 Approved
Vim 8.2.1101 1682 Wednesday, July 1, 2020 Approved
Vim 8.2.1095 1587 Tuesday, June 30, 2020 Approved
Vim 8.2.1076 2247 Sunday, June 28, 2020 Approved
Vim 8.2.1065 1151 Saturday, June 27, 2020 Approved
Vim 8.2.1058 1043 Friday, June 26, 2020 Approved
Vim 8.2.1052 1592 Thursday, June 25, 2020 Approved
Vim 8.2.1045 1415 Wednesday, June 24, 2020 Approved

This package has no dependencies.

Discussion for the Vim Package

### Ground Rules:

• This discussion is only about Vim and the Vim 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.