Mercurial > vim
view README_ami.txt @ 7231:a4d10eec6356 v7.4.924
commit https://github.com/vim/vim/commit/32d03b34ac8a34a962f57847fc431a2b4e14efea
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Nov 19 13:46:48 2015 +0100
patch 7.4.924
Problem: DEVELOPER_DIR gets reset by configure.
Solution: Do not reset DEVELOPER_DIR when there is no --with-developer-dir
argument. (Kazuki Sakamoto, closes #482)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 19 Nov 2015 14:00:05 +0100 |
parents | 359743c1f59a |
children |
line wrap: on
line source
README_ami.txt for version 7.4 of Vim: Vi IMproved. This file explains the installation of Vim on Amiga systems. See README.txt for general information about Vim. Unpack the distributed files in the place where you want to keep them. It is wise to have a "vim" directory to keep your vimrc file and any other files you change. The distributed files go into a subdirectory. This way you can easily upgrade to a new version. For example: dh0:editors/vim contains your vimrc and modified files dh0:editors/vim/vim54 contains the Vim version 5.4 distributed files dh0:editors/vim/vim55 contains the Vim version 5.5 distributed files You would then unpack the archives like this: cd dh0:editors tar xf t:vim60bin.tar tar xf t:vim60rt.tar Set the $VIM environment variable to point to the top directory of your Vim files. For the above example: set VIM=dh0:editors/vim Vim version 5.4 will look for your vimrc file in $VIM, and for the runtime files in $VIM/vim54. See ":help $VIM" for more information. Make sure the Vim executable is in your search path. Either copy the Vim executable to a directory that is in your search path, or (preferred) modify the search path to include the directory where the Vim executable is.