--- ctags-5.8/ctags.1	2009-07-10 00:03:54.000000000 +0200
+++ ctags-5.8-patch/ctags.1	2010-11-12 15:48:15.993163977 +0100
@@ -1,4 +1,4 @@
-.TH CTAGS 1 "Version 5.8" "Darren Hiebert" "Exuberant Ctags"
+.TH exctags 1 "Version 5.8" "Darren Hiebert" "Exuberant Ctags"
 
 
 .SH "NAME"
@@ -7,13 +7,13 @@
 
 .SH SYNOPSIS
 .TP 6
-\fBctags\fP [\fBoptions\fP] [\fIfile(s)\fP]
+\fBexctags\fP [\fBoptions\fP] [\fIfile(s)\fP]
 .TP 6
 \fBetags\fP [\fBoptions\fP] [\fIfile(s)\fP]
 
 
 .SH "DESCRIPTION"
-The \fBctags\fP and \fBetags\fP programs (hereinafter collectively referred to
+The \fBexctags\fP and \fBetags\fP programs (hereinafter collectively referred to
 as \fBctags\fP, except where distinguished) generate an index (or "tag") file
 for a variety of language objects found in \fIfile(s)\fP.
 This tag file allows these items to be quickly and easily located by a text
@@ -63,8 +63,8 @@
 checked to see if the file is a "#!" script for a recognized language.
 
 By default, all other files names are ignored. This permits running
-\fBctags\fP on all files in either a single directory (e.g. "ctags *"), or on
-all files in an entire source directory tree (e.g. "ctags \-R"), since only
+\fBctags\fP on all files in either a single directory (e.g. "exctags *"), or on
+all files in an entire source directory tree (e.g. "exctags \-R"), since only
 those files whose names are mapped to languages will be scanned.
 
 [The reason that .h extensions are mapped to C++ files rather than C files
@@ -75,7 +75,7 @@
 .SH "OPTIONS"
 
 Despite the wealth of available options, defaults are set so that \fBctags\fP
-is most commonly executed without any options (e.g. "ctags *", or "ctags \-R"),
+is most commonly executed without any options (e.g. "exctags *", or "exctags \-R"),
 which will create a tag file in the current directory for all recognized
 source files. The options described below are provided merely to allow custom
 tailoring to meet special needs.
@@ -123,7 +123,7 @@
 "\-", then the tag file is written to standard output instead. \fBCtags\fP
 will stubbornly refuse to take orders if \fItagfile\fP exists and its first
 line contains something other than a valid tags line. This will save your neck
-if you mistakenly type "ctags \-f *.c", which would otherwise overwrite your
+if you mistakenly type "exctags \-f *.c", which would otherwise overwrite your
 first C file with the tags generated by the rest! It will also refuse to
 accept a multi-character file name which begins with a '\-' (dash) character,
 since this most likely means that you left out the tag file name and this
@@ -277,9 +277,9 @@
 source line (with extra white space condensed) of the file which defines the
 tag. No tag file is written and all options affecting tag file output will be
 ignored. Example applications for this feature are generating a listing of all
-functions located in a source file (e.g. \fBctags \-x \-\-c\-kinds\fP=\fIf\fP
+functions located in a source file (e.g. \fBexctags \-x \-\-c\-kinds\fP=\fIf\fP
 \fIfile\fP), or generating a list of all externally visible global variables
-located in a source file (e.g. \fBctags \-x \-\-c\-kinds\fP=\fIv\fP
+located in a source file (e.g. \fBexctags \-x \-\-c\-kinds\fP=\fIv\fP
 \fB\-\-file\-scope\fP=\fIno file\fP). This option must appear before the first
 file name.
 
@@ -686,7 +686,7 @@
 list of supplied files is empty and no file list is specified with the
 \fB\-L\fP option, then the current directory (i.e. ".") is assumed. Symbolic
 links are followed. If you don't like these behaviors, either explicitly
-specify the files or pipe the output of \fBfind\fP(1) into \fBctags \-L\-\fP
+specify the files or pipe the output of \fBfind\fP(1) into \fBexctags \-L\-\fP
 instead. \fBNote:\fP This option is not supported on all platforms at present.
 It is available if the output of the \fB\-\-help\fP option includes this option.
 See, also, the \fB\-\-exclude\fP to limit recursion.
@@ -1070,7 +1070,7 @@
 .TP 8
 .B CTAGS
 If this environment variable exists, it will be expected to contain a set of
-default options which are read when \fBctags\fP starts, after the
+default options which are read when \fBexctags\fP starts, after the
 configuration files listed in \fBFILES\fP, below, are read, but before any
 command line options are read. Options appearing on the command line will
 override options specified in this variable. Only options will be read from