summaryrefslogtreecommitdiffstats
path: root/READMEdir
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--READMEdir/Contents23
-rw-r--r--READMEdir/Contents.infobin0 -> 582 bytes
-rw-r--r--READMEdir/README.txt.infobin0 -> 582 bytes
-rw-r--r--READMEdir/README_ami.txt32
-rw-r--r--READMEdir/README_ami.txt.infobin0 -> 582 bytes
-rw-r--r--READMEdir/README_amibin.txt12
-rw-r--r--READMEdir/README_amibin.txt.infobin0 -> 582 bytes
-rw-r--r--READMEdir/README_amisrc.txt11
-rw-r--r--READMEdir/README_amisrc.txt.infobin0 -> 582 bytes
-rw-r--r--READMEdir/README_bindos.txt16
-rw-r--r--READMEdir/README_dos.txt149
-rw-r--r--READMEdir/README_extra.txt42
-rw-r--r--READMEdir/README_haiku.txt13
-rw-r--r--READMEdir/README_mac.txt28
-rw-r--r--READMEdir/README_ole.txt20
-rw-r--r--READMEdir/README_os2.txt5
-rw-r--r--READMEdir/README_os390.txt117
-rw-r--r--READMEdir/README_src.txt8
-rw-r--r--READMEdir/README_srcdos.txt12
-rw-r--r--READMEdir/README_unix.txt10
-rw-r--r--READMEdir/README_vms.txt48
-rw-r--r--READMEdir/README_w32s.txt6
-rw-r--r--READMEdir/Vim.infobin0 -> 624 bytes
-rw-r--r--READMEdir/Xxd.infobin0 -> 835 bytes
-rw-r--r--READMEdir/runtime.infobin0 -> 624 bytes
-rw-r--r--READMEdir/src.infobin0 -> 624 bytes
-rw-r--r--READMEdir/vimdir.infobin0 -> 624 bytes
27 files changed, 552 insertions, 0 deletions
diff --git a/READMEdir/Contents b/READMEdir/Contents
new file mode 100644
index 0000000..c8107bb
--- /dev/null
+++ b/READMEdir/Contents
@@ -0,0 +1,23 @@
+Vim Vi IMproved. A clone of the UNIX text editor Vi. Very useful
+ for editing programs and other plain ASCII text. Full Vi
+ compatibility and includes all Ex commands. Extra features
+ above Vi: Multilevel undo, multiple windows, syntax
+ highlighting, command line history, folding, improved command
+ line editing, command typeahead display, command to display
+ yank buffers, possibility to edit binary files, file name
+ stack, support for Manx QuickFix and other compiler's error
+ messages, shows current file name in window title, on-line
+ help, rectangular cut/paste, etc., etc., etc...
+
+ Version 8.2. Also runs under UNIX, MS-Windows, Mac, etc.
+ vim82rt.tgz contains the documentation and syntax files.
+ vim82bin.tgz contains the binaries.
+ vim82src.tgz contains the sources.
+ Author: Bram Moolenaar et al.
+
+
+Xxd Hex dumper and reader. Can be used to view files as hex, edit
+ them and write them back. Can also be used to patch files.
+
+ Version 1.10 (1997 May 22)
+ Author: Juergen Weigert
diff --git a/READMEdir/Contents.info b/READMEdir/Contents.info
new file mode 100644
index 0000000..9e855c7
--- /dev/null
+++ b/READMEdir/Contents.info
Binary files differ
diff --git a/READMEdir/README.txt.info b/READMEdir/README.txt.info
new file mode 100644
index 0000000..e7fa114
--- /dev/null
+++ b/READMEdir/README.txt.info
Binary files differ
diff --git a/READMEdir/README_ami.txt b/READMEdir/README_ami.txt
new file mode 100644
index 0000000..7ea4332
--- /dev/null
+++ b/READMEdir/README_ami.txt
@@ -0,0 +1,32 @@
+README_ami.txt for version 8.2 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:vim82bin.tar
+ tar xf t:vim82rt.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.
diff --git a/READMEdir/README_ami.txt.info b/READMEdir/README_ami.txt.info
new file mode 100644
index 0000000..912436d
--- /dev/null
+++ b/READMEdir/README_ami.txt.info
Binary files differ
diff --git a/READMEdir/README_amibin.txt b/READMEdir/README_amibin.txt
new file mode 100644
index 0000000..962567d
--- /dev/null
+++ b/READMEdir/README_amibin.txt
@@ -0,0 +1,12 @@
+README_amibin.txt for version 8.2 of Vim: Vi IMproved.
+
+See "README.txt" for general information about Vim.
+See "README_ami.txt" for installation instructions for the Amiga.
+These files are in the runtime archive (vim82rt.tgz).
+
+
+The Amiga "bin" archive contains the Vim executable for the Amiga. It was
+compiled with "big" features.
+
+Postscript printing is not included to avoid requiring floating point
+computations.
diff --git a/READMEdir/README_amibin.txt.info b/READMEdir/README_amibin.txt.info
new file mode 100644
index 0000000..bdc3f02
--- /dev/null
+++ b/READMEdir/README_amibin.txt.info
Binary files differ
diff --git a/READMEdir/README_amisrc.txt b/READMEdir/README_amisrc.txt
new file mode 100644
index 0000000..6c4f76c
--- /dev/null
+++ b/READMEdir/README_amisrc.txt
@@ -0,0 +1,11 @@
+README_amisrc.txt for version 8.2 of Vim: Vi IMproved.
+
+See "README.txt" for general information about Vim.
+See "README_ami.txt" for installation instructions for the Amiga.
+These files are in the runtime archive (vim82rt.tgz).
+
+
+The Amiga source archive contains the files needed to compile Vim on the
+Amiga.
+
+See "src/INSTALLami.txt" for instructions on how to compile Vim on the Amiga.
diff --git a/READMEdir/README_amisrc.txt.info b/READMEdir/README_amisrc.txt.info
new file mode 100644
index 0000000..476af9a
--- /dev/null
+++ b/READMEdir/README_amisrc.txt.info
Binary files differ
diff --git a/READMEdir/README_bindos.txt b/READMEdir/README_bindos.txt
new file mode 100644
index 0000000..d16c8d8
--- /dev/null
+++ b/READMEdir/README_bindos.txt
@@ -0,0 +1,16 @@
+README_bindos.txt for version 8.2 of Vim: Vi IMproved.
+
+See "README.txt" for general information about Vim.
+See "README_dos.txt" for installation instructions for MS-DOS and MS-Windows.
+These files are in the runtime archive (vim82rt.zip).
+
+
+There are several binary distributions of Vim for the PC. You would normally
+pick only one of them, but it's also possible to install several.
+These ones are available (the version number may differ):
+ vim82w32.zip Windows 95/98/NT/etc. console version
+ gvim82.zip Windows 95/98/NT/etc. GUI version
+ gvim82ole.zip Windows 95/98/NT/etc. GUI version with OLE
+
+You MUST also get the runtime archive (vim82rt.zip).
+The sources are also available (vim82src.zip).
diff --git a/READMEdir/README_dos.txt b/READMEdir/README_dos.txt
new file mode 100644
index 0000000..3f08612
--- /dev/null
+++ b/READMEdir/README_dos.txt
@@ -0,0 +1,149 @@
+README_dos.txt for version 8.2 of Vim: Vi IMproved.
+
+This file explains the installation of Vim on MS-Windows systems.
+See "README.txt" for general information about Vim.
+
+There are two ways to install Vim:
+A. Use the self-installing .exe file.
+B. Unpack .zip files and run the install.exe program.
+
+
+A. Using the self-installing .exe
+---------------------------------
+
+This is mostly self-explaining. Just follow the prompts and make the
+selections. A few things to watch out for:
+
+- When an existing installation is detected, you are offered to first remove
+ this. The uninstall program is then started while the install program waits
+ for it to complete. Sometimes the windows overlap each other, which can be
+ confusing. Be sure the complete the uninstalling before continuing the
+ installation. Watch the taskbar for uninstall windows.
+
+- When selecting a directory to install Vim, use the same place where other
+ versions are located. This makes it easier to find your _vimrc file. For
+ example "C:\Program Files\vim" or "D:\vim". A name ending in "vim" is
+ preferred.
+
+- After selecting the directory where to install Vim, clicking on "Next" will
+ start the installation.
+
+
+B. Using .zip files
+-------------------
+
+These are the normal steps to install Vim from the .zip archives:
+
+1. Go to the directory where you want to put the Vim files. Examples:
+ cd C:\
+ cd D:\editors
+ If you already have a "vim" directory, go to the directory in which it is
+ located. Check the $VIM setting to see where it points to:
+ set VIM
+ For example, if you have
+ C:\vim\vim82
+ do
+ cd C:\
+ Binary and runtime Vim archives are normally unpacked in the same location,
+ on top of each other.
+
+2. Unpack the zip archives. This will create a new directory "vim\vim82",
+ 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 gvim82.zip
+ unzip vim82w32.zip
+
+ You need to unpack the runtime archive and at least one of the binary
+ archives. When using more than one binary version, be careful not to
+ overwrite one version with the other, the names of the executables
+ "vim.exe" and "gvim.exe" are the same.
+
+ After you unpacked the files, you can still move the whole directory tree
+ to another location. That is where they will stay, the install program
+ won't move or copy the runtime files.
+
+3. Change to the new directory:
+ cd vim\vim82
+ Run the "install.exe" program. It will ask you a number of questions about
+ how you would like to have your Vim setup. Among these are:
+ - You can tell it to write a "_vimrc" file with your preferences in the
+ parent directory.
+ - It can also install an "Edit with Vim" entry in the Windows Explorer
+ popup menu.
+ - You can have it create batch files, so that you can run Vim from the
+ console or in a shell. You can select one of the directories in your
+ $PATH. If you skip this, you can add Vim to the search path manually:
+ The simplest is to add a line to your autoexec.bat. Examples:
+ set path=%path%;C:\vim\vim82
+ set path=%path%;D:\editors\vim\vim82
+ - Create entries for Vim on the desktop and in the Start menu.
+
+That's it!
+
+
+Remarks:
+
+- If Vim can't find the runtime files, ":help" won't work and the GUI version
+ won't show a menubar. Then you need to set the $VIM environment variable to
+ point to the top directory of your Vim files. Example:
+ set VIM=C:\editors\vim
+ Vim version 8.2 will look for your vimrc file in $VIM, and for the runtime
+ files in $VIM/vim82. See ":help $VIM" for more information.
+
+- 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 it with the path you use)
+ Your own files:
+ C:\vim\_vimrc Your personal vimrc.
+ C:\vim\_viminfo Dynamic info for 'viminfo'.
+ C:\vim\vimfiles\ftplugin\*.vim Filetype plugins
+ C:\vim\... Other files you made.
+ Distributed files:
+ C:\vim\vim82\vim.exe The Vim version 8.2 executable.
+ C:\vim\vim82\doc\*.txt The version 8.2 documentation files.
+ C:\vim\vim82\bugreport.vim A Vim version 8.2 script.
+ C:\vim\vim82\... Other version 8.2 distributed files.
+ In this case the $VIM environment variable would be set like this:
+ set VIM=C:\vim
+ Then $VIMRUNTIME will automatically be set to "$VIM\vim82". Don't add
+ "vim82" to $VIM, that won't work.
+
+- You can put your Vim executable anywhere else. If the executable is not
+ with the other 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
+
+- If you have told the "install.exe" program to add the "Edit with Vim" menu
+ entry, you can remove it by running the "uninstall.exe". See
+ ":help win32-popup-menu".
+
+- In Windows 95/98/NT you can create a shortcut to Vim. This works for all
+ DOS and Win32 console versions. For the console version this gives you the
+ opportunity to set defaults for the Console where Vim runs in.
+
+ 1. On the desktop, click right to get a menu. Select New/Shortcut.
+ 2. In the dialog, enter Command line: "C:\command.com". Click "Next".
+ 3. Enter any name. Click "Finish".
+ The new shortcut will appear on the desktop.
+ 4. With the mouse pointer on the new shortcut, click right to get a menu.
+ Select Properties.
+ 5. In the Program tab, change the "Cmdline" to add "/c" and the name of the
+ Vim executable. Examples:
+ C:\command.com /c C:\vim\vim82\vim.exe
+ C:\command.com /c D:\editors\vim\vim82\vim.exe
+ 6. Select the font, window size, etc. that you like. If this isn't
+ possible, select "Advanced" in the Program tab, and deselect "MS-DOS
+ mode".
+ 7. Click OK.
+
+ For gvim, you can use a normal shortcut on the desktop, and set the size of
+ the Window in your $VIM/_gvimrc:
+ set lines=30 columns=90
+
+
+For further information, type one of these inside Vim:
+ :help dos
+ :help win32
diff --git a/READMEdir/README_extra.txt b/READMEdir/README_extra.txt
new file mode 100644
index 0000000..4f22d1b
--- /dev/null
+++ b/READMEdir/README_extra.txt
@@ -0,0 +1,42 @@
+README_extra.txt for version 8.2 of Vim: Vi IMproved.
+
+These extra files of Vim are for special purposes. This README explains what
+the files are for. For general information about Vim, see the "README.txt"
+file.
+
+
+farsi/* Files for the Farsi (persian) language. If you don't
+ know what Farsi is, this is not for you.
+
+src/if_sniff.* Interface to SNiFF. If you don't know what SNiFF is,
+ this is not for you.
+
+src/os_amiga.* Files for the Amiga port.
+
+src/os_msdos.*
+src/os_dos.* Files for the MS-DOS port.
+
+src/os_mac.* Files for the Mac port.
+
+src/os_vms* Files for the VMS port.
+
+src/os_w32*
+src/os_win32.* Files for the Win32 port.
+
+src/gui_w32.* Files for the Win32 GUI.
+src/gui_w48.* Files for the Win32 and Win16 GUI.
+src/Make_mvc.mak MS Visual C++ makefile for the Win32 GUI.
+runtime/rgb.txt File with color definitions for the Win32 GUI.
+
+src/if_ole.* OLE automation interface, for MS Windows 95 and NT.
+
+src/VisVim/* Integration of Win32 GUI with MS Visual Developer
+ Studio.
+
+src/GvimExt/* DLL for the "Edit with Vim" context menu entry
+
+nsis/* NSIS script to build the self-installing MS-Windows exe
+
+runtime/doc/*.man Preprocessed manual pages.
+
+runtime/macros/file_select.vim Vim script to browse directories (Unix only).
diff --git a/READMEdir/README_haiku.txt b/READMEdir/README_haiku.txt
new file mode 100644
index 0000000..860b40b
--- /dev/null
+++ b/READMEdir/README_haiku.txt
@@ -0,0 +1,13 @@
+README_haiku.txt for version 8.2 of Vim: Vi IMproved.
+
+This file explains the installation of Vim on Haiku operating system.
+See "README.txt" for general information about Vim.
+
+Preferred (and easy) way to get Vim on Haiku is to use default Haiku
+software repository HaikuPorts. To get Vim:
+
+- Open HaikuDepot application and search for "vim" package, then install,
+- Open a Terminal and type "pkgman install vim", then follow instructions.
+
+If you prefer to install Vim from source, follow the instructions on
+"runtime/doc/os_haiku.txt", "Compiling Vim" section.
diff --git a/READMEdir/README_mac.txt b/READMEdir/README_mac.txt
new file mode 100644
index 0000000..22671c2
--- /dev/null
+++ b/READMEdir/README_mac.txt
@@ -0,0 +1,28 @@
+README_mac.txt for version 8.2 of Vim: Vi IMproved.
+
+This file explains the installation of Vim on Macintosh systems.
+See "README.txt" for general information about Vim.
+
+
+To build from sources, like on Unix
+
+1. Get the build tools: "clang" and "make". These can be installed with the
+ "CommandLineTools" package. If you don't have one, do
+ xcode-select --install
+ Just like for any software development with OS X.
+
+2. Get the source code. Best is to use git (which you need to install first),
+ see http://www.vim.org/git.php
+ Or you can download and unpack the Unix tar archive, see
+ http://www.vim.org/download.php
+
+3. Go to the top directory of the source tree, do
+ make
+ sudo make install
+ A newly built vim will be installed under "/usr/local".
+
+
+If you can't manage to make this work, there is a fallback using Homebrew:
+
+1. Install Homebrew from http://brew.sh/
+2. Install latest Vim with: brew install vim
diff --git a/READMEdir/README_ole.txt b/READMEdir/README_ole.txt
new file mode 100644
index 0000000..839dd6a
--- /dev/null
+++ b/READMEdir/README_ole.txt
@@ -0,0 +1,20 @@
+README_ole.txt for version 8.2 of Vim: Vi IMproved.
+
+This archive contains gvim.exe with OLE interface and VisVim.
+This version of gvim.exe can also load a number of interface dynamically (you
+can optionally install the .dll files for each interface).
+It is only for MS-Windows 95/98/ME/NT/2000/XP.
+
+Also see the README_bindos.txt, README_dos.txt and README.txt files.
+
+Be careful not to overwrite the OLE gvim.exe with the non-OLE gvim.exe when
+unpacking another binary archive! Check the output of ":version":
+ Win32s - "MS-Windows 16/32 bit GUI version"
+ Win32 - "MS-Windows 32 bit GUI version"
+Win32 with OLE - "MS-Windows 32 bit GUI version with OLE support"
+
+For further information, type this inside Vim:
+ :help if_ole
+
+Furthermore, this archive contains VISVIM.DLL. It can be used to integrate
+the OLE gvim with Microsoft Visual Developer Studio. See VisVim/README.txt.
diff --git a/READMEdir/README_os2.txt b/READMEdir/README_os2.txt
new file mode 100644
index 0000000..3a9cdf1
--- /dev/null
+++ b/READMEdir/README_os2.txt
@@ -0,0 +1,5 @@
+README_os2.txt for version 8.2 of Vim: Vi IMproved.
+
+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.
diff --git a/READMEdir/README_os390.txt b/READMEdir/README_os390.txt
new file mode 100644
index 0000000..3601495
--- /dev/null
+++ b/READMEdir/README_os390.txt
@@ -0,0 +1,117 @@
+README_os390.txt for version 8.2 of Vim: Vi IMproved.
+
+This readme explains how to build Vim on z/OS. Formerly called OS/390.
+See "README.txt" for general information about Vim.
+
+Most likely there are not many users out there using Vim on z/OS. So chances
+are good, that some bugs are still undiscovered.
+
+Getting the source to z/OS:
+==========================
+
+First get the source code in one big tar file and ftp it a binary to z/OS. If
+the tar file is initially compressed with gzip (tar.gz) or bzip2 (tar.bz2)
+uncompress it on your PC, as these tools are (most likely) not available on
+the mainframe.
+
+To reduce the size of the tar file you might compress it into a zip file. On
+z/OS Unix you might have the command "jar" from java to uncompress a zip. Use:
+ jar xvf <zip file name>
+
+Unpack the tar file on z/OS with
+ pax -o from=ISO8859-1,to=IBM-1047 -rf vim.tar
+
+Note: The Vim source contains a few bitmaps etc which will be destroyed by
+this command, but these files are not needed on zOS (at least not for the
+console version).
+
+
+Compiling:
+==========
+
+Vim can be compiled with or without GUI support. For 7.4 only the compilation
+without GUI was tested. Below is a section about compiling with X11 but this
+is from an earlier version of Vim.
+
+Console only:
+-------------
+
+If you build VIM without X11 support, compiling and building is nearly
+straightforward.
+
+Change to the vim directory and do:
+
+ # Don't use c89!
+ # Allow intermixing of compiler options and files.
+
+ $ export CC=cc
+ $ export _CC_CCMODE=1
+ $./configure --with-features=big --without-x --enable-gui=no
+ $ cd src
+ $ make
+
+ There may be warnings:
+ - include files not found (libc, sys/param.h, ...)
+ - Redeclaration of ... differs from ...
+ -- just ignore them.
+
+ $ make test
+
+ This will produce lots of garbage on your screen (including error
+ messages). Don't worry.
+
+ If the test stops at one point in vim (might happen in test 11), just
+ press :q!
+
+ Expected test failures:
+ 11: If you don't have gzip installed
+ 24: test of backslash sequences in regexp are ASCII dependent
+ 42: Multibyte is not supported on z/OS
+ 55: ASCII<->EBCDIC sorting
+ 57: ASCII<->EBCDIC sorting
+ 58: Spell checking is not supported with EBCDIC
+ 71: Blowfish encryption doesn't work
+
+ $ make install
+
+
+With X11:
+---------
+
+WARNING: This instruction was not tested with Vim 7.4 or later.
+
+There are two ways for building VIM with X11 support. The first way is simple
+and results in a big executable (~13 Mb), the second needs a few additional
+steps and results in a much smaller executable (~4.5 Mb). These examples
+assume you want Motif.
+
+ The easy way:
+ $ export CC=cc
+ $ export _CC_CCMODE=1
+ $ ./configure --enable-max-features --enable-gui=motif
+ $ cd src
+ $ make
+
+ With this VIM is linked statically with the X11 libraries.
+
+ The smarter way:
+ Make VIM as described above. Then create a file named 'link.sed' with the
+ following content (see src/link.390):
+
+ s/-lXext *//g
+ s/-lXmu *//g
+ s/-lXm */\/usr\/lib\/Xm.x /g
+ s/-lX11 */\/usr\/lib\/X11.x /g
+ s/-lXt *//g
+ s/-lSM */\/usr\/lib\/SM.x /g
+ s/-lICE */\/usr\/lib\/ICE.x /g
+
+ Then do:
+ $ rm vim
+ $ make
+
+ Now Vim is linked with the X11-DLLs.
+
+ See the Makefile and the file link.sh on how link.sed is used.
+
+
diff --git a/READMEdir/README_src.txt b/READMEdir/README_src.txt
new file mode 100644
index 0000000..935830f
--- /dev/null
+++ b/READMEdir/README_src.txt
@@ -0,0 +1,8 @@
+README_src.txt for version 8.2 of Vim: Vi IMproved.
+
+The source archive contains the files needed to compile Vim on Unix systems.
+It is packed for Unix systems (NL line separator).
+
+For more information, see the README.txt file that comes with the runtime
+archive (vim-8.2-rt.tar.gz). To be able to run Vim you MUST get the runtime
+archive too!
diff --git a/READMEdir/README_srcdos.txt b/READMEdir/README_srcdos.txt
new file mode 100644
index 0000000..ca016bd
--- /dev/null
+++ b/READMEdir/README_srcdos.txt
@@ -0,0 +1,12 @@
+README_srcdos.txt for version 8.2 of Vim: Vi IMproved.
+
+See "README.txt" for general information about Vim.
+See "README_dos.txt" for installation instructions for MS-Windows.
+These files are in the runtime archive (vim82rt.zip).
+
+
+The DOS source archive contains the files needed to compile Vim on MS-Windows.
+It is packed for MS-Windows systems, with CR-LF. It also includes the VisVim
+sources.
+
+See "src/INSTALLpc.txt" for instructions on how to compile Vim on the PC.
diff --git a/READMEdir/README_unix.txt b/READMEdir/README_unix.txt
new file mode 100644
index 0000000..4ed11f0
--- /dev/null
+++ b/READMEdir/README_unix.txt
@@ -0,0 +1,10 @@
+README_unix.txt for version 8.2 of Vim: Vi IMproved.
+
+This file explains the installation of Vim on Unix systems.
+See "README.txt" for general information about Vim.
+
+
+When you use the source distribution, "make install" is used to install Vim.
+See the "INSTALL" file in the "src" directory.
+
+If you use a compiled package, follow the instructions for the package.
diff --git a/READMEdir/README_vms.txt b/READMEdir/README_vms.txt
new file mode 100644
index 0000000..d38fa98
--- /dev/null
+++ b/READMEdir/README_vms.txt
@@ -0,0 +1,48 @@
+README_vms.txt for version 8.2 of Vim: Vi IMproved.
+
+This file explains the installation of Vim on VMS systems.
+See "README.txt" in the runtime archive for information about Vim.
+
+
+Most information can be found in the on-line documentation. Use ":help vms"
+inside Vim. Or get the runtime files and read runtime/doc/os_vms.txt to find
+out how to install and configure Vim with runtime files etc.
+
+To compile Vim yourself you need three archives:
+ vim-X.X-rt.tar.gz runtime files
+ vim-X.X-src.tar.gz source files
+ vim-X.X-extra.tar.gz extra source files
+
+Compilation is recommended, in order to make sure that the correct
+libraries are used for your specific system. Read about compiling in
+src/INSTALLvms.txt.
+
+To use the binary version, you need one of these archives:
+
+ vim-XX-exe-ia64-gui.zip IA64 GUI/Motif executables
+ vim-XX-exe-ia64-gtk.zip IA64 GUI/GTK executables
+ vim-XX-exe-ia64-term.zip IA64 console executables
+ vim-XX-exe-axp-gui.zip Alpha GUI/Motif executables
+ vim-XX-exe-axp-gtk.zip Alpha GUI/GTK executables
+ vim-XX-exe-axp-term.zip Alpha console executables
+ vim-XX-exe-vax-gui.zip VAX GUI executables
+ vim-XX-exe-vax-term.zip VAX console executables
+
+and of course
+ vim-XX-runtime.zip runtime files
+
+The binary archives contain: vim.exe, ctags.exe, xxd.exe files,
+but there are also prepared "deploy ready" archives:
+
+vim-XX-ia64.zip GUI and console executables with runtime and
+ help files for IA64 systems
+vim-XX-axp.zip GUI and console executables with runtime and
+ help files for Alpha systems
+vim-XX-vax.zip GUI and console executables with runtime and
+ help files for VAX systems
+
+GTK builds need LIBGTK library installed.
+
+These executables and up to date patches for OpenVMS system are downloadable
+from http://www.polarhome.com/vim/ or ftp://ftp.polarhome.com/pub/vim/
+
diff --git a/READMEdir/README_w32s.txt b/READMEdir/README_w32s.txt
new file mode 100644
index 0000000..742a655
--- /dev/null
+++ b/READMEdir/README_w32s.txt
@@ -0,0 +1,6 @@
+README_w32s.txt for version 8.2 of Vim: Vi IMproved.
+
+This file used to explain the installation of Vim on MS-Windows 3.1 and 3.11
+systems. However, support for MS-Windows 3.1 and 3.11 has been removed in
+patch 7.4.1364.
+See "README.txt" for general information about Vim.
diff --git a/READMEdir/Vim.info b/READMEdir/Vim.info
new file mode 100644
index 0000000..5c465ff
--- /dev/null
+++ b/READMEdir/Vim.info
Binary files differ
diff --git a/READMEdir/Xxd.info b/READMEdir/Xxd.info
new file mode 100644
index 0000000..7ae7643
--- /dev/null
+++ b/READMEdir/Xxd.info
Binary files differ
diff --git a/READMEdir/runtime.info b/READMEdir/runtime.info
new file mode 100644
index 0000000..6ff0468
--- /dev/null
+++ b/READMEdir/runtime.info
Binary files differ
diff --git a/READMEdir/src.info b/READMEdir/src.info
new file mode 100644
index 0000000..1ab7c6c
--- /dev/null
+++ b/READMEdir/src.info
Binary files differ
diff --git a/READMEdir/vimdir.info b/READMEdir/vimdir.info
new file mode 100644
index 0000000..ddb2a14
--- /dev/null
+++ b/READMEdir/vimdir.info
Binary files differ