Mercurial > vim
view READMEdir/README_ami.txt @ 14505:3f1a17863b73 v8.1.0266
patch 8.1.0266: parsing Ex address range is not a separate function
commit https://github.com/vim/vim/commit/ee8415bc5998792fab6f4dcf289d027856e05b89
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Aug 10 23:13:12 2018 +0200
patch 8.1.0266: parsing Ex address range is not a separate function
Problem: Parsing Ex address range is not a separate function.
Solution: Refactor do_one_cmd() to separate address parsing.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 10 Aug 2018 23:15:04 +0200 |
parents | 1174611ad715 |
children | af69c9335223 |
line wrap: on
line source
README_ami.txt for version 8.1 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:vim81bin.tar tar xf t:vim81rt.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.