abstract
| - Set up a directory hierarchy as follows: vim\ vimuntime\ vimuntime\syntax\ vimuntime\plugin\ vimuntime\ftplugin\ vimuntime\indent\ vimuntime\doc\ vimuntime\colors\ vimuntime\compiler\ vimuntime\macros\ vimuntime ools\ vimuntime utor\ vim\vimfiles\ vim\vimfiles\syntax\ vim\vimfiles\plugin\ vim\vimfiles\ftplugin\ vim\vimfiles\indent\ vim\vimfiles\doc\ vim\vimfiles\colors\ vim\vimfiles\compiler\ Now put the runtime files and executables in place. You can get these files by copying from the default install location, or you can get the Vim source code and runtime files from Mercurial and compile the executables yourself. 1.
* Put gvim.exe and/or vim.exe, vimrun.exe, xxd.exe, gvimext.dll into vim\ 2.
* Put all the remaining .vim, .txt, and other non-executable files that are distributed under vim\vimxy\ in to vimuntime\ 3.
* Put the contents of the distributed vim\vimxy\plugin\ in to vimuntime\plugin\ and so on for all the other subdirectories of vim\vimxy\ including syntax, ftplugin, indent, doc, colors, compiler, macros, tools, tutor. 4.
* Put your _vimrc and _gvimrc files in vim\ with the executables. 5.
* Either ensure that vim\ is in your path, or create shortcuts and/or batch (bat or cmd) files that can start vim\(g)vim.exe for you. 6.
* If you have downloaded any scripts from vim.sf.net or elsewhere, put them in the appropriate spot in the vim\vimfiles\ hierarchy where they stay separate from the official distribution files in vimuntime\. In this way, when you upgrade (g)vim to a newer version, you will not have to copy, move or do anything with these extra files. For example, plugins from vim.sf.net go into vim\vimfiles\plugin\ and color scheme files go into vim\vimfiles\colors\ etc. 7.
* You are all done. $VIM and $VIMRUNTIME will be set automatically for you. They will point to vim\ and vimuntime\ respectively. See [ help $VIM] and [ help $VIMRUNTIME] if you want to know how this works (and potential pitfalls).
|