@chrisbra chrisbra released this Sep 12, 2016

Nightly Vim Windows build snapshots (more information).


  • 8.0.0003 getwinvar() returns wrong Value of boolean and number options, especially non big endian
  • Update translations for intro page.
  • 8.0.0002 The netrw plugin does not work. Solution: Make it accept version 8.0.
  • 8.0.0001 Intro screen still mentions version7. (Paul) Solution: Change it to version8.
  • Vim 8.0 release
  • 7.4.2367 Test runner misses a comma. Solution: Add the comma.
  • 7.4.2366 MS-Windows gvim.exe does not have DirectX support. Solution: Add the DIRECTX to the scrip
  • 7.4.2365 Needless line break. Confusing directory name. Solution: Remove line break. Prepend "../"
  • A few more runtime updates.

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.