Update to version 5.5.

Package change: $PKG_SYSCONFDIR/ctags.conf added as glogal,
configuration file, parsed before /etc/ctags.conf,
/usr/local/etc/ctags.conf and $HOME/.ctags

Changes since version 5.4:
ctags-5.5 (Tue Apr 1 2003)
* Changed kind indicator for methods from 'f' to 'm' [Tcl].
* Changed tags within interfaces to be disabled by default (like prototypes in
  C/C++) [Fortran].
* Removed explicit descriptions of individual --<LANG>-types options from
  --help output. See new --list-languages and --list-kinds options.
* Removed explicit list of supported languages and supported tag kinds and
  mapping patterns from man page. See new --list-languages, --list-kinds, and
  --list-maps options.
* Renamed --<LANG>-types option to --<LANG>-kinds (still accepts old name).
* Added --list-kinds option.
* Added --list-maps option.
* Added --list-languages option.
* Added support for dimensioned variables, contributed by Simon Bohlin [ASP].
* Added support for C# language.
* Added support for Erlang language, contributed by Brent Fulgham.
* Added support for HTML language files.
* Added support for JavaScript language files.
* Added support for SML (Standard ML) language, contributed by Venkatesh Prasad.
* Added mapping for .plx to Perl.
* Added tags for autocommand groups [Vim, Patch #664685].
* Added support for numerous language extensions [Fortran].
* Added '$', 'D', and 'd' in column 1 as comment characters [Fortran].
* Added special handling of --options=NONE to disable automatic reading of
  options from configuration files or environment.
* Added check for case-insensitive filenames to configure.
* Fixed problem with lower case <SID> tag [Vim, Bug #657327].
* Fixed problem recognizing indented code [Vim, Patch #664685].
* Fixed problem with infinite loop in certain comments [PL/SQL, Bug #629115].
* Fixed problem of incorrect extension field [C, Bug #639639].
* Fixed problem of empty scoping extension field [C, Bug #639644].
* Fixed missing tags for functions split across lines [PHP, Bug #681824].
* Fixed missing tags for nested subprograms using 'contains' [Fortran, Bug #670433].
* Fixed missing tags when variable has same name as keyword [Fortran].
* Fixed spurious tag when an array-spec occurs within an entity-decl [Fortran].
* Fixed mishandling of multiline raw strings [Python, Bug #699171].
* Fixed missing scope extension field on namespaces [C++, C#, Bug #665086].
* Fixed several bugs causing missed tags [Fortran].
* Fixed problem with --langmap option preventing clearing of map [Bug #688442].
* Fixed recognition of Unicode-8 characters [Java].
* Fixed man page errors and omissions.
* Fixed bug in readFieldValue() in readtags library.
* Fixed bug in option parsing in readtags command-line program.
* Fixed portability problems with DJGPP [Bug #692569].
* Fixed portability problems with Cygwin.

3 files changed, 78 insertions, 70 deletions

diff --git a/devel/exctags/Makefile b/devel/exctags/Makefile
index 3a7b47fdd85..5e9a492031c 100644
--- a/devel/exctags/Makefile
+++ b/devel/exctags/Makefile
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.6 2002/12/01 23:57:05 seb Exp $
+# $NetBSD: Makefile,v 1.7 2003/04/07 09:30:42 seb Exp $
 #
 
-DISTNAME=	ctags-5.4
+DISTNAME=	ctags-5.5
 PKGNAME=	ex${DISTNAME}
 CATEGORIES=	devel
 MASTER_SITES=	${MASTER_SITE_SOURCEFORGE:=ctags/}
@@ -14,6 +14,7 @@ USE_BUILDLINK2=		# defined
 GNU_CONFIGURE=		# defined
 CONFIGURE_ARGS+=	--enable-macro-patterns
 CONFIGURE_ARGS+=	--with-readlib
+CONFIGURE_ARGS+=	--enable-custom-config=${PKG_SYSCONFDIR}/ctags.conf
 
 CPPFLAGS+=		-DETAGS='\"exetags\"'
 
diff --git a/devel/exctags/distinfo b/devel/exctags/distinfo
index d0909bc9685..e0bf1f09400 100644
--- a/devel/exctags/distinfo
+++ b/devel/exctags/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.5 2002/12/01 23:57:06 seb Exp $
+$NetBSD: distinfo,v 1.6 2003/04/07 09:30:42 seb Exp $
 
-SHA1 (ctags-5.4.tar.gz) = 695bb4c1af11b605963402e6bd71ba588dc2e6d6
-Size (ctags-5.4.tar.gz) = 234277 bytes
+SHA1 (ctags-5.5.tar.gz) = 9e69d653d7847ec22150c4a20705576944fb5bbd
+Size (ctags-5.5.tar.gz) = 241089 bytes
 SHA1 (patch-aa) = 7a482534cd0c560df436f45ae3b697f6b07ef534
-SHA1 (patch-ab) = 993fc2d59dac47d0c6340a5abbb3fe00464b5ae6
+SHA1 (patch-ab) = 592f13430e6d7e2f4574cfcdb924f3bc9502a5e3
diff --git a/devel/exctags/patches/patch-ab b/devel/exctags/patches/patch-ab
index afee2714808..2a9cdb82caa 100644
--- a/devel/exctags/patches/patch-ab
+++ b/devel/exctags/patches/patch-ab
@@ -1,10 +1,10 @@
-$NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
+$NetBSD: patch-ab,v 1.6 2003/04/07 09:30:43 seb Exp $
 
---- ctags.1.orig	Thu Oct 17 21:18:55 2002
+--- ctags.1.orig	2003-04-01 05:02:33.000000000 +0000
 +++ ctags.1
 @@ -1,27 +1,27 @@
--.TH CTAGS 1 "Version 5.4" "Darren Hiebert"
-+.TH EXCTAGS 1 "Version 5.4" "Darren Hiebert"
+-.TH CTAGS 1 "Version 5.5" "Darren Hiebert"
++.TH EXCTAGS 1 "Version 5.5" "Darren Hiebert"
  
  
  .SH "NAME"
@@ -37,18 +37,18 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  human readable form, information about the various source objects found in a
  set of language files.
  
-@@ -148,8 +148,8 @@ names are mapped to languages according 
- .RE
+@@ -62,8 +62,8 @@ to a language and the file is executable
+ 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 all
--files in an entire source directory tree (e.g. "ctags -R"), since only those
-+\fBexctags\fP on all files in either a single directory (e.g. "exctags *"), or 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.
+-\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
++\fBexctags\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
-@@ -159,8 +159,8 @@ treating them as C++ files.
+ [The reason that .h extensions are mapped to C++ files rather than C files
+@@ -73,8 +73,8 @@ treating them as C++ files.]
  
  .SH "OPTIONS"
  
@@ -59,7 +59,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  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.
-@@ -196,7 +196,7 @@ Use backward searching patterns (e.g. ?p
+@@ -111,7 +111,7 @@ Use backward searching patterns (e.g. ?p
  .TP 5
  .B \-e
  Enable etags mode, which will create a tag file for use with the Emacs editor.
@@ -68,16 +68,16 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  "etags" (either by renaming, or creating a link to, the executable), etags
  mode will be enabled. This option must appear before the first file name.
  
-@@ -207,7 +207,7 @@ or "TAGS" when running in etags mode). I
+@@ -122,7 +122,7 @@ or "TAGS" when running in etags mode). I
  "-", 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 multicharacter file name which begins with a '-' (dash) character,
+ 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
-@@ -248,7 +248,7 @@ Specifies a list of tokens which are to 
+@@ -163,7 +163,7 @@ Specifies a list of tokens which are to 
  and C++ source files. This option is specifically provided to handle special
  cases arising through the use of preprocessor macros. When the tokens listed
  are simple tokens, these tokens will be ignored during parsing of the source
@@ -86,19 +86,19 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  ignore any parenthesis-enclosed argument list which may immediately follow the
  token in the source files. If two tokens are separated with the '=' character,
  the first token is replaced by the second token for parsing purposes. The list
-@@ -358,9 +358,9 @@ includes: the tag name; the kind of tag;
+@@ -273,9 +273,9 @@ includes: the tag name; the kind of tag;
  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-types\fP=\fIf\fP
-+functions located in a source file (e.g. \fBexctags -x --c-types\fP=\fIf\fP
+-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-types\fP=\fIv\fP
-+located in a source file (e.g. \fBexctags -x --c-types\fP=\fIv\fP
+-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.
  
-@@ -380,14 +380,14 @@ tag file which "includes" other tag file
+@@ -295,14 +295,14 @@ tag file which "includes" other tag file
  \fB--exclude\fP=[\fIpattern\fP]
  Add \fIpattern\fP to a list of excluded files and directories. This option
  may be specified as many times as desired. For each file name considered by
@@ -113,9 +113,9 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
 -from being expanded by the shell before being passed to \fBctags\fP; also be
 +from being expanded by the shell before being passed to \fBexctags\fP; also be
  aware that wildcards can match the slash character, '/'). You can determine if
- shell wildcards are available on your platfom by examining the output of the
+ shell wildcards are available on your platform by examining the output of the
  \fB--version\fP option, which will include "+wildcards" in the compiled
-@@ -555,7 +555,7 @@ is enabled by default.
+@@ -471,7 +471,7 @@ is enabled by default.
  
  .TP 5
  \fB--filter\fP[=\fIyes\fP|\fIno\fP]
@@ -124,7 +124,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  standard input and printing their tags to standard output on a file-by-file
  basis. If \fB--sorted\fP is enabled, tags are sorted only within the source
  file in which they are defined. File names are read from standard output in
-@@ -569,7 +569,7 @@ by default. This option must appear befo
+@@ -485,7 +485,7 @@ by default. This option must appear befo
  \fB--filter-terminator\fP=\fIstring\fP
  Specifies a string to print to standard output following the tags for each
  file name parsed when the \fB--filter\fP option is enabled. This may permit an
@@ -133,16 +133,16 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  file is finished. Note that if the file name read is a directory and
  \fB--recurse\fP is enabled, this string will be printed only one once at the
  end of all tags found for by descending the directory. This string will always
-@@ -640,7 +640,7 @@ enclosing the pattern in parentheses (e.
+@@ -557,7 +557,7 @@ enclosing the pattern in parentheses (e.
  support is available from the runtime library of your C compiler, then the
  file name pattern may contain the usual shell wildcards common on Unix (be
  sure to quote the option parameter to protect the wildcards from being
 -expanded by the shell before being passed to \fBctags\fP). You can determine
 +expanded by the shell before being passed to \fBexctags\fP). You can determine
- if shell wildcards are available on your platfom by examining the output of
+ if shell wildcards are available on your platform by examining the output of
  the \fB--version\fP option, which will include "+wildcards" in the compiled
  feature list; otherwise, the file name patterns are matched against file names
-@@ -667,7 +667,7 @@ file name patterns when inferring the la
+@@ -584,7 +584,7 @@ file name patterns when inferring the la
  
  .TP 5
  \fB--language-force\fP=\fIlanguage\fP
@@ -150,8 +150,8 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
 +By default, \fBexctags\fP automatically selects the language of a source file,
  ignoring those files whose language cannot be determined (see
  \fBSOURCE FILES\fP, above). This option forces the specified \fIlanguage\fP
- (either built-in or user-defined) to be used for every supplied file instead
-@@ -703,7 +703,7 @@ Prints a summary of the software license
+ (case-insensitive; either built-in or user-defined) to be used for every
+@@ -622,7 +622,7 @@ Prints a summary of the software license
  Specifies whether "#line" directives should be recognized. These are present
  in the output of preprocessors and contain the line number, and possibly the
  file name, of the original source file(s) from which the preprocessor output
@@ -160,7 +160,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  generate tag entries marked with the file names and line numbers of their
  locations original source file(s), instead of their actual locations in the
  preprocessor output. The actual file names placed into the tag file will have
-@@ -714,7 +714,7 @@ absolute path). This option is off by de
+@@ -633,7 +633,7 @@ absolute path). This option is off by de
  generally only useful when used together with the \fB--excmd\fP=\fInumber\fP
  (\fB-n\fP) option. Also, you may have to use either the \fB--langmap\fP or
  \fB--language-force\fP option if the extension of the preprocessor output file
@@ -169,7 +169,25 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  
  .TP 5
  \fB--links\fP[=\fIyes\fP|\fIno\fP]
-@@ -731,7 +731,7 @@ Recurse into directories encountered in 
+@@ -647,7 +647,7 @@ languages. Each kind of tag recorded in 
+ one-letter flag, which is also used to filter the tags placed into the output
+ through use of the \fB--<LANG>-kind\fP option. Note that some languages and/or
+ tag kinds may be implemented using regular expressions and may not be
+-available if regex support is not compiled into \fBctags\fP (see the
++available if regex support is not compiled into \fBexctags\fP (see the
+ \fB--regex-<LANG>\fP option). Each kind listed is enabled unless followed by
+ "[off]".
+ 
+@@ -659,7 +659,7 @@ the \fB--langmap\fP option, and \fBSOURC
+ 
+ .TP 5
+ \fB--list-languages\fP
+-Lists the names of the languages understood by \fBctags\fP. These language
++Lists the names of the languages understood by \fBexctags\fP. These language
+ names are case insensitive and may be used in the \fB--language-force\fP,
+ \fB--languages\fP, \fB--<LANG>-kinds\fP, and \fB--regex-<LANG>\fP options.
+ 
+@@ -676,7 +676,7 @@ Recurse into directories encountered in 
  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
@@ -178,7 +196,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  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.
-@@ -781,13 +781,13 @@ The regular expression is to be applied 
+@@ -729,13 +729,13 @@ The regular expression is to be applied 
  .RE
  
  .RS 5
@@ -189,12 +207,12 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  output of the \fB--version\fP option, which will include "+regex" in the
  compiled feature list.
  
--For more information on the regular expressionss used by \fBctags\fP, see
-+For more information on the regular expressionss used by \fBexctags\fP, see
+-For more information on the regular expressions used by \fBctags\fP, see
++For more information on the regular expressions used by \fBexctags\fP, see
  either the \fBregex(5,7)\fP man page, or the GNU info documentation for regex
  (e.g. "info regex").
  .RE
-@@ -798,7 +798,7 @@ Indicates whether the tag file should be
+@@ -746,7 +746,7 @@ Indicates whether the tag file should be
  \fIyes\fP). Note that the original \fBvi\fP(1) required sorted tags. 
  The \fIfoldcase\fP value specifies case insensitive (or case-folded) sorting.
  Fast binary searches of tag files sorted with case-folding will require
@@ -203,7 +221,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  readtags library, or Vim version 6.2 or higher (using "set ignorecase"). This
  option must appear before the first file name. [Ignored in etags mode]
  
-@@ -814,14 +814,14 @@ option), \fIno\fP otherwise.
+@@ -762,14 +762,14 @@ option), \fIno\fP otherwise.
  .TP 5
  \fB--totals\fP[=\fIyes\fP|\fIno\fP]
  Prints statistics about the source files read and the tag file written during
@@ -220,7 +238,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  until after options are read from the configuration files (see \fBFILES\fP,
  below) and the \fBCTAGS\fP environment variable. However, if this option is
  the first argument on the command line, it will take effect before any options
-@@ -829,7 +829,7 @@ are read from these sources. The default
+@@ -777,13 +777,13 @@ are read from these sources. The default
  
  .TP 5
  \fB--version\fP
@@ -229,17 +247,6 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  guaranteed to always contain the string "Exuberant Ctags".
  
  
-@@ -839,7 +839,7 @@ one-letter flag, which is also used to f
- through use of the \fB--<LANG>-type\fP option. The flags corresponding to each
- tag kind for each langauge are described below. Note that some languages
- and/or tag kinds may be implemented using regular expressions and may not be
--available if regex support is not compiled into \fBctags\fP (see the
-+available if regex support is not compiled into \fBexctags\fP (see the
- \fB--regex-<LANG>\fP option). Kinds are enabled by default
- except where noted (with "[off]").
- 
-@@ -1382,7 +1382,7 @@ labels
- 
  .SH "OPERATIONAL DETAILS"
  
 -As \fBctags\fP considers each file name in turn, it tries to determine the
@@ -247,7 +254,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  language of the file by applying the following three tests in order: if the
  file extension has been mapped to a language, if the file name matches a shell
  pattern mapped to a language, and finally if the file is executable and its
-@@ -1398,9 +1398,9 @@ code as do legacy implementations. Older
+@@ -799,9 +799,9 @@ code as do legacy implementations. Older
  rely upon certain formatting assumptions in order to help it resolve coding
  dilemmas caused by preprocessor conditionals.
  
@@ -259,7 +266,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  conditional (except in the special case of "#if 0", in which case it follows
  only the last branch). The reason for this is that failing to pursue only one
  branch can result in ambiguous syntax, as in the following example:
-@@ -1423,12 +1423,12 @@ long b;
+@@ -824,12 +824,12 @@ long b;
  }
  .RE
  
@@ -274,7 +281,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  selectively follow conditional preprocessor branches, but instead falls back
  to relying upon a closing brace ("}") in column 1 as indicating the end of a
  block once any brace imbalance results from following a #if conditional branch.
-@@ -1602,12 +1602,12 @@ to automatically load that tag file at s
+@@ -1003,12 +1003,12 @@ to automatically load that tag file at s
  
  
  .SH "CAVEATS"
@@ -291,7 +298,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  such problems by using the \fB-I\fP option.
  
  White space is treated as a separator for file names and options read from
-@@ -1616,7 +1616,7 @@ using the \fB--filter\fP option). Theref
+@@ -1017,7 +1017,7 @@ using the \fB--filter\fP option). Theref
  supply file names or other options containing embedded white space (spaces,
  etc.) through these options.
  
@@ -300,16 +307,16 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  the \fB--excmd\fP option), it is entirely possible that the wrong line may be
  found by your editor if there exists another source line which is identical to
  the line containing the tag. The following example demonstrates this condition:
-@@ -1648,7 +1648,7 @@ by use of the \fB--excmd\fP=\fIn\fP opti
+@@ -1049,7 +1049,7 @@ by use of the \fB--excmd\fP=\fIn\fP opti
  \fBCtags\fP has more options than \fBls\fP(1).
  
  When parsing a C++ member function definition (e.g. "className::function"),
 -\fBctags\fP cannot determine whether the scope specifier is a class name or a
 +\fBexctags\fP cannot determine whether the scope specifier is a class name or a
  namespace specifier and always lists it as a class name in the scope portion
- of the extension fields. Also, if the function defintion is located in a
- separate file from than where the class is defined (the usual case), the
-@@ -1663,7 +1663,7 @@ No qualified tags are generated for lang
+ of the extension fields. Also, if a C++ function is defined outside of the
+ class declaration (the usual case), the access specification (i.e. public,
+@@ -1066,7 +1066,7 @@ No qualified tags are generated for lang
  .TP 8
  .B CTAGS
  If this environment variable exists, it will be expected to contain a set of
@@ -318,7 +325,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  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
-@@ -1674,7 +1674,7 @@ embedded space. If this is a problem, us
+@@ -1077,7 +1077,7 @@ embedded space. If this is a problem, us
  .TP 8
  .B ETAGS
  Similar to the \fBCTAGS\fP variable above, this variable, if found, will be
@@ -327,7 +334,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  try to use \fBCTAGS\fP instead.
  
  .TP 8
-@@ -1683,12 +1683,12 @@ On Unix-like hosts where mkstemp() is av
+@@ -1086,12 +1086,12 @@ On Unix-like hosts where mkstemp() is av
  specifies the directory in which to place temporary files. This can be useful
  if the size of a temporary file becomes too large to fit on the partition
  holding the default temporary directory defined at compilation time.
@@ -342,7 +349,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  ignored.
  
  
-@@ -1705,10 +1705,10 @@ ignored.
+@@ -1108,10 +1108,10 @@ ignored.
  .I .ctags (ctags.cnf on MSDOS, MSWindows)
  .IP
  If any of these configuration files exist, each will be expected to contain a
@@ -355,7 +362,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  additional configuration file before any of those shown above, which will be
  indicated if the output produced by the \fB--version\fP option lists the
  "custom-conf" feature. Options appearing in the \fBCTAGS\fP environment
-@@ -1722,10 +1722,10 @@ lines to indicate separate command-line 
+@@ -1125,10 +1125,10 @@ lines to indicate separate command-line 
  
  .TP
  .I tags
@@ -368,7 +375,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  
  .SH "SEE ALSO"
  The official Exuberant Ctags web site at:
-@@ -1735,7 +1735,7 @@ http://ctags.sourceforge.net
+@@ -1138,7 +1138,7 @@ http://ctags.sourceforge.net
  .RE
  
  Also \fBex\fP(1), \fBvi\fP(1), \fBelvis\fP, or, better yet, \fBvim\fP, the
@@ -377,7 +384,7 @@ $NetBSD: patch-ab,v 1.5 2002/12/01 23:57:06 seb Exp $
  Pages web site at:
  
  .RS
-@@ -1763,7 +1763,7 @@ to humanity."
+@@ -1166,7 +1166,7 @@ to humanity."
  
  
  .SH "CREDITS"