Mercurial > vim
view READMEdir/README_ami.txt @ 14891:66176f8735aa v8.1.0457
patch 8.1.0457: win32 console: key mappings don't work
commit https://github.com/vim/vim/commit/0cc7b2d6ccc79d6ce69f5405f9914a42cb4f615e
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Oct 7 15:49:56 2018 +0200
patch 8.1.0457: win32 console: key mappings don't work
Problem: Win32 console: key mappings don't work.
Solution: Use another solution for the keypad keys that doesn't break
mappings. Some values will be negative. (Mike Williams)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 07 Oct 2018 16:00:06 +0200 |
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.