Mercurial > vim
view READMEdir/README_ami.txt @ 15794:0d8291665b59 v8.1.0904
patch 8.1.0904: USE_LONG_FNAME never defined
commit https://github.com/vim/vim/commit/00f148d2f24fb955ab36b0833811582c58b2cf2f
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Feb 12 22:37:27 2019 +0100
patch 8.1.0904: USE_LONG_FNAME never defined
Problem: USE_LONG_FNAME never defined.
Solution: Remove using USE_LONG_FNAME. (Ken Takata, closes https://github.com/vim/vim/issues/3938)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 12 Feb 2019 22:45:06 +0100 |
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.