Changes: Where to download Vim

Revision as of 02:46, 27 August 2014

Tip 1578 Printable Monobook Previous Next

created 2008 · complexity basic · author Metacosm · version 7.0

This tip outlines some recommended procedures for downloading a Vim executable (that is, a program you can run). Alternatively, you can download the Vim source and build your own Vim.

Windows

Which version of Vim should I use?

I want a fully patched standard Vim for Windows, without compiling it myself.
Get Vim without Cream: The easiest and best solution for Windows users on 32-bit systems is to use the standard Vim at http://sourceforge.net/projects/cream/files/

Under "Newest Files" near the top of the list, there should be a file with a name like gvim-7-3-3.exe
(Vim without Cream, version 7.3.3 = 7.3 with patches 1–3).

The release notes are also available; they show the output of the Vim :version
command which includes what features are in the build.

Click the most recent gvim-7-3-xxx.exe to download.

Run the downloaded installer and accept the license agreement.

On the Choose Components window, expand "Icons, menus and shortcuts".

If you want an "Edit with Vim" item in Explorer's right-click menu, check the box for "Add Contextual Menu".

Finish the install.

It installs a patched standard gvim.exe (GUI) and vim.exe (console), with all help and runtime files.

All installed files are "standard" Vim (the installers named cream-xxx.exe are for a special "Vim with Cream" version).

Includes interfaces for Lua, MzScheme, Perl, Python, Tcl. Ruby 1.8 support was included up until version 7.3.289. More recent versions no longer include Ruby support.

See "Vim without Cream problems" below.
I'm using 64-bit Windows.

You can probably use the Vim without Cream install mentioned above. The Cream build is better tested and supported than current 64-bit distributions.
Multiple individuals have published 64-bit builds compiled from the official Vim Mercurial repository (in no particular order):

http://bintray.com/veegee/generic/vim_x64, including 64-bit python 2.7 and 3.3 support, and lua 5.2 support
https://bitbucket.org/Haroogan/vim-for-windows , supports both x86 (32-bit) and x64 (64-bit) architectures, provides "huge" feature set and scripting interfaces for latest Python 2, Python 3, Ruby, Lua, and Perl
(outdated) http://code.google.com/p/vim-win3264/wiki/Win64Binaries

While the 32-bit Vim should suffice for most users as mentioned, there are a few reasons why a 64-bit Vim is preferable to a 32-bit version on 64-bit systems:

Editing files >4GB in size.
64-bit WinPE does not have a WOW64 subsystem, hence you cannot run a 32-bit executable.
Windows Server 2008 R2 (i.e. Win7 Server) also does not have the WOW64 subsystem, by default, although it is an optional component you can install.
Potential for performance gains, particularly in heavy memory operations like memcpy and memcmp which can be optimized for the 64-bit word size.
Getting 32-bit Vim into a 64-bit "Edit with Vim" context menu entry is tricky.

I want standard Vim (source code to compile for all platforms, or unpatched Windows executables).
Available at http://www.vim.org/download.php
I want an easy-to-use configuration for Windows with common menus and standard keyboard shortcuts.
Cream for BSD, Linux and Windows is available at http://cream.sourceforge.net/download.html

Click "Windows ... One-click installer, includes both Vim and Cream".

You will download a file with a name like cream-0-42-gvim-7-2-245.exe
(Cream version 0.42 with gvim version 7.2.245 = 7.2 with patches 1–245).

Vim without Cream problems

"Vim without Cream", as described above, is the best Vim for 32-bit Windows (without compiling it yourself). This section documents known problems.

The release notes show that it is built with feature +ole which means that it will try to load the OLE interface DLL each time it starts, which would be irritating if you just wanted to run Vim on another computer without bothering to install Vim.
The format of the Sourceforge page occasionally changes and the instructions given above may not exactly match what you see. For standard Vim and gvim without Cream, look for the highest version of the gvim-7-3-xxx.exe file.
In the past, the Sourceforge page required that scripting be enabled in your browser, and, near the bottom of the file list, you had to click "+" next to "Vim" to expand the list of files.

