Mercurial > vim
view READMEdir/README_ami.txt @ 12351:4e61b77cd96f v8.0.1055
patch 8.0.1055: bufline test hangs on MS-Windows
commit https://github.com/vim/vim/commit/11aa62f8f949bb590b4d7792a334885fba5e4137
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Sep 4 22:56:01 2017 +0200
patch 8.0.1055: bufline test hangs on MS-Windows
Problem: Bufline test hangs on MS-Windows.
Solution: Avoid message for writing file. Source shared.vim when running
test individually.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Mon, 04 Sep 2017 23:00:05 +0200 |
parents | 9f48eab77d62 |
children | 1174611ad715 |
line wrap: on
line source
README_ami.txt for version 8.0 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:vim80bin.tar tar xf t:vim80rt.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.