view READMEdir/README_ami.txt @ 12990:ec86ba548446 v8.0.1371

patch 8.0.1371: Shift-Insert doesn't always work in MS-Windows console commit https://github.com/vim/vim/commit/feeb4d0901c7b16958e8f02ffcdac83b605b0b43 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Dec 5 15:14:46 2017 +0100 patch 8.0.1371: Shift-Insert doesn't always work in MS-Windows console Problem: Shift-Insert doesn't always work in MS-Windows console. Solution: Handle K_NUL differently if the second character is more than one byte. (Yasuhiro Matsumoto, closes #2381)
author Christian Brabandt <cb@256bit.org>
date Tue, 05 Dec 2017 15:15:05 +0100
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.