Downloads of v 7.4.493:


Last Update:

04 Nov 2014

Package Maintainer(s):

Software Author(s):

  • Bram Moolenaar
  • Vim Community


vim editor vi admin


This is not the latest version of Vim available.

  • 1
  • 2
  • 3

7.4.493 | Updated: 04 Nov 2014



Downloads of v 7.4.493:


Software Author(s):

  • Bram Moolenaar
  • Vim Community


vim editor vi admin

  • 1
  • 2
  • 3
Vim 7.4.493

This is not the latest version of Vim available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


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 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 vim -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 vim -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 vim installed
    name: vim
    state: present
    version: 7.4.493
    source: STEP 3 URL

See docs at

chocolatey_package 'vim' do
  action    :install
  version  '7.4.493'
  source   'STEP 3 URL'

See docs at

    Name: vim,
    Version: 7.4.493,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vim
   Name     = 'vim'
   Ensure   = 'Present'
   Version  = '7.4.493'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

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

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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

This package was approved by moderator gep13 on 04 Nov 2014.


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.

$packageName = 'vim'
$fileType = 'exe'
$args = '/S'
$version = '7.4.493'
$versionDash = $version -replace '\.', '-'

$url = "${version}/gvim-${versionDash}.exe/download"

Install-ChocolateyPackage $packageName $fileType $args $url

$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path

Start-ChocolateyProcessAsAdmin (Join-Path $scriptDir 'chocolateyPostInstallUAC.ps1')
$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path

# Attention people from the future. This function will be built into chocolatey or possibly
. (Join-Path $scriptDir '.\Invoke-GenerateBinFile.ps1')

$is64bit = (Get-WmiObject Win32_Processor).AddressWidth -eq 64
if ($is64bit) {
      $installDir = Split-Path -Parent (Get-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Vim UninstallString).UninstallString
      $installDir = Split-Path -Parent (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim UninstallString).UninstallString

$binDir = Join-Path (Split-Path -Parent $installDir) 'bin'

if (-not(Test-Path $bindir -PathType Container)) { mkdir $bindir }
Invoke-GenerateBinFile 'gvim' $installDir $binDir -UseStart
Invoke-GenerateBinFile 'vim' $installDir $binDir

# Being safe in case your session path is not the same as the path in your registry
$oldPath = [Environment]::GetEnvironmentVariable('PATH', [EnvironmentVariableTarget]::Machine)
if(-not ($oldPath.Split(';') -contains $binDir)) {
  Write-Host "Adding $($binDir) to your path in the registry"
  [Environment]::SetEnvironmentVariable('PATH', "$($oldPath);$binDir", [EnvironmentVariableTarget]::Machine)

# Just a place until this gets included in a chocolatey release.
function Invoke-GenerateBinFile {
  [string] $name,
  [string] $path,
  [string] $outPath,
  [switch] $useStart
  Write-Debug "Running 'Invoke-GenerateBinFile' for $name with path:'$path'";

  $packageBatchFileName = Join-Path $outPath "$name.bat"
  $path  = Join-Path $path "$name.exe"
  Write-Host "Adding $packageBatchFileName and pointing to '$path'."
  if ($useStart) {
    Write-Host "Setting up $name as a non-command line application."
"@echo off
SET DIR=%~dp0%
start """" ""$path"" %*" | Out-File $packageBatchFileName -encoding ASCII
  } else {
"@echo off
SET DIR=%~dp0%
""$path"" %*" | Out-File $packageBatchFileName -encoding ASCII

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
Vim 8.2.3206 704 Saturday, July 24, 2021 Approved
Vim 8.2.3204 497 Friday, July 23, 2021 Approved
Vim 8.2.3197 1744 Thursday, July 22, 2021 Approved
Vim 8.2.3192 1130 Wednesday, July 21, 2021 Approved
Vim 8.2.3187 1252 Tuesday, July 20, 2021 Approved
Vim 8.2.3182 1189 Monday, July 19, 2021 Approved
Vim 8.2.3174 743 Sunday, July 18, 2021 Approved
Vim 8.2.3172 944 Saturday, July 17, 2021 Approved
Vim 8.2.3161 2044 Thursday, July 15, 2021 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.
  • 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 Vim, 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