Downloads:

10,610

Downloads of v 7.4.827:

237

Last Update:

14 Nov 2015

Package Maintainer(s):

Software Author(s):

  • Build: veegee developer: vim team

Tags:

vim-x64 vim editor admin

vim-x64

This is not the latest version of vim-x64 available.

7.4.827 | Updated: 14 Nov 2015

Downloads:

10,610

Downloads of v 7.4.827:

237

Maintainer(s):

Software Author(s):

  • Build: veegee developer: vim team

vim-x64 7.4.827

This is not the latest version of vim-x64 available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install vim-x64, run the following command from the command line or from PowerShell:

>

To upgrade vim-x64, run the following command from the command line or from PowerShell:

>

To uninstall vim-x64, 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 Download

3. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade vim-x64 -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-x64 -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-x64 installed
  win_chocolatey:
    name: vim-x64
    state: present
    version: 7.4.827
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'vim-x64' do
  action    :install
  version  '7.4.827'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: vim-x64,
    Version: 7.4.827,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller vim-x64
{
   Name     = 'vim-x64'
   Ensure   = 'Present'
   Version  = '7.4.827'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vim-x64':
  provider => 'chocolatey',
  ensure   => '7.4.827',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install vim-x64 version="7.4.827" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 28 Dec 2015.

Description

64-bit Vim for 64-bit Windows, with 64-bit Python 2.7 and 3.4 support, 64-bit Lua 5.2 support, and 64-bit Ruby 2.0.0 support (via RubyInstaller). Compiled with HUGE feature set and full optimizations for speed. Includes both the GUI (gvim.exe) and console (vim.exe) executables. Updated weekly.


tools\chocolateyinstall.ps1
$packageName = 'vim-x64' # arbitrary name for the package, used in messages
$fileFullPath = "$ENV:Temp\vim-x64.exe"
$fileType = 'exe'
$silentArgs = '/S'
$version = '7.4.827'
$url = "https://bintray.com/artifact/download/veegee/generic/vim${version}_x64.exe"
$checksum = 'e12f770e30320ffb792ae2974d8a38aa7c4f6855'
$checksumType = 'SHA1'

# Elevation bug, omitted until further notice
#Install-ChocolateyPackage $packageName $fileType $silentArgs $url -checksum $checksum -checksumType $checksumType
Get-ChocolateyWebFile $packageName $fileFullPath $url -checksum $checksum -checksumType $checksumType
Start-Process -FilePath $fileFullPath -ArgumentList $silentArgs -Verb RunAs
tools\chocolateyuninstall.ps1
$packageName = 'vim-x64'
$registryUninstallerKeyName = 'Vim 7.4'
$shouldUninstall = $true
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)

$machine_key   = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"

$file = $machine_key `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString

if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false
}

$installerType = 'EXE' 
#$silentArgs = '/S'
$validExitCodes = @(0)

#if (!(Test-Path $file)) {
#    Write-Host "$packageName has already been uninstalled by other means."
#    $shouldUninstall = $false
#}


if ($shouldUninstall) {
 # Enforce elevation until chocolatey bug is resolved
 Start-Process powershell -ArgumentList "Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -validExitCodes $validExitCodes -File $file" -Verb RunAs
 # Uninstaller doesn't seem to work properly, so let's clean up after it
 # Explorer handle prevents removal, reboot explorer
 Get-Process | Where { $_.name -eq 'explorer' } | Stop-Process
 # I hope you don't have any documents open in the editor you're uninstalling...
 Get-Process | Where { $_.name -eq 'vim'      } | Stop-Process
 Get-Process | Where { $_.name -eq 'gvim'     } | Stop-Process
 Start-Process PowerShell -ArgumentList "-File $scriptPath\housekeeping.ps1" -Verb RunAs
}
tools\housekeeping.ps1
Remove-Item -Path "$ENV:ProgramFiles\Vim" -Force -Recurse
Remove-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Vim 7.4' -Force -Recurse
Remove-Item -Path 'HKLM:\SOFTWARE\Vim' -Force -Recurse

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 x64 7.4.1817 179 Thursday, May 5, 2016 Approved
Vim x64 7.4.1796 339 Friday, April 29, 2016 Approved
Vim x64 7.4.1759 272 Thursday, April 21, 2016 Approved
Vim x64 7.4.1739 305 Friday, April 15, 2016 Approved
Vim x64 7.4.1713 360 Thursday, April 7, 2016 Approved
Vim x64 7.4.1709 276 Tuesday, April 5, 2016 Approved
Vim x64 7.4.1689 289 Thursday, March 31, 2016 Approved
Vim x64 7.4.1646 301 Friday, March 25, 2016 Approved
Vim x64 7.4.1641 268 Thursday, March 24, 2016 Approved

This package has no dependencies.

Discussion for the vim-x64 Package

Ground Rules:

  • This discussion is only about vim-x64 and the vim-x64 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-x64, 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