Mercurial > vim
view READMEdir/README_ami.txt @ 31614:f3c7e573b7be v9.0.1139
patch 9.0.1139: cannot create a new object in a compiled function
Commit: https://github.com/vim/vim/commit/46ab925937d04c208d905cfb50bd8ffcae11e466
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Jan 3 14:01:21 2023 +0000
patch 9.0.1139: cannot create a new object in a compiled function
Problem: Cannot create a new object in a compiled function.
Solution: Compile the instructins to create a new object.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 03 Jan 2023 15:15:03 +0100 |
parents | f8116058ca76 |
children | 4635e43f2c6f |
line wrap: on
line source
README_ami.txt for version 9.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:vim90bin.tar tar xf t:vim90rt.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.