Mercurial > vim
view READMEdir/README_ami.txt @ 31914:0aef9a59f24c v9.0.1289
patch 9.0.1289: a newer version of clang can be used for CI
Commit: https://github.com/vim/vim/commit/43e234e8b48caf59d6895a31628dad0bba4fd5c8
Author: Philip H <47042125+pheiduck@users.noreply.github.com>
Date: Mon Feb 6 20:22:48 2023 +0000
patch 9.0.1289: a newer version of clang can be used for CI
Problem: A newer version of clang can be used for CI.
Solution: Switch from clang-15 to clang-16. (closes https://github.com/vim/vim/issues/11577)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 06 Feb 2023 21:30:04 +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.