Mercurial > vim
view READMEdir/README_ami.txt @ 20931:2351948e193d v8.2.1017
patch 8.2.1017: Appveyor output doesn't show MinGW console features
Commit: https://github.com/vim/vim/commit/1089374130862e5c19745d3ff4314f0c5690baf1
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Jun 19 22:37:47 2020 +0200
patch 8.2.1017: Appveyor output doesn't show MinGW console features
Problem: Appveyor output doesn't show MinGW console features.
Solution: List the features of the console build.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Fri, 19 Jun 2020 22:45:05 +0200 |
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.