Mercurial > vim
annotate README_ami.txt @ 5090:8b7baf39a345 v7.3.1288
updated for version 7.3.1288
Problem: The first ":echo 'hello'" command output doesn't show. Mapping
for <S-F3> gets triggered during startup.
Solution: Add debugging code for the termresponse. When receiving the "Co"
entry and when setting 'ambiwidth' redraw right away if possible.
Add redraw_asap(). Don't set 'ambiwidth' if it already had the
right value. Do the 'ambiwidth' check in the second row to avoid
confusion with <S-F3>.
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Wed, 03 Jul 2013 12:45:31 +0200 |
| parents | 073ff46fe397 |
| children | 6ec6b7ff2d43 |
| rev | line source |
|---|---|
|
2572
ee53a39d5896
Last changes for the 7.3 release!
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
1 README_ami.txt for version 7.3 of Vim: Vi IMproved. |
| 7 | 2 |
| 3 This file explains the installation of Vim on Amiga systems. | |
| 4 See README.txt for general information about Vim. | |
| 5 | |
| 6 | |
| 7 Unpack the distributed files in the place where you want to keep them. It is | |
| 8 wise to have a "vim" directory to keep your vimrc file and any other files you | |
| 9 change. The distributed files go into a subdirectory. This way you can | |
| 10 easily upgrade to a new version. For example: | |
| 11 | |
| 12 dh0:editors/vim contains your vimrc and modified files | |
| 13 dh0:editors/vim/vim54 contains the Vim version 5.4 distributed files | |
| 14 dh0:editors/vim/vim55 contains the Vim version 5.5 distributed files | |
| 15 | |
| 16 You would then unpack the archives like this: | |
| 17 | |
| 18 cd dh0:editors | |
| 19 tar xf t:vim60bin.tar | |
| 20 tar xf t:vim60rt.tar | |
| 21 | |
| 22 Set the $VIM environment variable to point to the top directory of your Vim | |
| 23 files. For the above example: | |
| 24 | |
| 25 set VIM=dh0:editors/vim | |
| 26 | |
| 27 Vim version 5.4 will look for your vimrc file in $VIM, and for the runtime | |
| 28 files in $VIM/vim54. See ":help $VIM" for more information. | |
| 29 | |
| 30 Make sure the Vim executable is in your search path. Either copy the Vim | |
| 31 executable to a directory that is in your search path, or (preferred) modify | |
| 32 the search path to include the directory where the Vim executable is. |