view READMEdir/README_ami.txt @ 30533:4f6c0ca7530b v9.0.0602

patch 9.0.0602: new TypeScript extensions are not recognized Commit: https://github.com/vim/vim/commit/7fc6c0e4dab4e80b9806a973936af54276468513 Author: rhysd <lin90162@yahoo.co.jp> Date: Tue Sep 27 11:57:13 2022 +0100 patch 9.0.0602: new TypeScript extensions are not recognized Problem: New TypeScript extensions are not recognized. Solution: Recognize .mts and .cts files. (closes https://github.com/vim/vim/issues/11237)
author Bram Moolenaar <Bram@vim.org>
date Tue, 27 Sep 2022 13:00:05 +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.