*kybu Windows build available at https://bitbucket.org/kybu/vim-for-windows-single-drop This includes support for Ruby, Python, Perl, Lua, libiconv and vimproc. All third-party dependencies (e.g. Python DLL) are included in this one installer.

*I'm using 64-bit Windows.

*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. However, there are a few reasons why you may desire a Vim compiled for 64-bit support:

+

**You can ''probably'' use the '''''Vim without Cream''''' install mentioned above. The Cream build is better tested and supported than current 64-bit distributions.

−

::#Editingfiles>4GB in size.

+

** Multiple individuals have published 64-bit builds compiled from the official [http://code.google.com/p/vim/VimMercurialrepository](in no particular order):

"Vim without Cream", as described above, is the best Vim for 32-bit Windows (without compiling it yourself). This section documents known 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 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 <code>gvim-7-3-xxx.exe</code> file.

+

*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-4-xxx.exe</code> 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.

*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.

Ratherthan 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 yourownVim]].

+

ForDebian and Ubuntu-basedLinuxdistributions:

+

:<code># apt-get install vim-gtk</code>

+

For Fedora:

+

:<code># yum install vim-enhanced vim-X11</code>

+

+

Beware that installing distribution's Vim package usually adds a system-wide customization of Vim via .vimrc, .gvimrc, .virc, etc. You may want to examine locations of system .vimrc files in the output of <code>:version</code> and to check what gets sourced on Vim startup with <code>:scriptnames</code>. In case of Debian vim-gtk package, the system-wide customization starts in /etc/vim/ and the actual settings are in /usr/share/vim/vim74/debian.vim or similar.

+

+

Your distribution's package for installing Vim may be very out of date, or it may not have the right Vim features. You may get a better result by downloading the source and building your own Vim because it is very easy to [[Building Vim|build your own Vim]].

"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-4-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.

Linux distributions by default often include a stripped-down version of Vim without scripting or GUI (aliased to command vi or vim). Use your distribution's package manager to install the full-featured Vim version. The relevant package names are usually in the form vim-* .

For Debian and Ubuntu-based Linux distributions:

# apt-get install vim-gtk

For Fedora:

# yum install vim-enhanced vim-X11

Beware that installing distribution's Vim package usually adds a system-wide customization of Vim via .vimrc, .gvimrc, .virc, etc. You may want to examine locations of system .vimrc files in the output of :version and to check what gets sourced on Vim startup with :scriptnames. In case of Debian vim-gtk package, the system-wide customization starts in /etc/vim/ and the actual settings are in /usr/share/vim/vim74/debian.vim or similar.

Your distribution's package for installing Vim may be very out of date, or it may not have the right Vim features. You may get a better result by downloading the source and building your own Vim because it is very easy to build your own Vim.