Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

#### Vim

2,071,899

9

Maintainer(s):

Software Author(s):

• Bram Moolenaar
• Vim Community
• 1
• 2
• 3

### Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as an Error:

At least one file within this package has greater than 10 detections

Details
WARNING

There are versions of this package awaiting moderation . See the Version History section below.

WARNING

This package was rejected on 17 Feb 2023. The reviewer Pauby has listed the following reason(s):

#### chocolatey-community (maintainer) on 24 Jan 2023 00:13:26 +00:00:

User 'chocolatey-community' (maintainer) submitted package.

#### chocolatey-ops (reviewer) on 24 Jan 2023 00:50:07 +00:00:

vim has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

##### Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

• There are more than 3 automation scripts in this package. This is not recommended as it increases the complexity of the package. More...
##### Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

• Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

#### chocolatey-ops (reviewer) on 24 Jan 2023 00:56:46 +00:00:

vim has passed automated package testing (verification). The next step in the process is package scanning.
This is an FYI only. There is no action you need to take.

#### chocolatey-ops (reviewer) on 24 Jan 2023 03:25:59 +00:00:

vim has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.

#### chocolatey-ops (reviewer) on 13 Feb 2023 00:51:07 +00:00:

We've found vim v9.0.1237 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

• Resubmit fixes for this version.
• If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

#### Pauby (reviewer) on 17 Feb 2023 22:59:42 +00:00:

Status Change - Changed status of package from 'submitted' to 'rejected'.

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.

• /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. • See https://github.com/vim/vim-win32-installer for more information. • If the package is out of date please check Version History for the latest submitted version. If you have a question, please ask it in Chocolatey Community Package Discussions or raise an issue on the Chocolatey Community Packages Repository if you have problems with the package. Disqus comments will generally not be responded to. tools\chocolateybeforemodify.ps1 $toolsDir = "$(Split-Path -parent$MyInvocation.MyCommand.Definition)"
$installDir = Get-Content "$toolsDir\installDir"
$shortversion = '90' 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 = '90'
$pp = Get-PackageParameters .$toolsDir\helpers.ps1
$installDir = Get-InstallDir$packageArgs = @{
packageName   = $env:ChocolateyPackageName unzipLocation =$installDir
file          = "$toolsDir\gvim_9.0.1237_x86.zip" file64 = "$toolsDir\gvim_9.0.1237_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 | Write-Debug
Set-Content -Path "$toolsDir\installDir" -Value$installDir

tools\chocolateyuninstall.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"$installDir = Get-Content "$toolsDir\installDir"$shortversion = '90'
$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 "$installDir\vim" -Recurse -Force

tools\gvim_9.0.1237_x64.zip
md5: 0C85B7BC45CA0B35CBB5FA65C1DEADF2 | sha1: 19D2695CDD06322D6C9BE98EDB1908459E928D24 | sha256: 87BD35355A63B2052E3C018BF6FB4D7E0DD3EC1EED9899200614013D297C793F | sha512: A925446A7BADC31BB9F875A0D509C05C592F9C0CBC4D4C6348EB97BCA918B704194B63CF262891BAFE3C928B76A1A68B41315DB417DC214CACCE21EB69404065
tools\gvim_9.0.1237_x86.zip
md5: D588A2B4A18C35B3814CD0DE684523AE | sha1: C3F09C62A0AFCA5360084482B37388A221CFA1D2 | sha256: 2B7E0D90F5F0F01BAB5B2ECB455F853C16B065594ACE7DC8B5F27313503B7FB5 | sha512: 309C0718A3BF5F07228E8DB2051DBA8CDB9DDF9328F27431C584FB27F8E0EDDFA6B731AF3744B389060D7CB05C651F5B8A9986B741FB911E6B81569F857E09E4
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 vimtutor -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') {
$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 function Create-SymbolicLink() { 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" }
}

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
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
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
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

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: 2B7E0D90F5F0F01BAB5B2ECB455F853C16B065594ACE7DC8B5F27313503B7FB5
checksum64: 87BD35355A63B2052E3C018BF6FB4D7E0DD3EC1EED9899200614013D297C793F


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 9.0.1424 1423 Thursday, March 23, 2023 Approved
Vim 9.0.1423 1899 Wednesday, March 22, 2023 Approved
Vim 9.0.1418 1578 Tuesday, March 21, 2023 Approved
Vim 9.0.1417 1789 Monday, March 20, 2023 Approved
Vim 9.0.1414 1194 Sunday, March 19, 2023 Approved
Vim 9.0.1413 904 Saturday, March 18, 2023 Approved
Vim 9.0.1411 551 Friday, March 17, 2023 Approved
Vim 9.0.1403 5072 Monday, March 13, 2023 Approved
Vim 9.0.1402 1274 Sunday, March 12, 2023 Approved

This package has no dependencies.

Discussion for the Vim Package