Mercurial > vim
view READMEdir/README_ami.txt @ 27843:532a0c5de1ec v8.2.4447
patch 8.2.4447: Vim9: can still use s:var in a compiled function
Commit: https://github.com/vim/vim/commit/afa048f0d4b5d63f2192c9ba340a9eb8b0822985
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Feb 22 20:43:36 2022 +0000
patch 8.2.4447: Vim9: can still use s:var in a compiled function
Problem: Vim9: can still use s:var in a compiled function.
Solution: Disallow using s:var for Vim9 script. (closes https://github.com/vim/vim/issues/9824)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 22 Feb 2022 21:45:03 +0100 |
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.