doc: remove generated manpages

4 files changed, 0 insertions, 786 deletions

diff --git a/runtime/doc/vim.man b/runtime/doc/vim.man
deleted file mode 100644
index 5b9b83cb6c..0000000000
--- a/runtime/doc/vim.man
+++ /dev/null
@@ -1,428 +0,0 @@
-VIM(1)                                                                  VIM(1)
-
-
-
-NAME
-       vim - Vi IMproved, a programmers text editor
-
-SYNOPSIS
-       vim [options] [file ..]
-       vim [options] -
-       vim [options] -t tag
-       vim [options] -q [errorfile]
-
-       ex
-       view
-       gvim gview evim eview
-       rvim rview rgvim rgview
-
-DESCRIPTION
-       Vim  is a text editor that is upwards compatible to Vi.  It can be used
-       to edit all kinds of plain text.  It is especially useful  for  editing
-       programs.
-
-       There  are a lot of enhancements above Vi: multi level undo, multi win-
-       dows and buffers, syntax highlighting, command line  editing,  filename
-       completion,   on-line   help,   visual  selection,  etc..   See  ":help
-       vi_diff.txt" for a summary of the differences between Vim and Vi.
-
-       While running Vim a lot of help can be obtained from the  on-line  help
-       system,  with the ":help" command.  See the ON-LINE HELP section below.
-
-       Most often Vim is started to edit a single file with the command
-
-            vim file
-
-       More generally Vim is started with:
-
-            vim [options] [filelist]
-
-       If the filelist is missing, the editor will start with an empty buffer.
-       Otherwise  exactly  one out of the following four may be used to choose
-       one or more files to be edited.
-
-       file ..     A list of filenames.  The first one  will  be  the  current
-                   file  and  read  into the buffer.  The cursor will be posi-
-                   tioned on the first line of the buffer.  You can get to the
-                   other  files with the ":next" command.  To edit a file that
-                   starts with a dash, precede the filelist with "--".
-
-       -           The file to edit is read from  stdin.   Commands  are  read
-                   from stderr, which should be a tty.
-
-       -t {tag}    The file to edit and the initial cursor position depends on
-                   a "tag", a sort of goto label.  {tag} is looked up  in  the
-                   tags file, the associated file becomes the current file and
-                   the associated command is executed.  Mostly  this  is  used
-                   for  C  programs,  in  which case {tag} could be a function
-                   name.  The effect is that the file containing that function
-                   becomes  the  current  file and the cursor is positioned on
-                   the start of the function.  See ":help tag-commands".
-
-       -q [errorfile]
-                   Start in quickFix mode.  The file [errorfile] is  read  and
-                   the  first  error is displayed.  If [errorfile] is omitted,
-                   the  filename  is  obtained  from  the  'errorfile'  option
-                   (defaults  to  "AztecC.Err"  for the Amiga, "errors.err" on
-                   other systems).  Further errors can be jumped to  with  the
-                   ":cn" command.  See ":help quickfix".
-
-       Vim behaves differently, depending on the name of the command (the exe-
-       cutable may still be the same file).
-
-       vim       The "normal" way, everything is default.
-
-       ex        Start in Ex mode.  Go to Normal mode with the ":vi"  command.
-                 Can also be done with the "-e" argument.
-
-       view      Start  in read-only mode.  You will be protected from writing
-                 the files.  Can also be done with the "-R" argument.
-
-       gvim gview
-                 The GUI version.  Starts a new window.  Can also be done with
-                 the "-g" argument.
-
-       evim eview
-                 The GUI version in easy mode.  Starts a new window.  Can also
-                 be done with the "-y" argument.
-
-       rvim rview rgvim rgview
-                 Like the above, but with restrictions.  It will not be possi-
-                 ble  to  start  shell  commands, or suspend Vim.  Can also be
-                 done with the "-Z" argument.
-
-OPTIONS
-       The options may be given in  any  order,  before  or  after  filenames.
-       Options without an argument can be combined after a single dash.
-
-       +[num]      For  the  first  file the cursor will be positioned on line
-                   "num".  If "num" is missing, the cursor will be  positioned
-                   on the last line.
-
-       +/{pat}     For  the  first  file  the cursor will be positioned on the
-                   first occurrence of {pat}.  See ":help search-pattern"  for
-                   the available search patterns.
-
-       +{command}
-
-       -c {command}
-                   {command}  will  be  executed after the first file has been
-                   read.  {command} is interpreted as an Ex command.   If  the
-                   {command}  contains  spaces  it  must be enclosed in double
-                   quotes (this depends on the shell that is used).   Example:
-                   Vim "+set si" main.c
-                   Note: You can use up to 10 "+" or "-c" commands.
-
-       -S {file}   {file}  will be sourced after the first file has been read.
-                   This is equivalent to -c "source  {file}".   {file}  cannot
-                   start with '-'.  If {file} is omitted "Session.vim" is used
-                   (only works when -S is the last argument).
-
-       --cmd {command}
-                   Like using "-c", but the command is  executed  just  before
-                   processing  any  vimrc file.  You can use up to 10 of these
-                   commands, independently from "-c" commands.
-
-       -A          If Vim has been compiled with ARABIC  support  for  editing
-                   right-to-left  oriented  files and Arabic keyboard mapping,
-                   this option starts Vim in Arabic  mode,  i.e.  'arabic'  is
-                   set.  Otherwise an error message is given and Vim aborts.
-
-       -b          Binary  mode.  A few options will be set that makes it pos-
-                   sible to edit a binary or executable file.
-
-       -C          Compatible.  Set the 'compatible' option.  This  will  make
-                   Vim  behave  mostly  like  Vi,  even  though  a .vimrc file
-                   exists.
-
-       -d          Start in diff mode.  There should be  two,  three  or  four
-                   file  name arguments.  Vim will open all the files and show
-                   differences between them.  Works like vimdiff(1).
-
-       -d {device} Open {device} for use as a terminal.  Only  on  the  Amiga.
-                   Example: "-d con:20/30/600/150".
-
-       -D          Debugging.   Go  to debugging mode when executing the first
-                   command from a script.
-
-       -e          Start Vim in Ex mode, just like the executable  was  called
-                   "ex".
-
-       -E          Start Vim in improved Ex mode, just like the executable was
-                   called "exim".
-
-       -f          Foreground.  For the GUI version, Vim  will  not  fork  and
-                   detach from the shell it was started in.  On the Amiga, Vim
-                   is not restarted to open a new window.  This option  should
-                   be  used  when  Vim is executed by a program that will wait
-                   for the edit session to finish (e.g. mail).  On  the  Amiga
-                   the ":sh" and ":!" commands will not work.
-
-       --nofork    Foreground.   For  the  GUI  version, Vim will not fork and
-                   detach from the shell it was started in.
-
-       -F          If Vim has been compiled with  FKMAP  support  for  editing
-                   right-to-left  oriented  files  and Farsi keyboard mapping,
-                   this option starts Vim in  Farsi  mode,  i.e.  'fkmap'  and
-                   'rightleft'  are  set.  Otherwise an error message is given
-                   and Vim aborts.
-
-       -g          If Vim has been compiled  with  GUI  support,  this  option
-                   enables  the  GUI.   If  no GUI support was compiled in, an
-                   error message is given and Vim aborts.
-
-       -h          Give a bit of help about the  command  line  arguments  and
-                   options.  After this Vim exits.
-
-       -H          If Vim has been compiled with RIGHTLEFT support for editing
-                   right-to-left oriented files and Hebrew  keyboard  mapping,
-                   this  option  starts  Vim  in Hebrew mode, i.e. 'hkmap' and
-                   'rightleft' are set.  Otherwise an error message  is  given
-                   and Vim aborts.
-
-       -i {viminfo}
-                   When  using  the  viminfo file is enabled, this option sets
-                   the filename to use, instead of the  default  "~/.viminfo".
-                   This can also be used to skip the use of the .viminfo file,
-                   by giving the name "NONE".
-
-       -L          Same as -r.
-
-       -l          Lisp mode.  Sets the 'lisp' and 'showmatch' options on.
-
-       -m          Modifying files is disabled.  Resets  the  'write'  option.
-                   You  can still modify the buffer, but writing a file is not
-                   possible.
-
-       -M          Modifications not allowed.  The  'modifiable'  and  'write'
-                   options  will be unset, so that changes are not allowed and
-                   files can not be written.  Note that these options  can  be
-                   set to enable making modifications.
-
-       -N          No-compatible  mode.   Reset the 'compatible' option.  This
-                   will make Vim behave a bit better, but less Vi  compatible,
-                   even though a .vimrc file does not exist.
-
-       -n          No  swap file will be used.  Recovery after a crash will be
-                   impossible.  Handy if you want to edit a  file  on  a  very
-                   slow  medium  (e.g.  floppy).   Can also be done with ":set
-                   uc=0".  Can be undone with ":set uc=200".
-
-       -nb         Become an editor server for NetBeans.   See  the  docs  for
-                   details.
-
-       -o[N]       Open N windows stacked.  When N is omitted, open one window
-                   for each file.
-
-       -O[N]       Open N windows side by side.  When N is omitted,  open  one
-                   window for each file.
-
-       -p[N]       Open N tab pages.  When N is omitted, open one tab page for
-                   each file.
-
-       -R          Read-only mode.  The 'readonly' option will  be  set.   You
-                   can still edit the buffer, but will be prevented from acci-
-                   dently overwriting a file.  If you do want to  overwrite  a
-                   file,  add  an  exclamation  mark  to the Ex command, as in
-                   ":w!".  The -R option  also  implies  the  -n  option  (see
-                   below).   The  'readonly'  option  can  be reset with ":set
-                   noro".  See ":help 'readonly'".
-
-       -r          List swap files, with  information  about  using  them  for
-                   recovery.
-
-       -r {file}   Recovery  mode.  The swap file is used to recover a crashed
-                   editing session.  The swap file is a  file  with  the  same
-                   filename as the text file with ".swp" appended.  See ":help
-                   recovery".
-
-       -s          Silent mode.  Only when started as "Ex" or  when  the  "-e"
-                   option was given before the "-s" option.
-
-       -s {scriptin}
-                   The  script file {scriptin} is read.  The characters in the
-                   file are interpreted as if you had typed  them.   The  same
-                   can be done with the command ":source! {scriptin}".  If the
-                   end of the file is reached before the editor exits, further
-                   characters are read from the keyboard.
-
-       -T {terminal}
-                   Tells  Vim  the  name  of the terminal you are using.  Only
-                   required when the automatic way doesn't work.  Should be  a
-                   terminal  known  to Vim (builtin) or defined in the termcap
-                   or terminfo file.
-
-       -u {vimrc}  Use the commands in the file {vimrc}  for  initializations.
-                   All  the  other  initializations  are skipped.  Use this to
-                   edit a special kind of files.  It can also be used to  skip
-                   all  initializations by giving the name "NONE".  See ":help
-                   initialization" within vim for more details.
-
-       -U {gvimrc} Use the commands in the file {gvimrc} for  GUI  initializa-
-                   tions.   All the other GUI initializations are skipped.  It
-                   can also be used to skip all GUI initializations by  giving
-                   the  name "NONE".  See ":help gui-init" within vim for more
-                   details.
-
-       -V[N]       Verbose.  Give messages about which files are  sourced  and
-                   for  reading and writing a viminfo file.  The optional num-
-                   ber N is the value for 'verbose'.  Default is 10.
-
-       -v          Start Vim in Vi mode, just like the executable  was  called
-                   "vi".   This  only has effect when the executable is called
-                   "ex".
-
-       -w {scriptout}
-                   All the characters that you type are recorded in  the  file
-                   {scriptout},  until  you  exit  Vim.  This is useful if you
-                   want to create a script file to be used with  "vim  -s"  or
-                   ":source!".  If the {scriptout} file exists, characters are
-                   appended.
-
-       -W {scriptout}
-                   Like -w, but an existing file is overwritten.
-
-       -x          Use encryption when writing files.  Will prompt for a crypt
-                   key.
-
-       -X          Don't  connect to the X server.  Shortens startup time in a
-                   terminal, but the window title and clipboard  will  not  be
-                   used.
-
-       -y          Start Vim in easy mode, just like the executable was called
-                   "evim" or "eview".  Makes Vim behave like a  click-and-type
-                   editor.
-
-       -Z          Restricted  mode.   Works  like  the executable starts with
-                   "r".
-
-       --          Denotes the end of the options.  Arguments after this  will
-                   be  handled  as  a  file  name.  This can be used to edit a
-                   filename that starts with a '-'.
-
-       --echo-wid  GTK GUI only: Echo the Window ID on stdout.
-
-       --help      Give a help message and exit, just like "-h".
-
-       --literal   Take file name arguments literally,  do  not  expand  wild-
-                   cards.   This has no effect on Unix where the shell expands
-                   wildcards.
-
-       --noplugin  Skip loading plugins.  Implied by -u NONE.
-
-       --remote    Connect to a Vim server and make it edit the files given in
-                   the rest of the arguments.  If no server is found a warning
-                   is given and the files are edited in the current Vim.
-
-       --remote-expr {expr}
-                   Connect to a Vim server, evaluate {expr} in  it  and  print
-                   the result on stdout.
-
-       --remote-send {keys}
-                   Connect to a Vim server and send {keys} to it.
-
-       --remote-silent
-                   As  --remote,  but  without  the  warning when no server is
-                   found.
-
-       --remote-wait
-                   As --remote, but Vim does not exit  until  the  files  have
-                   been edited.
-
-       --remote-wait-silent
-                   As --remote-wait, but without the warning when no server is
-                   found.
-
-       --serverlist
-                   List the names of all Vim servers that can be found.
-
-       --servername {name}
-                   Use {name} as the server name.  Used for the  current  Vim,
-                   unless used with a --remote argument, then it's the name of
-                   the server to connect to.
-
-       --socketid {id}
-                   GTK GUI only: Use the GtkPlug  mechanism  to  run  gvim  in
-                   another window.
-
-       --version   Print version information and exit.
-
-ON-LINE HELP
-       Type  ":help"  in Vim to get started.  Type ":help subject" to get help
-       on a specific subject.  For example: ":help ZZ" to  get  help  for  the
-       "ZZ"  command.   Use <Tab> and CTRL-D to complete subjects (":help cmd-
-       line-completion").  Tags are present to jump from one place to  another
-       (sort of hypertext links, see ":help").  All documentation files can be
-       viewed in this way, for example ":help syntax.txt".
-
-FILES
-       /usr/local/lib/vim/doc/*.txt
-                      The Vim documentation files.  Use ":help  doc-file-list"
-                      to get the complete list.
-
-       /usr/local/lib/vim/doc/tags
-                      The  tags file used for finding information in the docu-
-                      mentation files.
-
-       /usr/local/lib/vim/syntax/syntax.vim
-                      System wide syntax initializations.
-
-       /usr/local/lib/vim/syntax/*.vim
-                      Syntax files for various languages.
-
-       /usr/local/lib/vim/vimrc
-                      System wide Vim initializations.
-
-       ~/.vimrc       Your personal Vim initializations.
-
-       /usr/local/lib/vim/gvimrc
-                      System wide gvim initializations.
-
-       ~/.gvimrc      Your personal gvim initializations.
-
-       /usr/local/lib/vim/optwin.vim
-                      Script used for the ":options" command, a  nice  way  to
-                      view and set options.
-
-       /usr/local/lib/vim/menu.vim
-                      System wide menu initializations for gvim.
-
-       /usr/local/lib/vim/bugreport.vim
-                      Script to generate a bug report.  See ":help bugs".
-
-       /usr/local/lib/vim/filetype.vim
-                      Script  to  detect  the type of a file by its name.  See
-                      ":help 'filetype'".
-
-       /usr/local/lib/vim/scripts.vim
-                      Script to detect the type of a  file  by  its  contents.
-                      See ":help 'filetype'".
-
-       /usr/local/lib/vim/print/*.ps
-                      Files used for PostScript printing.
-
-       For recent info read the VIM home page:
-       <URL:http://www.vim.org/>
-
-SEE ALSO
-       vimtutor(1)
-
-AUTHOR
-       Most of Vim was made by Bram Moolenaar, with a lot of help from others.
-       See ":help credits" in Vim.
-       Vim is based on Stevie, worked on by: Tim Thompson,  Tony  Andrews  and
-       G.R.  (Fred) Walter.  Although hardly any of the original code remains.
-
-BUGS
-       Probably.  See ":help todo" for a list of known problems.
-
-       Note that a number of things that may be regarded as bugs by some,  are
-       in  fact  caused by a too-faithful reproduction of Vi's behaviour.  And
-       if you think other things are bugs "because Vi  does  it  differently",
-       you  should  take  a closer look at the vi_diff.txt file (or type :help
-       vi_diff.txt when in Vim).  Also have a look  at  the  'compatible'  and
-       'cpoptions' options.
-
-
-
-                                  2006 Apr 11                           VIM(1)
diff --git a/runtime/doc/vimdiff.man b/runtime/doc/vimdiff.man
deleted file mode 100644
index 913ac13847..0000000000
--- a/runtime/doc/vimdiff.man
+++ /dev/null
@@ -1,46 +0,0 @@
-VIMDIFF(1)                                                          VIMDIFF(1)
-
-
-
-NAME
-       vimdiff  - edit two, three or four versions of a file with Vim and show
-       differences
-
-SYNOPSIS
-       vimdiff [options] file1 file2 [file3 [file4]]
-
-       gvimdiff
-
-DESCRIPTION
-       Vimdiff starts Vim on two (or three or four) files.  Each file gets its
-       own  window.   The differences between the files are highlighted.  This
-       is a nice way to inspect changes and to move changes from  one  version
-       to another version of the same file.
-
-       See vim(1) for details about Vim itself.
-
-       When started as gvimdiff the GUI will be started, if available.
-
-       In  each window the 'diff' option will be set, which causes the differ-
-       ences to be highlighted.
-       The 'wrap' and 'scrollbind' options are set to make the text look good.
-       The  'foldmethod'  option  is set to "diff", which puts ranges of lines
-       without changes in a fold.  'foldcolumn' is set to two to make it  easy
-       to spot the folds and open or close them.
-
-OPTIONS
-       Vertical  splits  are  used to align the lines, as if the "-O" argument
-       was used.  To use horizontal splits instead, use the "-o" argument.
-
-       For all other arguments see vim(1).
-
-SEE ALSO
-       vim(1)
-
-AUTHOR
-       Most of Vim was made by Bram Moolenaar, with a lot of help from others.
-       See ":help credits" in Vim.
-
-
-
-                                 2001 March 30                      VIMDIFF(1)
diff --git a/runtime/doc/vimtutor.man b/runtime/doc/vimtutor.man
deleted file mode 100644
index 9f2350a0ae..0000000000
--- a/runtime/doc/vimtutor.man
+++ /dev/null
@@ -1,50 +0,0 @@
-VIMTUTOR(1)                                                        VIMTUTOR(1)
-
-
-
-NAME
-       vimtutor - the Vim tutor
-
-SYNOPSIS
-       vimtutor [-g] [language]
-
-DESCRIPTION
-       Vimtutor starts the Vim tutor.  It copies the tutor file first, so that
-       it can be modified without changing the original file.
-
-       The Vimtutor is useful for people that want to learn  their  first  Vim
-       commands.
-
-       The  optional argument -g starts vimtutor with gvim rather than vim, if
-       the GUI version of vim is available, or falls back to Vim  if  gvim  is
-       not found.
-
-       The  optional [language] argument is the two-letter name of a language,
-       like "it" or "es".  If the [language] argument is missing, the language
-       of  the  current  locale  will be used.  If a tutor in this language is
-       available, it will be used.  Otherwise  the  English  version  will  be
-       used.
-
-       Vim is always started in Vi compatible mode.
-
-FILES
-       /usr/local/lib/vim/tutor/tutor[.language]
-                      The Vimtutor text file(s).
-
-       /usr/local/lib/vim/tutor/tutor.vim
-                      The Vim script used to copy the Vimtutor text file.
-
-AUTHOR
-       The  Vimtutor  was  originally  written for Vi by Michael C. Pierce and
-       Robert K. Ware, Colorado  School  of  Mines  using  ideas  supplied  by
-       Charles  Smith,  Colorado  State  University.  E-mail: bware@mines.col‐
-       orado.edu.
-       It was modified for Vim by Bram Moolenaar.  For the names of the trans‐
-       lators see the tutor files.
-
-SEE ALSO
-       vim(1)
-
-
-
-                                 2001 April 2                      VIMTUTOR(1)
diff --git a/runtime/doc/xxd.man b/runtime/doc/xxd.man
deleted file mode 100644
index 057c8e911b..0000000000
--- a/runtime/doc/xxd.man
+++ /dev/null
@@ -1,262 +0,0 @@
-XXD(1)                                                                  XXD(1)
-
-
-
-NAME
-       xxd - make a hexdump or do the reverse.
-
-SYNOPSIS
-       xxd -h[elp]
-       xxd [options] [infile [outfile]]
-       xxd -r[evert] [options] [infile [outfile]]
-
-DESCRIPTION
-       xxd  creates a hex dump of a given file or standard input.  It can also
-       convert a hex dump back to its original binary form.  Like  uuencode(1)
-       and  uudecode(1)  it allows the transmission of binary data in a `mail-
-       safe' ASCII representation, but has the advantage of decoding to  stan-
-       dard output.  Moreover, it can be used to perform binary file patching.
-
-OPTIONS
-       If no infile is given, standard input is read.  If infile is  specified
-       as  a  `-'  character,  then input is taken from standard input.  If no
-       outfile is given (or a `-' character is in its place), results are sent
-       to standard output.
-
-       Note  that  a  "lazy" parser is used which does not check for more than
-       the first option letter, unless the option is followed by a  parameter.
-       Spaces  between  a single option letter and its parameter are optional.
-       Parameters to options can be specified in decimal, hexadecimal or octal
-       notation.  Thus -c8, -c 8, -c 010 and -cols 8 are all equivalent.
-
-
-       -a | -autoskip
-              toggle  autoskip: A single '*' replaces nul-lines.  Default off.
-
-       -b | -bits
-              Switch to bits (binary digits) dump, rather than hexdump.   This
-              option  writes octets as eight digits "1"s and "0"s instead of a
-              normal hexadecimal dump. Each line is preceded by a line  number
-              in  hexadecimal and followed by an ascii (or ebcdic) representa-
-              tion. The command line switches -r, -p, -i do not work with this
-              mode.
-
-       -c cols | -cols cols
-              format  <cols> octets per line. Default 16 (-i: 12, -ps: 30, -b:
-              6). Max 256.
-
-       -E | -EBCDIC
-              Change the character encoding in the righthand column from ASCII
-              to EBCDIC.  This does not change the hexadecimal representation.
-              The option is meaningless in combinations with -r, -p or -i.
-
-       -g bytes | -groupsize bytes
-              separate the output of every <bytes> bytes (two  hex  characters
-              or eight bit-digits each) by a whitespace.  Specify -g 0 to sup-
-              press grouping.  <Bytes> defaults to 2 in normal mode and  1  in
-              bits  mode.   Grouping  does  not apply to postscript or include
-              style.
-
-       -h | -help
-              print a summary of available commands and exit.  No hex  dumping
-              is performed.
-
-       -i | -include
-              output  in C include file style. A complete static array defini-
-              tion is written (named after the input file), unless  xxd  reads
-              from stdin.
-
-       -l len | -len len
-              stop after writing <len> octets.
-
-       -p | -ps | -postscript | -plain
-              output  in  postscript  continuous  hexdump style. Also known as
-              plain hexdump style.
-
-       -r | -revert
-              reverse operation: convert (or patch) hexdump into  binary.   If
-              not  writing  to stdout, xxd writes into its output file without
-              truncating it. Use the combination -r -p to read plain hexadeci-
-              mal dumps without line number information and without a particu-
-              lar column layout. Additional  Whitespace  and  line-breaks  are
-              allowed anywhere.
-
-       -seek offset
-              When used after -r: revert with <offset> added to file positions
-              found in hexdump.
-
-       -s [+][-]seek
-              start at <seek> bytes abs. (or rel.) infile offset.  + indicates
-              that  the  seek  is  relative to the current stdin file position
-              (meaningless when not reading from stdin).  - indicates that the
-              seek  should  be  that many characters from the end of the input
-              (or if combined with +: before the current stdin file position).
-              Without -s option, xxd starts at the current file position.
-
-       -u     use upper case hex letters. Default is lower case.
-
-       -v | -version
-              show version string.
-
-CAVEATS
-       xxd -r has some builtin magic while evaluating line number information.
-       If the output file is seekable, then the linenumbers at  the  start  of
-       each  hexdump  line may be out of order, lines may be missing, or over-
-       lapping. In these cases xxd will lseek(2) to the next position. If  the
-       output  file  is  not  seekable,  only  gaps are allowed, which will be
-       filled by null-bytes.
-
-       xxd -r never generates parse errors. Garbage is silently skipped.
-
-       When editing hexdumps, please note that xxd -r skips everything on  the
-       input line after reading enough columns of hexadecimal data (see option
-       -c). This also means, that changes to the printable ascii  (or  ebcdic)
-       columns  are  always  ignored.  Reverting a plain (or postscript) style
-       hexdump with xxd -r -p does not depend on the correct  number  of  col-
-       umns.  Here  anything  that  looks  like a pair of hex-digits is inter-
-       preted.
-
-       Note the difference between
-       % xxd -i file
-       and
-       % xxd -i < file
-
-       xxd -s +seek may be different from xxd -s seek, as lseek(2) is used  to
-       "rewind" input.  A '+' makes a difference if the input source is stdin,
-       and if stdin's file position is not at the start of  the  file  by  the
-       time  xxd  is  started and given its input.  The following examples may
-       help to clarify (or further confuse!)...
-
-       Rewind stdin before reading; needed because the `cat' has already  read
-       to the end of stdin.
-       % sh -c "cat > plain_copy; xxd -s 0 > hex_copy" < file
-
-       Hexdump  from  file  position  0x480 (=1024+128) onwards.  The `+' sign
-       means "relative to the current position", thus the `128' adds to the 1k
-       where dd left off.
-       %  sh -c "dd of=plain_snippet bs=1k count=1; xxd -s +128 > hex_snippet"
-       < file
-
-       Hexdump from file position 0x100 ( = 1024-768) on.
-       % sh -c "dd of=plain_snippet bs=1k count=1; xxd -s +-768 > hex_snippet"
-       < file
-
-       However,  this is a rare situation and the use of `+' is rarely needed.
-       The author prefers to monitor the  effect  of  xxd  with  strace(1)  or
-       truss(1), whenever -s is used.
-
-EXAMPLES
-       Print everything but the first three lines (hex 0x30 bytes) of file.
-       % xxd -s 0x30 file
-
-       Print 3 lines (hex 0x30 bytes) from the end of file.
-       % xxd -s -0x30 file
-
-       Print 120 bytes as continuous hexdump with 20 octets per line.
-       % xxd -l 120 -ps -c 20 xxd.1
-       2e54482058584420312022417567757374203139
-       39362220224d616e75616c207061676520666f72
-       20787864220a2e5c220a2e5c222032317374204d
-       617920313939360a2e5c22204d616e2070616765
-       20617574686f723a0a2e5c2220202020546f6e79
-       204e7567656e74203c746f6e79407363746e7567
-
-       Hexdump the first 120 bytes of this man page with 12 octets per line.
-       % xxd -l 120 -c 12 xxd.1
-       0000000: 2e54 4820 5858 4420 3120 2241  .TH XXD 1 "A
-       000000c: 7567 7573 7420 3139 3936 2220  ugust 1996"
-       0000018: 224d 616e 7561 6c20 7061 6765  "Manual page
-       0000024: 2066 6f72 2078 7864 220a 2e5c   for xxd"..\
-       0000030: 220a 2e5c 2220 3231 7374 204d  "..\" 21st M
-       000003c: 6179 2031 3939 360a 2e5c 2220  ay 1996..\"
-       0000048: 4d61 6e20 7061 6765 2061 7574  Man page aut
-       0000054: 686f 723a 0a2e 5c22 2020 2020  hor:..\"
-       0000060: 546f 6e79 204e 7567 656e 7420  Tony Nugent
-       000006c: 3c74 6f6e 7940 7363 746e 7567  <tony@sctnug
-
-       Display just the date from the file xxd.1
-       % xxd -s 0x36 -l 13 -c 13 xxd.1
-       0000036: 3231 7374 204d 6179 2031 3939 36  21st May 1996
-
-       Copy input_file to output_file and prepend 100 bytes of value 0x00.
-       % xxd input_file | xxd -r -s 100 > output_file
-
-       Patch the date in the file xxd.1
-       % echo "0000037: 3574 68" | xxd -r - xxd.1
-       % xxd -s 0x36 -l 13 -c 13 xxd.1
-       0000036: 3235 7468 204d 6179 2031 3939 36  25th May 1996
-
-       Create  a  65537 byte file with all bytes 0x00, except for the last one
-       which is 'A' (hex 0x41).
-       % echo "010000: 41" | xxd -r > file
-
-       Hexdump this file with autoskip.
-       % xxd -a -c 12 file
-       0000000: 0000 0000 0000 0000 0000 0000  ............
-       *
-       000fffc: 0000 0000 40                   ....A
-
-       Create a 1 byte file containing a single  'A'  character.   The  number
-       after '-r -s' adds to the linenumbers found in the file; in effect, the
-       leading bytes are suppressed.
-       % echo "010000: 41" | xxd -r -s -0x10000 > file
-
-       Use xxd as a filter within an editor such as vim(1) to hexdump a region
-       marked between `a' and `z'.
-       :'a,'z!xxd
-
-       Use xxd as a filter within an editor such as vim(1) to recover a binary
-       hexdump marked between `a' and `z'.
-       :'a,'z!xxd -r
-
-       Use xxd as a filter within an editor such as vim(1) to recover one line
-       of a hexdump.  Move the cursor over the line and type:
-       !!xxd -r
-
-       Read single characters from a serial line
-       % xxd -c1 < /dev/term/b &
-       % stty < /dev/term/b -echo -opost -isig -icanon min 1
-       % echo -n foo > /dev/term/b
-
-
-RETURN VALUES
-       The following error values are returned:
-
-       0      no errors encountered.
-
-       -1     operation not supported ( xxd -r -i still impossible).
-
-       1      error while parsing options.
-
-       2      problems with input file.
-
-       3      problems with output file.
-
-       4,5    desired seek position is unreachable.
-
-SEE ALSO
-       uuencode(1), uudecode(1), patch(1)
-
-WARNINGS
-       The  tools  weirdness matches its creators brain.  Use entirely at your
-       own risk. Copy files. Trace it. Become a wizard.
-
-VERSION
-       This manual page documents xxd version 1.7
-
-AUTHOR
-       (c) 1990-1997 by Juergen Weigert
-       <jnweiger@informatik.uni-erlangen.de>
-
-       Distribute freely and credit me,
-       make money and share with me,
-       lose money and don't ask me.
-
-       Manual page started by Tony Nugent
-       <tony@sctnugen.ppp.gu.edu.au> <T.Nugent@sct.gu.edu.au>
-       Small changes by Bram Moolenaar.  Edited by Juergen Weigert.
-
-
-
-
-Manual page for xxd               August 1996                           XXD(1)