-
Notifications
You must be signed in to change notification settings - Fork 397
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Problem: Still a few OS/2 pieces remain. Solution: Delete more.
- Loading branch information
Showing
4 changed files
with
4 additions
and
76 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,58 +1,5 @@ | ||
README_os2.txt for version 7.4 of Vim: Vi IMproved. | ||
|
||
This file explains the installation of Vim on OS/2 systems. | ||
This file used to explain the installation of Vim on OS/2 systems. | ||
However, support for OS/2 has been removed in patch 7.4.1008. | ||
See "README.txt" for general information about Vim. | ||
|
||
|
||
NOTE: You will need two archives: | ||
vim74rt.zip contains the runtime files (same as for the PC version) | ||
vim74os2.zip contains the OS/2 executables | ||
|
||
1. Go to the directory where you want to put the Vim files. Examples: | ||
cd C:\ | ||
cd D:\editors | ||
|
||
2. Unpack the zip archives. This will create a new directory "vim/vim74", | ||
in which all the distributed Vim files are placed. Since the directory | ||
name includes the version number, it is unlikely that you overwrite | ||
existing files. | ||
Examples: | ||
pkunzip -d vim74os2.zip | ||
unzip vim74os2.zip | ||
|
||
After you unpacked the files, you can still move the whole directory tree | ||
to another location. | ||
|
||
3. Add the directory where vim.exe is to your path. The simplest is to add a | ||
line to your autoexec.bat. Examples: | ||
set path=%path%;C:\vim\vim74 | ||
set path=%path%;D:\editors\vim\vim74 | ||
|
||
That's it! | ||
|
||
|
||
Extra remarks: | ||
|
||
- To avoid confusion between distributed files of different versions and your | ||
own modified vim scripts, it is recommended to use this directory layout: | ||
("C:\vim" is used here as the root, replace with the path you use) | ||
Your own files: | ||
C:\vim\_vimrc Your personal vimrc. | ||
C:\vim\_viminfo Dynamic info for 'viminfo'. | ||
C:\vim\... Other files you made. | ||
Distributed files: | ||
C:\vim\vim74\vim.exe The Vim version 7.4 executable. | ||
C:\vim\vim74\doc\*.txt The version 7.4 documentation files. | ||
C:\vim\vim74\bugreport.vim A Vim version 7.4 script. | ||
C:\vim\vim74\... Other version 7.4 distributed files. | ||
In this case the $VIM environment variable would be set like this: | ||
set VIM=C:\vim | ||
|
||
- You can put your Vim executable anywhere else. If the executable is not | ||
with the other distributed Vim files, you should set $VIM. The simplest is | ||
to add a line to your autoexec.bat. Examples: | ||
set VIM=c:\vim | ||
set VIM=d:\editors\vim | ||
|
||
For further information, type this inside Vim: | ||
:help os2 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.