Hello Vim users!
Announcing: Vim (Vi IMproved) version 8.0
This the first major Vim release in ten years. There are interesting
new features, many small improvements and lots of bug fixes.
Among the new features are:
- Asynchronous I/O support, channels, JSON
- Partials, Lambdas and Closures
- New style testing
- Viminfo merged by timestamp
- GTK+ 3 support
- MS-Windows DirectX support
Once you have installed Vim 8.0 you can find details about the changes
since Vim 7.4 with:
Or view it online:
If you like Vim, please consider helping poor children in the south of
Where to get it
The best way to obtain the latest Vim is using Git. Summary:
git clone https://github.com/vim/vim.git
More information here: http://www.vim.org/git.php
For MS-Windows most of you will want the self-installing executable:
Information about which files to download for what system:
A list of mirror sites can be found here:
The files available for download:
sources + runtime files, bzip2 compressed:
help files converted to HTML:
Self-installing, includes all runtime files, loads libraries dynamically:
MS-WINDOWS separate files:
GUI binary for Windows 95/98/NT/2000/XP/7:
GUI binary with OLE support:
Console version for Windows NT/2000/XP/7:
Sources for PC (with CR-LF):
Only runtime and sources are provided, no binary:
Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The 32-bit console version for MS-DOS/Windows 95/98
- The 16 bit MS-Windows version
For user questions you can turn to the Vim mailing list. There are a
lot of tips, scripts and solutions. You can ask your Vim questions, but
only if you subscribe. See http://www.vim.org/maillist.php#vim
If you want to help Vim development, discuss new features or get the
latest patches, subscribe to the vim-dev mailing list. See
Subject specific lists:
Macintosh issues: http://www.vim.org/maillist.php#vim-mac
Before you ask a question you should search the archives, someone may
already have given the answer.
Send them to <vim...@vim.org
>. Please describe the problem precisely.
All the time spent on answering mail is subtracted from the time that is
spent on improving Vim! Always give a reproducible example and try to
find out which settings or other things influence the appearance of the
bug. Try starting without your own vimrc file: "vim -u NONE". Try
different machines if possible. See ":help bugs" in Vim.
Alternatively, create an issue at github and/or a pull request.
Please try to write a test that reproduces the problem and will pass
once it is fixed. See https://github.com/vim/vim
"Marriage is a wonderful institution...
but who wants to live in an institution?"
- Groucho Marx
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
\\\ an exciting new programming language -- http://www.Zimbu.org
\\\ help me help AIDS victims -- http://ICCF-Holland.org