Downloads:

2,259

Downloads of v 7.4.2098-nightly:

355

Last Update:

24 Jul 2016

Package Maintainer(s):

Software Author(s):

  • vim

Tags:

vim-nightly vim nightly-build editor

vim-nightly

This is a prerelease version of vim-nightly.

7.4.2098-nightly | Updated: 24 Jul 2016

Downloads:

2,259

Downloads of v 7.4.2098-nightly:

355

Maintainer(s):

Software Author(s):

  • vim

Tags:

vim-nightly vim nightly-build editor

vim-nightly 7.4.2098-nightly

This is a prerelease version of vim-nightly.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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

>

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

>

To uninstall vim-nightly, 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://community.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://community.chocolatey.org/api/v2)

4. Choose your deployment method:


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

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


chocolatey_package 'vim-nightly' do
  action    :install
  version  '7.4.2098-nightly'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller vim-nightly
{
   Name     = 'vim-nightly'
   Ensure   = 'Present'
   Version  = '7.4.2098-nightly'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install vim-nightly version="7.4.2098-nightly" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

This is the vim nightly build, the project can be found on vim-win32-installer
The chocolatey package repo can be found: vim-nightly-choco
* This project may not support 32-bits any more only 64-bits machine will be supported

tools\chocolateyinstall.ps1 
Install-ChocolateyZipPackage -packageName 'vim-nightly' -UnzipLocation $(Split-Path -Parent $MyInvocation.MyCommand.Definition) -Url64bit 'https://github.com/vim/vim-win32-installer/releases/download/v7.4.2098/gvim_7.4.2098_x64.zip' -Url 'https://github.com/vim/vim-win32-installer/releases/download/v7.4.2098/gvim_7.4.2098_x86.zip'

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-nightly 7.4.2098-nightly 355 Sunday, July 24, 2016 Exempted
vim-nightly 7.4.2066-nightly 280 Monday, July 18, 2016 Exempted
vim-nightly 7.4.2054-nightly 273 Sunday, July 17, 2016 Exempted
vim-nightly 7.4.2028-nightly 279 Monday, July 11, 2016 Exempted
vim-nightly 7.4.2025-nightly 297 Monday, July 11, 2016 Exempted
vim-nightly 7.4.1990-nightly 259 Tuesday, July 5, 2016 Exempted

Nightly Vim Windows build snapshots (more information).

Changes:

  • 7.4.2098 Text object tests are old style. Solution: Turn them into new style tests. (James McCoy,
  • 7.4.2097 Warning from 64 bit compiler. Solution: use size_t instead of int. (Mike Williams)
  • 7.4.2096 Lambda functions show up with completion. Solution: Don't show lambda functions. (Ken Tak
  • 7.4.2095 Man test fails when run with the GUI. Solution: Adjust for different behavior of GUI. Add
  • 7.4.2094 The color allocation in X11 is overly complicated. Solution: Remove find_closest_color(),
  • 7.4.2093 Netbeans test fails once in a while. Leaving log file behind. Solution: Add it to the lis

Download and execute the most recent gvim_7.._x86.exe file to install Vim.
The exe file contains the (32bit) installer while the .zip files contain an
archive of the 32bit (_x86) or 64bit versions (_x64). To install it, extract
the archive and update your PATH variable. The installer will do that
automatically and provide some additional extensions (e.g. Edit with Vim menu).
The gvim...pdb.zip file only contains the corresponding pdb files for debugging the binaries.

If you need a dynamic interface to Perl, Python2, Python3, Ruby, TCL, Lua or Racket/MzScheme,
make sure you also install the following. Vim will work without it, but some Plugin
might need this additional dependency. (e.g. Gundo needs a working Pyhton2 installation,
Command-T needs a working Ruby installation and Neocomplete needs a working Lua
installation). This means, those interpreters have to be installed in addition to Vim.
Without it Vim won't be able to use that feature! You can find those interperters here:

Make sure that you install the same architecture (32bit/64bit) that matches your Vim installation.

This package has no dependencies.

Discussion for the vim-nightly Package

Ground Rules:

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