Downloads of v 8.2.750:


Last Update:

14 May 2020

Package Maintainer(s):

Software Author(s):

  • Build:
  • Developer: vim team


vim-tux vim editor tux admin

Vim Tux (Install)

This is not the latest version of Vim Tux (Install) available.

  • 1
  • 2
  • 3

8.2.750 | Updated: 14 May 2020



Downloads of v 8.2.750:



Software Author(s):

  • Build:
  • Developer: vim team

  • 1
  • 2
  • 3
Vim Tux (Install) 8.2.750

This is not the latest version of Vim Tux (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


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 Tux (Install), run the following command from the command line or from PowerShell:


To upgrade Vim Tux (Install), run the following command from the command line or from PowerShell:


To uninstall Vim Tux (Install), 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-tux.install -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-tux.install -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-tux.install installed
    name: vim-tux.install
    state: present
    version: 8.2.750
    source: STEP 3 URL

See docs at

chocolatey_package 'vim-tux.install' do
  action    :install
  version  '8.2.750'
  source   'STEP 3 URL'

See docs at

    Name: vim-tux.install,
    Version: 8.2.750,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vim-tux.install
   Name     = 'vim-tux.install'
   Ensure   = 'Present'
   Version  = '8.2.750'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'vim-tux.install':
  provider => 'chocolatey',
  ensure   => '8.2.750',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vim-tux.install version="8.2.750" 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 likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

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

This package was approved as a trusted package on 14 May 2020.


Package Parameters

The following package parameters can be set:

  • /InstallPopUp - Install into the context menu "Edit with gVim", powered by GVimExt.dll.
  • /RestartExplorer - Kill explorer.exe before each update to free up the in-use GVimExt.dll.
  • /NoCreateBatFiles - Do not create batch files in C:\Windows (vim.bat, vimdiff.bat, etc).

Please visit the official site at for more information.
Build provided by - consider donating to help support their server costs.

$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $ENV:ProgramFiles 'Vim\vim82'
if ($Env:ChocolateyPackageParameters -match '/InstallDir:\s*(.+)') {
	$destDir = $Matches[1]
	$destDir = $destDir -replace '^[''"]|[''"]$' # Strip quotations. Necessary?
	$destDir = $destDir -replace '[\/]$' # Remove any slashes from end of line
	if (-not ($destDir.EndsWith('vim82'))) { $destDir = Join-Path $destDir 'vim82' } # installer will not run if it is not within folder vim82

$pp = Get-PackageParameters

# Optionally restart explorer before install
if ($pp['RestartExplorer'] -eq 'true') {
	Write-Debug "Restarting Explorer"
	Get-Process explorer | Stop-Process -Force

# Create batch files in C:\Windows by default
$createBatFiles = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff'
if ($pp['NoCreateBatFiles'] -eq 'true') {
	Write-Debug 'Not installing batch files'
	$createBatFiles = $null

# Do not install context menu entry by default
$installPopUp = $null
if ($pp['InstallPopUp'] -eq 'true') {
	Write-Debug 'Installing context menu entry'
	$installPopUp = '-install-popup'

$baseArgs = "-install-openwith -add-start-menu"
$installArgs = $installPopUp, $createBatFiles, $baseArgs -ne $null -join ' '

$packageArgs = @{
        packageName  = 'vim-tux.install'
        filetype     = 'exe'
        file         = gi $toolsDir\*_x32.exe
        file64       = gi $toolsDir\*_x64.exe
        silentArgs   = "-o`"$destDir`" -y"
        softwareName = 'vim*'

Install-ChocolateyPackage @packageArgs
Move-Item "$toolsDir\patch.exe.manifest" $destDir -Force -ea 0 # Supplied manifest fixes useless UAC request
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest
# Run vim's installer
Move-Item "$toolsDir\install" "$destDir\install.exe" -Force -ea 0 # vim-tux removed the installer, just in time for Defender to stop flagging it
Move-Item "$toolsDir\uninstal" "$destDir\uninstal.exe" -Force -ea 0 # vim-tux removed the uninstaller, just in time for Defender to stop flagging it
Start-ChocolateyProcessAsAdmin "$installArgs" "$destDir\install.exe" -validExitCodes '0'
Remove-Item -Force -ea 0 "$toolsDir\*_x32.exe","$toolsDir\*_x64.exe"
Write-Host 'Build provided by - consider donating to help support their server costs.'
$packageName = 'vim-tux.install'
$destDir = Join-Path $ENV:ProgramFiles "Vim"

# Apparently doesn't have a non-interactive mode. Send 'y' to its input
Set-Content -Path "$env:TEMP\vimuninstallinput" -Value 'y'
Start-Process -FilePath "$destDir\vim82\uninstal.exe" -ArgumentList '-nsis' -RedirectStandardInput "$env:TEMP\vimuninstallinput" -Wait
Remove-Item "$env:TEMP\vimuninstallinput"
Remove-Item $destDir -Force -Recurse
md5: E1B058E8468FC07F25FAEA1DC342149B | sha1: D0CFD045A8B46DEF67788A4E7F96D7206DF445E1 | sha256: E07299E0463B7B134506FBD9C4BE1ADBEE2BD1812690D611F617832AA59081CB | sha512: 4EE8A6CD2E6127DF026518B31EE1BC6020A7928B937B4E97B5DE401F6E5FD9ECCBEBD70C6FFCFC09D008FD6945D7BDA7C9AEAABC5E9DDE0E5A74788D7F1F2655

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 Tux (Install) 8.2.2840 269 Saturday, May 8, 2021
Waiting for Maintainer
Vim Tux (Install) 8.2.2799 192 Thursday, April 22, 2021 Approved
Vim Tux (Install) 8.2.2794 44 Wednesday, April 21, 2021 Approved
Vim Tux (Install) 8.2.2763 150 Thursday, April 15, 2021 Approved
Vim Tux (Install) 8.2.2738 140 Friday, April 9, 2021 Approved
Vim Tux (Install) 8.2.2730 76 Wednesday, April 7, 2021 Approved
Vim Tux (Install) 8.2.2679 107 Wednesday, March 31, 2021 Approved
Vim Tux (Install) 8.2.2650 45 Friday, March 26, 2021 Approved
Discussion for the Vim Tux (Install) Package

Ground Rules:

  • This discussion is only about Vim Tux (Install) and the Vim Tux (Install) 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 Tux (Install), 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