doc: remove legacy os_*.txt

keeping os_dos.txt, see #1115

10 files changed, 0 insertions, 1982 deletions

diff --git a/runtime/doc/Makefile b/runtime/doc/Makefile
index 16ce4d9082..14adf2432e 100644
--- a/runtime/doc/Makefile
+++ b/runtime/doc/Makefile
@@ -59,17 +59,9 @@ DOCS = \
 	nvim_intro.txt \
 	nvim_python.txt \
 	options.txt \
-	os_390.txt \
-	os_amiga.txt \
-	os_beos.txt \
 	os_dos.txt \
 	os_mac.txt \
-	os_mint.txt \
-	os_os2.txt \
-	os_qnx.txt \
-	os_risc.txt \
 	os_unix.txt \
-	os_vms.txt \
 	os_win32.txt \
 	pattern.txt \
 	pi_getscript.txt \
@@ -190,17 +182,9 @@ HTMLS = \
 	nvim_intro.html \
 	nvim_python.html \
 	options.html \
-	os_390.html \
-	os_amiga.html \
-	os_beos.html \
 	os_dos.html \
 	os_mac.html \
-	os_mint.html \
-	os_os2.html \
-	os_qnx.html \
-	os_risc.html \
 	os_unix.html \
-	os_vms.html \
 	os_win32.html \
 	pattern.html \
 	pi_getscript.html \
