Vim Tips Wiki
Don't have an account?
Register
Register
in: VimTip, Getting started, Todo

Changes: Where to download Vim

Back to page
Edit
(→‎Comments: couple more tips related to building Vim)
(add sections: make it easier to find your system and ignore the others)
Line 11: Line 11:
 
|category2=
  
|category2=
 
}}
  
}}
  +
==Any platform==
  +
It is ''very'' easy to build Vim from the source code. We even have some [[:Category:Building_Vim|tips for building Vim]]. In general, it takes four steps:
  +
#Get dependencies. On Unix-like systems, <tt>apt-get build-dep vim-gnome</tt> or similar can do this for you. On Windows, there ''are'' no dependencies, unless you want to build Vim to use an external DLL for Python, Perl, Ruby, or Scheme.
  +
#[[Getting_the_Vim_source_with_Mercurial|Get the Vim source code from Mercurial]].
  +
#Change to the directory with the Vim source code and run "make".
  +
#Do a "make install" or manually copy necessary files to somewhere Vim knows to use. See {{help|$VIMRUNTIME}} for details and our tip on [[Version_independent_installation_of_Vim_on_Windows|manually locating your Vim files]].
  +
  +
With that said...you certainly don't ''need'' to compile Vim yourself, if you don't want to.
  +
  +
==Windows==
 
Which version of Vim should I use?
  
Which version of Vim should I use?
 
*I want a fully patched standard Vim for Windows, without compiling it myself.
  
*I want a fully patched standard Vim for Windows, without compiling it myself.
Line 31: Line 41:
 
*I want to put Vim on a keydrive and use it on a bunch of Windows machines,<br>but standard versions of Vim choke when the keydrive is mounted as a different drive letter.
  
*I want to put Vim on a keydrive and use it on a bunch of Windows machines,<br>but standard versions of Vim choke when the keydrive is mounted as a different drive letter.
 
*:Check out GVim Portable http://portablegvim.sourceforge.net/
  
*:Check out GVim Portable http://portablegvim.sourceforge.net/
−
*I want Vim on a Macintosh.
  
⚫
*:See the versions at http://www.vim.org/download.php#mac
  
   
−
==Vim without Cream problems==
 +
===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.
  
"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 it.
  
*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 it.
 
*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 <tt>gvim-7-2-xxx.exe</tt> 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 <tt>gvim-7-2-xxx.exe</tt> 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.
  +
  +
==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.
  +
  +
But, it is very easy to build your own Vim, as mentioned previously.
   
 
==Comments==
  
==Comments==
Line 47: Line 63:
   
 
The following seem relevant (may need to merge):
  
The following seem relevant (may need to merge):
−
*[[VimTip46|46 Win32 binaries with perl, python, and tcl]]
  
 
*[[VimTip222|222 Building vim with color on HP-UX]]
  
*[[VimTip222|222 Building vim with color on HP-UX]]
 
*[[VimTip376|376 Build Vim with your name included]] want to develop this as our "how to build" tip
  
*[[VimTip376|376 Build Vim with your name included]] want to develop this as our "how to build" tip
Line 57: Line 72:
   
 
----
  
----
  +
  +
I think you're saying the same thing, but I certainly recommend leaving the "building" tips separate from this one. I've tried to add info at the top of this tip to indicate how easy it is, but I know most people just want a "grab and go" download they can use. Maybe we should move that section? It probably needs a little work, still. --[[User:Fritzophrenic|Fritzophrenic]] 20:23, July 10, 2010 (UTC)

Revision as of 20:23, 10 July 2010

Tip 1578 Printable Monobook Previous Next

created February 3, 2008 · complexity basic · author Metacosm · version 7.0

Any platform

It is very easy to build Vim from the source code. We even have some tips for building Vim. In general, it takes four steps:

  1. Get dependencies. On Unix-like systems, apt-get build-dep vim-gnome or similar can do this for you. On Windows, there are no dependencies, unless you want to build Vim to use an external DLL for Python, Perl, Ruby, or Scheme.
  2. Get the Vim source code from Mercurial.
  3. Change to the directory with the Vim source code and run "make".
  4. Do a "make install" or manually copy necessary files to somewhere Vim knows to use. See :help $VIMRUNTIME for details and our tip on manually locating your Vim files.

With that said...you certainly don't need to compile Vim yourself, if you don't want to.

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-2-411.exe
    (Vim without Cream, version 7.2.411 = 7.2 with patches 1–411).
    You can click the icon in the "Notes/Subscribe" column to see the output of the :version command
    (that shows what features are in the build).
    Click the most recent gvim-7-2-xxx.exe to download; run the download to 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 Perl, Python, Ruby, Tcl and MzScheme interfaces.
    See "Vim without Cream problems" below.
  • I'm using 64-bit Windows.
    See information and download.
  • 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).
  • 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.
    Check out GVim Portable http://portablegvim.sourceforge.net/

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 it.
  • 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-2-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.

But, it is very easy to build your own Vim, as mentioned previously.

Comments

 TO DO 
This can be our tip on downloading 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).

The following seem relevant (may need to merge):

I think you're saying the same thing, but I certainly recommend leaving the "building" tips separate from this one. I've tried to add info at the top of this tip to indicate how easy it is, but I know most people just want a "grab and go" download they can use. Maybe we should move that section? It probably needs a little work, still. --Fritzophrenic 20:23, July 10, 2010 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.