view READMEdir/README_ami.txt @ 33676:46cd1fc257de v9.0.2075

patch 9.0.2075: TextChangedI may not always trigger Commit: https://github.com/vim/vim/commit/4bca4897a12dfb91b3b27e3083fd5f370bd857d1 Author: Christian Brabandt <cb@256bit.org> Date: Fri Oct 27 19:26:49 2023 +0200 patch 9.0.2075: TextChangedI may not always trigger Problem: TextChangedI may not always trigger Solution: trigger it in more cases: for insert/ append/change operations, and when opening a new line, fixes: #13367 closes: #13375 Signed-off-by: Christian Brabandt <cb@256bit.org> Signed-off-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
author Christian Brabandt <cb@256bit.org>
date Fri, 27 Oct 2023 19:45:04 +0200
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.