Mercurial > vim
view READMEdir/README_ami.txt @ 23346:2060f53b7c17 v8.2.2216
patch 8.2.2216: Vim9: range with missing colon can be hard to spot
Commit: https://github.com/vim/vim/commit/6e2c2c50bada4e3f5c7234902c0bdd64f66619ac
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Dec 25 19:25:45 2020 +0100
patch 8.2.2216: Vim9: range with missing colon can be hard to spot
Problem: Vim9: range with missing colon can be hard to spot.
Solution: Include the start of the range in the error. (closes https://github.com/vim/vim/issues/7543)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Fri, 25 Dec 2020 19:30:03 +0100 |
parents | af69c9335223 |
children | f8116058ca76 |
line wrap: on
line source
README_ami.txt for version 8.2 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:vim82bin.tar tar xf t:vim82rt.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.