Macintosh

See the versions at http://www.vim.org/download.php#mac

Linux/Unix

Your distribution's package manager probably includes a package for installing Vim, but it is often very out of date. Be sure to look for "vim-huge", "vim-gnome", "vim-full", or similar if you want to go this route.

Rather than downloading a Vim executable, you may get a better result by downloading the source and building your own because it is very easy to build your own Vim.

@@ Line 1: / Line 1: @@
+{{TipNew
-{{TipProposed
-|id=0
+|id=1578
-|previous=0
+|previous=1577
-|next=0
+|next=1579
-|created=February 3, 2008
+|created=2008
 |complexity=basic
-|author=Anon
+|author=Metacosm
 |version=7.0
 |subpage=/200802
-|category1=
+|category1=Getting started
 |category2=
 }}
+This tip outlines some recommended procedures for downloading a Vim executable (that is, a program you can run). Alternatively, you can download the Vim source and [[Building Vim|build your own Vim]].
+==Windows==
 Which version of Vim should I use?
+*I want a fully patched standard Vim for Windows, without compiling it myself.
+*:Get '''''Vim without Cream''''': The easiest and best solution for Windows users on 32-bit systems is to use the standard Vim at http://sourceforge.net/projects/cream/files/
+*:Under "Newest Files" near the top of the list, there should be a file with a name like <code>gvim-7-3-3.exe</code><br>(Vim without Cream, version 7.3.3 = 7.3 with patches 1–3).
+*:The release notes are also available; they show the output of the Vim <code>:version</code><br>command which includes what features are in the build.
+*:Click the most recent <code>gvim-7-3-''xxx''.exe</code> to download.
+*:Run the downloaded installer and accept the license agreement.
+*:On the Choose Components window, expand "Icons, menus and shortcuts".
+*:If you want an "Edit with Vim" item in Explorer's right-click menu, check the box for "Add Contextual Menu".
+*:Finish the install.
+*:It installs a patched standard <code>gvim.exe</code> (GUI) and <code>vim.exe</code> (console), with all help and runtime files.
+*:All installed files are "standard" Vim (the installers named <code>cream-''xxx''.exe</code> are for a special "Vim ''with'' Cream" version).
+*:Includes interfaces for Lua, MzScheme, Perl, Python, Tcl. Ruby 1.8 support was included up until version 7.3.289. More recent versions no longer include Ruby support.
+*:See [[#Vim without Cream problems|"Vim without Cream problems" below]].
+*I'm using 64-bit Windows.
+:*You can ''probably'' use the '''''Vim without Cream''''' install mentioned above. The Cream build is better tested and supported than current 64-bit distributions.
+:*Multiple individuals have published 64-bit builds compiled from the official [http://code.google.com/p/vim/ Vim Mercurial repository] (in no particular order):
+::*http://bintray.com/veegee/generic/vim_x64, including 64-bit python 2.7 and 3.3 support, and lua 5.2 support
+::* https://bitbucket.org/Haroogan/vim-for-windows , supports both x86 (32-bit) and x64 (64-bit) architectures, provides "huge" feature set and scripting interfaces for latest Python 2, Python 3, Ruby, Lua, and Perl
+::*'''(outdated)''' http://code.google.com/p/vim-win3264/wiki/Win64Binaries
+:While the 32-bit Vim should suffice for most users as mentioned, there are a few reasons why a 64-bit Vim is preferable to a 32-bit version on 64-bit systems:
+:# Editing files >4GB in size.
+:# 64-bit WinPE does not have a WOW64 subsystem, hence you cannot run a 32-bit executable.
+:# Windows Server 2008 R2 (i.e. Win7 Server) also does not have the WOW64 subsystem, by default, although it is an optional component you can install.
+:# Potential for performance gains, particularly in heavy memory operations like memcpy and memcmp which can be optimized for the 64-bit word size.
+:#Getting 32-bit Vim into a 64-bit "Edit with Vim" context menu entry is tricky.
+*I want standard Vim (source code to compile for all platforms, or unpatched Windows executables).
+*:Available at http://www.vim.org/download.php
+*I want an easy-to-use configuration for Windows with common menus and standard keyboard shortcuts.
+*:Cream for BSD, Linux and Windows is available at http://cream.sourceforge.net/download.html
+*:Click "Windows ... One-click installer, includes both Vim and Cream".
+*:You will download a file with a name like <code>cream-0-42-gvim-7-2-245.exe</code><br>(Cream version 0.42 with gvim version 7.2.245 = 7.2 with patches 1–245).
+===Vim without Cream problems===
-* I want a "standard" Vim. &rarr; get it from http://www.vim.org/download.php
+"Vim without Cream", as described above, is the best Vim for 32-bit Windows (without compiling it yourself). This section documents known problems.
-* I am very comfortable with the Macintosh way of doing things (HIG). &rarr; check out the versions at http://www.vim.org/download.php#mac
+*The release notes show that it is built with feature +ole which means that it will try to load the OLE interface DLL each time it starts, which would be irritating if you just wanted to run Vim on another computer without bothering to install Vim.
-* I am very comfortable with the Windows way of doing things (CUA). &rarr; check out the Cream versions at http://cream.sourceforge.net/download.html
+*The format of the Sourceforge page occasionally changes and the instructions given above may not exactly match what you see. For standard Vim and gvim without Cream, look for the highest version of the <code>gvim-7-3-xxx.exe</code> file.
-* I want a fully patched standard Vim for Windows, and I don't want to compile it myself! &rarr; Check out Cream's "standard" Vim packages at http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
+*In the past, the Sourceforge page required that scripting be enabled in your browser, and, near the bottom of the file list, you had to click "+" next to "Vim" to expand the list of files.
-* I want to put Vim on a keydrive and use it on a bunch of Windows machines. But standard versions of Vim choke when the keydrive is mounted as a different drive letter on every machine. &rarr; check out GVim Portable http://portablegvim.sourceforge.net/
-==Comments==
+==Macintosh==
+See the versions at http://www.vim.org/download.php#mac
-I like the idea of a tip for download locations, but I'm not sure if we already have one or not. A better tip title might be "Where to download the latest Vim" or something of that nature.
+==Linux/Unix==
-----
+Your distribution's package manager probably includes a package for installing Vim, but it is often very out of date. Be sure to look for "vim-huge", "vim-gnome", "vim-full", or similar if you want to go this route.
-I'm pretty sure we don't have a tip on downloading Vim, so this may as well be it.
+Rather than downloading a Vim executable, you may get a better result by downloading the source and building your own because it is very easy to [[Building Vim|build your own Vim]].
-The [[Main Page]] links to [[Vim documentation]] and I would eventually like that page cleaned up with a new section about downloading and building Vim. It would have a link to this tip, and hopefully a link to another tip about building Vim (one for Unix and one for Windows).
+==Comments==
-The "Which version of Vim should I use?" heading is quite nice, but I agree that the tip should be renamed. Is "the latest" helpful? Maybe just "Where to download Vim" or "How to download Vim"?? I think "Downloading Vim" is a bit too blunt.
-The following seem relevant (may need to merge):
-*[[VimTip46|46 Win32 binaries with perl, python, and tcl]]
-*[[VimTip531|531 Build Vim in Windows with Cygwin]]
-*[[VimTip714|714 Version independent installation of Vim on Windows]]
-*[[VimTip744|744 Get latest releases for syntax highlighting, runtime, plugins etc]]
-*[[VimTip747|747 Easily keep runtime files up to date]]
-*http://www.vim.org/download.php
-----
-I'd name it "Where to download Vim" and put in lots of redirects, including all your suggestions, the current title, as well as "Vim installers" and "Installing Vim". This is an important enough topic that it needs to be ridiculously easy to find. --[[User:Fritzophrenic|Fritzophrenic]] 14:34, 8 October 2008 (UTC)