diff --git a/runtime/doc/os_390.txt b/runtime/doc/os_390.txt
deleted file mode 100644
index 5501b8009b..0000000000
--- a/runtime/doc/os_390.txt
+++ /dev/null
@@ -1,134 +0,0 @@
-*os_390.txt*    For Vim version 7.4.  Last change: 2010 May 30
-
-
-		  VIM REFERENCE MANUAL	  by Ralf Schandl
-
-					*zOS* *z/OS* *OS390* *os390* *MVS*
-This file contains the particulars for the z/OS UNIX version of Vim.
-
-1. ASCII/EBCDIC dependent scripts	|zOS-has-ebcdic|
-2. Putty and Colors                     |zOS-PuTTY|
-3. Motif Problems			|zOS-Motif|
-4. Bugs					|zOS-Bugs|
-5. Limitations     			|zOS-limitations|
-6. Open source on z/OS UNIX		|zOS-open-source|
-
-Contributors: ~
-The port to z/OS UNIX was done by Ralf Schandl for the Redbook mentioned
-below.
-
-Changes, bug-reports, or both by:
-
-	David Moore
-	Anthony Giorgio
-	and others
-
-==============================================================================
-1. ASCII/EBCDIC dependent scripts	*OS390-has-ebcdic* *zOS-has-ebcdic*
-
-For the internal script language the feature "ebcdic" was added.  With this
-you can fix ASCII dependent scripts like this:
->
-    if has("ebcdic")
-	let space = 64
-    else
-	let space = 32
-    endif
-<
-
-==============================================================================
-2. PuTTY and Colors			*OS390-PuTTY* *zOS-PuTTY*
-
-If you see problems with syntax highlighting or screen corruptions when you
-connect to z/OS using Putty, try the following:
-
-- Configure Putty as "vt220" terminal (Connection->Data)
-- Add the following 3 lines to your vimrc:
-
->
-    set t_AB=[4%p1%dm
-    set t_AF=[3%p1%dm
-    set t_CO=8
-<
-
-Note:  is one character use <C-V><Esc> to enter it.
-
-==============================================================================
-3. Motif Problems			*OS390-Motif* *zOS-Motif*
-
-Note: Seen with Vim 6.*, never tested since.
-
-It seems that in porting the Motif library to z/OS, a translation from EBCDIC
-to ASCII for the accelerator characters of the pull-down menus was forgotten.
-Even after I tried to hand convert the menus, the accelerator keys continued
-to only work for the opening of menus (like <Alt-F> to open the file menu).
-They still do not work for the menu items themselves (like <Alt-F>O to open
-the file browser).
-
-There is no solution for this yet.
-
-==============================================================================
-4. Bugs					*OS390-bugs* *zOS-Bugs*
-
-- Vim will consistently hang when a large amount of text is selected in
-  visual block mode.  This may be due to a memory corruption issue.  Note that
-  this occurs in both the terminal and gui versions.
-
-==============================================================================
-5. Limitations     			*OS390-limitations* *zOS-limitations*
-
-- No binary search in tag files.
-  The program /bin/sort sorts by ASCII value by default.  This program is
-  normally used by ctags to sort the tags.  There might be a version of
-  ctags out there, that does it right, but we can't be sure.  So this seems to
-  be a permanent restriction.
-
-- The cscope interface (|cscope|) doesn't work for the version of cscope
-  that we use on our mainframe.  We have a copy of version 15.0b12, and it
-  causes Vim to hang when using the "cscope add" command.  I'm guessing that
-  the binary format of the cscope database isn't quite what Vim is expecting.
-  I've tried to port the current version of cscope (15.3) to z/OS, without
-  much success.  If anyone is interested in trying, drop me a line if you
-  make any progress.
-
-- No glib/gtk support.  I have not been able to successfully compile glib on
-  z/OS UNIX.  This means you'll have to live without the pretty gtk toolbar.
- 
-Disabled at compile time:
-    - Multibyte support         (|multibyte|)
-    - Right-to-left mode        (|rileft|)
-    - Farsi key map             (|Farsi|)
-    - Arabic language support   (|Arabic|)
-    - Spell checking            (|spell|)
-
-Never tested:
-    - Perl interface		(|perl|)
-    - Encryption support	(|encryption|)
-    - Langmap			(|'langmap'|)
-    - Python support		(|Python|)
-    - Right-to-left mode	(|'rightleft'|)
-    - SNiFF+ interface		(|sniff|)
-    - TCL interface		(|tcl|)
-    ...
-
-==============================================================================
-6. Open source on z/OS UNIX		*OS390-open-source* *zOS-open-source*
-
-If you are interested in other Open Source Software on z/OS UNIX, have a
-look at the following Redbook:
-
-    Mike MacIsaac et al
-    "Open Source Software for z/OS and OS/390 UNIX"
-    IBM Form Number: SG24-5944-01
-    ISBN: 0738424633
-    http://www-03.ibm.com/systems/resources/servers_eserver_zseries_zos_unix_redbook_sg245944.pdf
-
-Also look at:
-    http://www.redbooks.ibm.com
-    http://www-03.ibm.com/systems/z/os/zos/features/unix/
-    http://www-03.ibm.com/systems/z/os/zos/features/unix/library/IBM+Redbooks/index.html
-
-
-
-------------------------------------------------------------------------------
- vim:tw=78:fo=tcq2:ts=8:ft=help:norl:
diff --git a/runtime/doc/os_amiga.txt b/runtime/doc/os_amiga.txt
deleted file mode 100644
index b9ac611129..0000000000
--- a/runtime/doc/os_amiga.txt
+++ /dev/null
@@ -1,147 +0,0 @@
-*os_amiga.txt*  For Vim version 7.4.  Last change: 2010 Aug 14
-
-
-		  VIM REFERENCE MANUAL    by Bram Moolenaar
-
-
-							*Amiga*
-This file contains the particularities for the Amiga version of Vim.
-There is also a section specifically for |MorphOS| below.
-
-NOTE: The Amiga code is still included, but has not been maintained or tested.
-
-Installation on the Amiga:
-- Assign "VIM:" to the directory where the Vim "doc" directory is.  Vim will
-  look for the file "VIM:doc/help.txt" (for the help command).
-  Setting the environment variable $VIM also works.  And the other way around:
-  when $VIM used and it is not defined, "VIM:" is used.
-- With DOS 1.3 or earlier: Put "arp.library" in "libs:".  Vim must have been
-  compiled with the |+ARP| feature enabled.  Make sure that newcli and run are
-  in "C:" (for executing external commands).
-- Put a shell that accepts a command with "-c" (e.g. "Csh" from Fish disk
-  624) in "c:" or in any other directory that is in your search path (for
-  executing external commands).
-
-If you have sufficient memory you can avoid startup delays by making Vim and
-csh resident with the command "rez csh vim".  You will have to put
-"rezlib.library" in your "libs:" directory.  Under 2.0 you will need rez
-version 0.5.
-
-If you do not use digraphs, you can save some memory by recompiling without
-the |+digraphs| feature.  If you want to use Vim with other terminals you can
-recompile with the TERMCAP option.  Vim compiles with Manx 5.x and SAS 6.x.
-See the makefiles and feature.h.
-
-If you notice Vim crashes on some files when syntax highlighting is on, or
-when using a search pattern with nested wildcards, it might be that the stack
-is too small.  Try increasing the stack size.  In a shell use the Stack
-command before launching Vim.  On the Workbench, select the Vim icon, use the
-workbench "Info" menu and change the Stack field in the form.
-
-If you want to use different colors set the termcap codes:
-	t_mr (for inverted text)
-	t_md (for bold text)
-	t_me (for normal text after t_mr and t_md)
-	t_so (for standout mode)
-	t_se (for normal text after t_so)
-	t_us (for underlined text)
-	t_ue (for normal text after t_us)
-	t_ZH (for italic text)
-	t_ZR (for normal text after t_ZH)
-
-Standard ANSI escape sequences are used.  The codes are:
-30 grey char   40 grey cell   >0 grey background    0 all attributes off
-31 black char  41 black cell  >1 black background   1 boldface
-32 white char  42 white cell  >2 white background   2 faint
-33 blue char   43 blue cell   >3 blue background    3 italic
-34 grey char   44 grey cell   >4 grey background    4 underscore
-35 black char  45 black cell  >5 black background   7 reverse video
-36 white char  46 white cell  >6 white background   8 invisible
-37 blue char   47 blue cell   >7 blue background
-
-The codes with '>' must be the last.  The cell and background color should be
-the same.  The codes can be combined by separating them with a semicolon.  For
-example to get white text on a blue background: >
-  :set t_me=^V<Esc>[0;32;43;>3m
-  :set t_se=^V<Esc>[0;32;43;>3m
-  :set t_ue=^V<Esc>[0;32;43;>3m
-  :set t_ZR=^V<Esc>[0;32;43;>3m
-  :set t_md=^V<Esc>[1;32;43;>3m
-  :set t_mr=^V<Esc>[7;32;43;>3m
-  :set t_so=^V<Esc>[0;31;43;>3m
-  :set t_us=^V<Esc>[4;32;43;>3m
-  :set t_ZH=^V<Esc>[3;32;43;>3m
-
-When using multiple commands with a filter command, e.g. >
-  :r! echo this; echo that
-Only the output of the last command is used.  To fix this you have to group the
-commands.  This depends on the shell you use (that is why it is not done
-automatically in Vim).  Examples: >
-  :r! (echo this; echo that)
-  :r! {echo this; echo that}
-
-Commands that accept a single file name allow for embedded spaces in the file
-name.  However, when using commands that accept several file names, embedded
-spaces need to be escaped with a backslash.
-
-------------------------------------------------------------------------------
-Vim for MorphOS							*MorphOS*
-
-[this section mostly by Ali Akcaagac]
-
-For the latest info about the MorphOS version:
-	http://www.akcaagac.com/index_vim.html
-
-
-Problems ~
-
-There are a couple of problems which are not MorphOS related but more Vim and
-UN*X related.  When starting up Vim in ram: it complains with a nag requester
-from MorphOS please simply ignore it.  Another problem is when running Vim as
-is some plugins will cause a few problems which you can ignore as well.
-Hopefully someone will be fixing it over the time.
-
-To pass all these problems for now you can either run:
-
-	vim <file to be edited>
-
-or if you want to run Vim plain and enjoy the motion of Helpfiles etc. it then
-would be better to enter:
-
-	vim --noplugins <of course you can add a file>
-
-
-Installation ~
-
-1) Please copy the binary 'VIM' file to c:
-2) Get the Vim runtime package from:
-
-	ftp://ftp.vim.org/pub/vim/amiga/vim62rt.tgz
-
-   and unpack it in your 'Apps' directory of the MorphOS installation.  For me
-   this would create following directory hierarchy:
-
-	MorphOS:Apps/Vim/Vim62/...
-
-3) Add the following lines to your s:shell-startup (Important!).
-
-	;Begin VIM
-	Set VIM=MorphOS:Apps/Vim/Vim62
-	Assign HOME: ""
-	;End VIM
-
-4) Copy the '.vimrc' file to s:
-
-5) There is also a file named 'color-sequence' included in this archive.  This
-   will set the MorphOS Shell to show ANSI colors.  Please copy the file to s:
-   and change the s:shell-startup to:
-
-	;Begin VIM
-	Set VIM=MorphOS:Apps/Vim/Vim62
-	Assign HOME: ""
-	Execute S:Color-Sequence
-	Cls
-	;End VIM
-
-
- vim:tw=78:ts=8:ft=help:norl:
diff --git a/runtime/doc/os_beos.txt b/runtime/doc/os_beos.txt
deleted file mode 100644
index 5099ae6126..0000000000
--- a/runtime/doc/os_beos.txt
+++ /dev/null
@@ -1,319 +0,0 @@
-*os_beos.txt*	For Vim version 7.4.  Last change: 2010 Aug 14
-
-
-		  VIM REFERENCE MANUAL    by Bram Moolenaar
-
-
-							*BeOS* *BeBox*
-This is a port of Vim 5.1 to the BeOS Preview Release 2 (also known as PR2)
-or later.
-
-This file contains the particularities for the BeBox/BeOS version of Vim.  For
-matters not discussed in this file, Vim behaves very much like the Unix
-|os_unix.txt| version.
-
- 1. General			|beos-general|
- 2. Compiling Vim		|beos-compiling|
- 3. Timeout in the Terminal	|beos-timeout|
- 4. Unicode vs. Latin1		|beos-unicode|
- 5. The BeOS GUI		|beos-gui|
- 6. The $VIM directory		|beos-vimdir|
- 7. Drag & Drop			|beos-dragndrop|
- 8. Single Launch vs. Multiple
-    Launch			|beos-launch|
- 9. Fonts			|beos-fonts|
-10. The meta key modifier	|beos-meta|
-11. Mouse key mappings		|beos-mouse|
-12. Color names			|beos-colors|
-13. Compiling with Perl		|beos-perl|
-
-
-1. General						*beos-general*
-
-The default syntax highlighting mostly works with different foreground colors
-to highlight items.  This works best if you set your Terminal window to a
-darkish background and light letters.  Some middle-grey background (for
-instance (r,g,b)=(168,168,168)) with black letters also works nicely.  If you
-use the default light background and dark letters, it may look better to
-simply reverse the notion of foreground and background color settings.  To do
-this, add this to your .vimrc file (where <Esc> may need to be replaced with
-the escape character): >
-
-  :if &term == "beos-ansi"
-  :    set t_AB=<Esc>[3%dm
-  :    set t_AF=<Esc>[4%dm
-  :endif
-
-
-2. Compiling Vim					*beos-compiling*
-
-From the Advanced Access Preview Release (AAPR) on, Vim can be configured with
-the standard configure script.  To get the compiler and its flags right, use
-the following command-line in the shell (you can cut and paste it in one go):
-
-CC=$BE_C_COMPILER CFLAGS="$BE_DEFAULT_C_FLAGS -O7" \
-    ./configure --prefix=/boot/home/config
-
-$BE_C_COMPILER is usually "mwcc", $BE_DEFAULT_C_FLAGS is usually "-I- -I."
-
-When configure has run, and you wish to enable GUI support, you must edit the
-config.mk file so that the lines with GUI_xxx refer to $(BEOSGUI_xxx) instead
-of $(NONE_xxx).
-Alternatively you can make this change in the Makefile; it will have a
-more permanent effect.  Search for "NONE_".
-
-After compilation you need to add the resources to the binary.  Add the
-following few lines near the end (before the line with "exit $exit_value") of
-the link.sh script to do this automatically.
-
-    rmattr BEOS:TYPE vim
-    copyres os_beos.rsrc vim
-    mimeset vim
-
-Also, create a dummy file "strip":
-
-    #!/bin/sh
-    mimeset $1
-    exit 0
-
-You will need it when using "make install" to install Vim.
-
-Now type "make" to compile Vim, then "make install" to install it.
-
-If you want to install Vim by hand, you must copy Vim to $HOME/config/bin, and
-create a bunch of symlinks to it ({g,r,rg}{vim,ex,view}).  Furthermore you must
-copy Vim's configuration files to $HOME/config/share/vim:
-vim-5.0s/{*.vim,doc,syntax}.  For completeness, you should also copy the nroff
-manual pages to $HOME/config/man/man1.  Don't forget ctags/ctags and xxd/xxd!
-
-Obviously, you need the unlimited linker to actually link Vim.  See
-http://www.metrowerks.com for purchasing the CodeWarrior compiler for BeOS.
-There are currently no other linkers that can do the job.
-
-This won't be able to include the Perl or Python interfaces even if
-you have the appropriate files installed. |beos-perl|
-
-
-3. Timeout in the Terminal				*beos-timeout*
-
-Because some POSIX/UNIX features are still missing[1], there is no direct OS
-support for read-with-timeout in the Terminal.  This would mean that you cannot
-use :mappings of more than one character, unless you also :set notimeout.
-|'timeout'|
-
-To circumvent this problem, I added a workaround to provide the necessary
-input with timeout by using an extra thread which reads ahead one character.
-As a side effect, it also makes Vim recognize when the Terminal window
-resizes.
-
-Function keys are not supported in the Terminal since they produce very
-indistinctive character sequences.
-
-These problems do not exist in the GUI.
-
-[1]: there is no select() on file descriptors; also the termios VMIN and VTIME
-settings do not seem to work properly.  This has been the case since DR7 at
-least and still has not been fixed as of PR2.
-
-							*beos-unicode*
-4. Unicode vs. Latin1					*beos-utf8*
-
-BeOS uses Unicode and UTF-8 for text strings (16-bit characters encoded to
-8-bit characters).  Vim assumes ISO-Latin1 or other 8-bit character codes.
-This does not produce the desired results for non-ASCII characters.  Try the
-command :digraphs to see.  If they look messed up, use :set isprint=@ to
-(slightly) improve the display of ISO-Latin1 characters 128-255.  This works
-better in the GUI, depending on which font you use (below).
-
-You may also use the /boot/bin/xtou command to convert UTF-8 files from (xtou
--f iso1 filename) or to (xtou -t iso1 filename) ISO-Latin1 characters.
-
-
-5. The BeOS GUI						*beos-gui*
-
-The BeOS GUI is no longer included.  It was not maintained for a while and
-most likely didn't work.  If you want to work on this: get the Vim 6.x version
-and merge it back in.
-
-
-6. The $VIM directory					*beos-vimdir*
-
-$VIM is the symbolic name for the place where Vims support files are stored.
-The default value for $VIM is set at compile time and can be determined with >
-
-  :version
-
-The normal value is /boot/home/config/share/vim.  If you don't like it you can
-set the VIM environment variable to override this, or set 'helpfile' in your
-.vimrc: >
-
-  :if version >= 500
-  :    set helpfile=~/vim/vim54/doc/help.txt
-  :    syntax on
-  :endif
-
-
-7. Drag & Drop						*beos-dragndrop*
-
-You can drop files and directories on either the Vim icon (starts a new Vim
-session, unless you use the File Types application to set Vim to be "Single
-Launch") or on the Vim window (starts editing the files).  Dropping a folder
-sets Vim's current working directory. |:cd| |:pwd| If you drop files or
-folders with either SHIFT key pressed, Vim changes directory to the folder
-that contains the first item dropped.  When starting Vim, there is no need to
-press shift: Vim behaves as if you do.
-
-Files dropped set the current argument list. |argument-list|
-
-
-8. Single Launch vs. Multiple Launch			*beos-launch*
-
-As distributed Vim's Application Flags (as seen in the FileTypes preference)
-are set to Multiple Launch.  If you prefer, you can set them to Single Launch
-instead.  Attempts to start a second copy of Vim will cause the first Vim to
-open the files instead.  This works from the Tracker but also from the command
-line.  In the latter case, non-file (option) arguments are not supported.
-
-NB: Only the GUI version has a BApplication (and hence Application Flags).
-This section does not apply to the GUI-less version, should you compile one.
-
-
-9. Fonts						*beos-fonts*
-
-Set fonts with >
-
-  :set guifont=Courier10_BT/Roman/10
-
-where the first part is the font family, the second part the style, and the
-third part the size.  You can use underscores instead of spaces in family and
-style.
-
-Best results are obtained with monospaced fonts (such as Courier).  Vim
-attempts to use all fonts in B_FIXED_SPACING mode but apparently this does not
-work for proportional fonts (despite what the BeBook says).
-
-Vim also tries to use the B_ISO8859_1 encoding, also known as ISO Latin 1.
-This also does not work for all fonts.  It does work for Courier, but not for
-ProFontISOLatin1/Regular (strangely enough).  You can verify this by giving the >
-
-  :digraphs
-
-command, which lists a bunch of characters with their ISO Latin 1 encoding.
-If, for instance, there are "box" characters among them, or the last character
-isn't a dotted-y, then for this font the encoding does not work.
-
-If the font you specify is unavailable, you get the system fixed font.
-
-Standard fixed-width system fonts are:
-
-	      ProFontISOLatin1/Regular
-		  Courier10_BT/Roman
-		  Courier10_BT/Italic
-		  Courier10_BT/Bold
-		  Courier10_BT/Bold_Italic
-
-Standard proportional system fonts are:
-
-		    Swis721_BT/Roman
-		    Swis721_BT/Italic
-		    Swis721_BT/Bold
-		    Swis721_BT/Bold_Italic
-		Dutch801_Rm_BT/Roman
-		Dutch801_Rm_BT/Italic
-		Dutch801_Rm_BT/Bold
-		Dutch801_Rm_BT/Bold_Italic
-		   Baskerville/Roman
-		   Baskerville/Italic
-		   Baskerville/Bold
-		   Baskerville/Bold_Italic
-		 SymbolProp_BT/Regular
-
-Try some of them, just for fun.
-
-
-10. The meta key modifier				*beos-meta*
-
-The META key modifier is obtained by the left or right OPTION keys.  This is
-because the ALT (aka COMMAND) keys are not passed to applications.
-
-
-11. Mouse key mappings					*beos-mouse*
-
-Vim calls the various mouse buttons LeftMouse, MiddleMouse and RightMouse.  If
-you use the default Mouse preference settings these names indeed correspond to
-reality.  Vim uses this mapping:
-
-    Button 1 -> LeftMouse,
-    Button 2 -> RightMouse,
-    Button 3 -> MiddleMouse.
-
-If your mouse has fewer than 3 buttons you can provide your own mapping from
-mouse clicks with modifier(s) to other mouse buttons.  See the file
-vim-5.x/macros/swapmous.vim for an example.		|gui-mouse-mapping|
-
-
-12. Color names						*beos-colors*
-
-Vim has a number of color names built-in.  Additional names are read from the
-file $VIMRUNTIME/rgb.txt, if present.  This file is basically the color
-database from X.  Names used from this file are cached for efficiency.
-
-
-13. Compiling with Perl					*beos-perl*
-
-Compiling with Perl support enabled is slightly tricky.  The Metrowerks
-compiler has some strange ideas where to search for include files.  Since
-several include files with Perl have the same names as some Vim header
-files, the wrong ones get included.  To fix this, run the following Perl
-script while in the vim-5.0/src directory: >
-
-   preproc.pl > perl.h
-
-    #!/bin/env perl
-    # Simple #include expander, just good enough for the Perl header files.
-
-    use strict;
-    use IO::File;
-    use Config;
-
-    sub doinclude
-    {
-	my $filename = $_[0];
-	my $fh = new IO::File($filename, "r");
-	if (defined $fh) {
-	    print "/* Start of $filename */\n";
-
-	    while (<$fh>) {
-		if (/^#include "(.*)"/) {
-		    doinclude($1);
-		    print "/* Back in $filename */\n";
-		} else {
-		    print $_;
-		}
-	    }
-	    print "/* End of $filename */\n";
-
-	    undef $fh;
-	} else {
-	    print "/* Cannot open $filename */\n";
-	    print "#include \"$filename\"\n";
-	}
-    }
-
-    chdir     $Config{installarchlib}."/CORE";
-    doinclude "perl.h";
-
-It expands the "perl.h" header file, using only other Perl header files.
-
-Now you can configure & make Vim with the --enable-perlinterp option.
-Be warned though that this adds about 616 kilobytes to the size of Vim!
-Without Perl, Vim with default features and GUI is about 575K, with Perl
-it is about 1191K.
-
--Olaf Seibert
-
-[Note: these addresses no longer work:]
-<rhialto@polder.ubc.kun.nl>
-http://polder.ubc.kun.nl/~rhialto/be
-
- vim:tw=78:ts=8:ft=help:norl:
diff --git a/runtime/doc/os_mint.txt b/runtime/doc/os_mint.txt
deleted file mode 100644
index d44b1a4f40..0000000000
--- a/runtime/doc/os_mint.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-*os_mint.txt*   For Vim version 7.4.  Last change: 2005 Mar 29
-
-
-		  VIM REFERENCE MANUAL    by Jens M. Felderhoff
-
-
-							*MiNT* *Atari*
-This file contains the particularities for the Atari MiNT version of Vim.
-
-For compiling Vim on the Atari running MiNT see "INSTALL" and "Makefile"
-in the src directory.
-
-Vim for MiNT behaves almost exactly like the Unix version.
-The Unix behavior described in the documentation also refers to the
-MiNT version of Vim unless explicitly stated otherwise.
-
-For wildcard expansion of <~> (home directory) you need a shell that
-expands the tilde.  The vanilla Bourne shell doesn't recognize it.
-With csh and ksh it should work OK.
-
-The MiNT version of vim needs the termcap file /etc/termcap with the
-terminal capabilities of your terminal.  Builtin termcaps are
-supported for the vt52 terminal.  Termcap entries for the TOSWIN window
-manager and the virtual console terminals have been appended to the
-termcap file that comes with the Vim distribution.
-
-If you should encounter problems with swapped <BS> and <Del> keys, see
-|:fixdel|.
-
-Because terminal updating under MiNT is often slow (e.g. serial line
-terminal), the 'showcmd' and 'ruler' options are default off.
-If you have a fast terminal, try setting them on.  You might
-also want to set 'ttyfast'.
-
-Send bug reports to
-
-	Jens M. Felderhoff, e-mail: <jmf@infko.uni-koblenz.de>
-
- vim:tw=78:ts=8:ft=help:norl:
diff --git a/runtime/doc/os_os2.txt b/runtime/doc/os_os2.txt
deleted file mode 100644
index 231d7d1027..0000000000
--- a/runtime/doc/os_os2.txt
+++ /dev/null
@@ -1,221 +0,0 @@
-*os_os2.txt*    For Vim version 7.4.  Last change: 2007 Apr 22
-
-
-		  VIM REFERENCE MANUAL    by Paul Slootman
-
-
-							*os2* *OS2* *OS/2*
-This file contains the particularities for the OS/2 version of Vim.
-
-At present there is no native PM version of the GUI version of Vim: The OS/2
-version is a console application.  However, there is now a Win32s-compatible
-GUI version, which should be usable by owners of Warp 4 (which supports
-Win32s) in a Win-OS/2 session.  The notes in this file refer to the native
-console version.
-
-
-NOTE
-
-This OS/2 port works well for me and a couple of other OS/2 users; however,
-since I haven't had much feedback, that either means no (OS/2-specific) bugs
-exist (besides the ones mentioned below), or no one has yet created a
-situation in which any bugs are apparent.  File I/O in Dos and Unix mode,
-binary mode, and FAT handling all seem to work well, which would seem to be
-the most likely places for trouble.
-
-A known problem is that files opened by Vim are inherited by other programs
-that are started via a shell escape from within Vim.  This specifically means
-that Vim won't be able to remove the swap file(s) associated with buffers open
-at the time the other program was started, until the other program is stopped.
-At that time, the swap file may be removed, but if Vim could not do that the
-first time, it won't be removed at all.  You'll get warnings that some other
-Vim session may be editing the file when you start Vim up again on that file.
-This can be reproduced with ":!start epm".  Now quit Vim, and start Vim again
-with the file that was in the buffer at the time epm was started.  I'm working
-on this!
-
-A second problem is that Vim doesn't understand the situation when using it
-when accessing the OS/2 system via the network, e.g. using telnet from a Unix
-system, and then starting Vim.  The problem seems to be that OS/2 =sometimes=
-recognizes function / cursor keys, and tries to convert those to the
-corresponding OS/2 codes generated by the "normal" PC keyboard.  I've been
-testing a workaround (mapping the OS/2 codes to the correct functions), but so
-far I can't say anything conclusive (this is on Warp 3, by the way).  In the
-meantime any help will be appreciated.
-
-
-PREREQUISITES
-
-To run Vim, you need the emx runtime environment (at least rev. 0.9b).  This
-is generally available as (ask Archie about it):
-
-    emxrt.zip     emx runtime package
-
-I've included a copy of emx.dll, which should be copied to one of the
-directories listed in your LIBPATH.  Emx is GPL'ed, but the emx.dll library is
-not (read COPYING.EMX to find out what that means to you).
-
-This emx.dll is from the emxfix04.zip package, which unfortunately has a bug,
-eh, I mean a POSIX feature, in select().  Versions of Vim before 3.27 will
-appear to hang when starting (actually, while processing vimrc).  Hit <Enter> a
-couple of times until Vim starts working if this happens.  Next, get an up to
-date version of Vim!
-
-
-HELP AND VIMRC FILE
-
-If you unpack the archive that Vim came in and run Vim directly from where it
-was unpacked, Vim should be able to find the runtime files and your .vimrc
-without any settings.
-
-If you put the runtime files separately from the binary, the VIM environment
-variable is used to find the location of the help files and the system .vimrc.
-Place an entry such as this in CONFIG.SYS: >
-
-  SET VIM=c:/local/lib/vim
-
-Put your .vimrc and your other Vim files in this directory.  Copy the runtime
-directory to this directory.  Each version of Vim has its own runtime
-directory.  It will be called something like "c:/local/lib/vim/vim54".  Thus
-you get a tree of Vim files like this:
-	c:/local/lib/vim/.vimrc
-	c:/local/lib/vim/vim54/filetype.vim
-	c:/local/lib/vim/vim54/doc/help.txt
-	etc.
-
-Note: .vimrc may also be called _vimrc to accommodate those who have chosen to
-install OS/2 on a FAT file system.  Vim first tries to find .vimrc and if that
-fails, looks for _vimrc in the same place.  The existence of a .vimrc or
-_vimrc file influences the 'compatible' options, which can have unexpected side
-effects.  See |'compatible'|.
-
-If you're using network drives with OS/2, then you can install Vim on a
-network drive (including .vimrc; this is then called the "system" vimrc file),
-and then use a personal copy of .vimrc (the "user" vimrc file).  This should be
-located in a directory indicated by the HOME environment variable.
-
-
-ENVIRONMENT VARIABLES IN FILE NAMES
-
-This HOME environment variable is also used when using ~ in file names, so
-":e ~/textfile" will edit the file "textfile" in the directory referred to by
-HOME.  Additionally you can use other environment variables in file names, as
-in ":n $SRC/*.c".
-
-The HOME environment variable is also used to locate the .viminfo file
-(see |viminfo-file|).  There is no support yet for .viminfo on FAT file
-systems yet, sorry.  You could try the -i startup flag (as in "vim -i
-$HOME/_viminfo") however.
-
-If the HOME environment variable is not set, the value "C:/" is used as a
-default.
-
-
-BACKSLASHES
-
-Using slashes ('/') and backslashes ('\') can be a bit of a problem (see
-|dos-backslash| for more explanation), but in almost all cases Vim does "The
-Right Thing".  Vim itself uses backslashes in file names, but will happily
-accept forward slashes if they are entered (in fact, sometimes that works
-better!).
-
-
-TEMP FILES
-
-Temporary files (for filtering) are put in the first directory in the next
-list that exists and where a file can be created:
-	$TMP
-	$TEMP
-	C:\TMP
-	C:\TEMP
-	current directory
-
-
-TERMINAL SETTING
-
-							*os2ansi*
-Use "os2ansi" as the TERM environment variable (or don't set it at all, as the
-default is the correct value).  You can set term to os2ansi in the .vimrc, in
-case you need TERM to be a different value for other applications.  The
-problem is that OS/2 ANSI emulation is quite limited (it doesn't have insert /
-delete line, for example).
-
-If you want to use a different value for TERM (because of other programs, for
-example), make sure that the termcap entry for that TERM value has the
-appropriate key mappings.  The termcap.dat distributed with emx does not always
-have them.  Here are some suitable values to add to the termcap entry of your
-choice; these allow the cursor keys and the named function keys (such as
-pagedown) to work.
-
-	:ku=\316H:kd=\316P:kl=\316K:kr=\316M:%i=\316t:#4=\316s:\
-	:kD=\316S:kI=\316R:kN=\316Q:kP=\316I:kh=\316G:@7=\316O:\
-	:k1=\316;:k2=\316<:k3=\316=:k4=\316>:k5=\316?:k6=\316@:\
-	:k7=\316A:k8=\316B:k9=\316C:k;=\316D:
-
-
-Paul Slootman
-
-
-43 LINE WINDOW
-
-A suggestion from Steven Tryon, on how to run Vim in a bigger window:
-
-When I call Vim from an OS/2 WPS application such as PMMail it comes up
-in the default 25-line mode.  To get a more useful window size I make
-my external editor "vimbig.cmd" which in turn calls "vimbig2.cmd".
-Brute force and awkwardness, perhaps, but it works.
-
-vimbig.cmd: >
-   @echo off
-   start "Vi Improved" /f vimbig2.cmd %1 %2 %3 %4
-
-vimbig2.cmd: >
-   @echo off
-   mode 80,43
-   vim.exe %1 %2 %3 %4
-   exit
-<
-
-CLIPBOARD ACCESS (provided by Alexander Wagner)
-
-Vim for OS/2 has no direct access to the system clipboard.  To enable access
-anyway you need an additional tool which gives you access to the clipboard
-from within a vio application.  The freeware package clipbrd.zip by Stefan
-Gruendel can be used for this purpose.  You might download the package
-including precompiled binaries and all sources from:
-	http://www.os2site.com/sw/util/clipboard/index.html
-	http://download.uni-hd.de/ftp/pub/os2/pmtools/
-
-Installation of this package is straight forward: just put the two executables
-that come with this package into a directory within your PATH for Vim should
-be able to call them from whatever directory you are working.
-
-To copy text from the clipboard to your Vim session you can use the :r
-command.  Simply call clipbrd.exe from within Vim in the following way: >
-
-	:r !clipbrd -r
-
-To copy text from Vim to the system clipboard just mark the text in the usual
-vim-manner and call: >
-
-	:!clipbrd -w
-
-which will write your selection right into OS/2's clipboard.
-
-For ease of use you might want to add some maps for these commands.  E.g. to
-use F11 to paste the clipboard into Vim and F12 to copy selected text to the
-clipboard you would use: >
-
-	if has("os2"