| blob | 6ff0fdd5872f1cdb30809ee228ed4cdcaa960d31 |
1 <!-- Creator : groff version 1.19.2 -->
2 <!-- CreationDate: Thu Jul 9 17:03:58 2009 -->
5 <html>
6 <head>
14 </style>
17 </head>
18 <body>
41 <hr>
49 Generate tag files for source code</p>
68 This tag file allows these items to be quickly and easily
70 signifies a language object for which an index entry is
71 available (or, alternatively, the index entry created for
72 that object).</p>
76 lists, in human readable form, information about the various
77 source objects found in a set of language files.</p>
80 are supported by numerous editors, which allow the user to
81 locate the object associated with a name appearing in a
82 source file and jump to the file and line which defines the
83 name. Those known about at the time of this release are:</p>
86 and its derivatives (e.g. Elvis, Vim, Vile, Lemmy),
94 capable of generating different kinds of tags for each of
95 many different languages. For a complete list of supported
96 languages, the names by which they are recognized, and the
97 kinds of tags which are generated for each, see the
107 specified, the language of each source file is automatically
108 selected based upon a mapping of file names to languages.
109 The mappings in effect for each language may be display
112 option. On platforms which support it, if the name of a file
113 is not mapped to a language and the file is executable, the
114 first line of the file is checked to see if the file is a
118 other files names are ignored. This permits running
122 those files whose names are mapped to languages will be
123 scanned.</p>
126 that .h extensions are mapped to C++ files rather than C
127 files is because it is common to use .h extensions in C++,
128 and no harm results in treating them as C++ files.]</p>
135 wealth of available options, defaults are set so that
138 which will create a tag file in the current directory for
139 all recognized source files. The options described below are
140 provided merely to allow custom tailoring to meet special
141 needs.</p>
144 spaces separating the single-letter options from their
145 parameters are optional.</p>
148 the boolean parameters to the long form options (those
149 beginning with "−−" and that take a
160 are either ignored or useful only when used while running in
162 be noted.</p>
165 may appear anywhere on the command line, affecting only
166 those files which follow the option. A few options, however,
167 must appear before the first file name and will be noted as
168 such.</p>
171 language names will accept those names in either upper or
172 lower case. See the
174 complete list of the built-in language names.</p>
201 <p>Use backward searching patterns (e.g. ?pattern?).
202 [Ignored in etags mode]</p></td>
213 <p>Enable etags mode, which will create a tag file for use
216 (either by renaming, or creating a link to, the executable),
217 etags mode will be enabled. This option must appear before
218 the first file name.</p></td>
219 </table>
228 "−", then the tag file is written to
231 contains something other than a valid tags line. This will
233 *.c", which would otherwise overwrite your first C file
234 with the tags generated by the rest! It will also refuse to
235 accept a multi-character file name which begins with a
236 ’−’ (dash) character, since this most
237 likely means that you left out the tag file name and this
238 option tried to grab the next option as the file name. If
239 you really want to name your output tag file
242 the first file name. If this option is specified more than
243 once, only the last will apply.</p>
259 searching patterns (e.g. /pattern/) (default). [Ignored in
260 etags mode]</p></td>
261 </table>
266 extensions, separated by periods, which are to be
267 interpreted as include (or header) files. To indicate files
268 having no extension, use a period not followed by a
271 of a particular kinds of tags is interpreted (i.e. whether
272 or not they are considered as globally visible or visible
273 only within the file in which they are defined); it does not
274 map the extension to any particular language. Any tag which
275 is located in a non-include file and cannot be seen (e.g.
276 linked to) from another file is considered to have
277 file-limited (e.g. static) scope. No kind of tag appearing
278 in an include file will be considered to have file-limited
279 scope. If the first character in the list is a plus sign,
280 then the extensions in the list will be appended to the
281 current list; otherwise, the list will replace the current
283 option. The default list is
286 that if an extension supplied to this option is not already
288 above), you will also need to use either the
296 which are to be specially handled while parsing C and C++
297 source files. This option is specifically provided to handle
298 special cases arising through the use of preprocessor
299 macros. When the identifiers listed are simple identifiers,
300 these identifiers will be ignored during parsing of the
301 source files. If an identifier is suffixed with a
303 parenthesis-enclosed argument list which may immediately
304 follow the identifier in the source files. If two
306 character, the first identifiers is replaced by the second
307 identifiers for parsing purposes. The list of identifiers
308 may be supplied directly on the command line or read in from
309 a separate file. If the first character of
315 filename from which to read a list of identifiers, one per
317 list of identifiers (or identifier pairs) to be specially
318 handled, each delimited by a either a comma or by white
319 space (in which case the list should be quoted to keep the
320 entire list as one command line argument). Multiple
322 of ignore identifiers, supply a single dash
326 useful when preprocessor macros are used in such a way that
327 they cause syntactic confusion due to their presence.
328 Indeed, this is the best way of working around a number of
329 problems caused by the presence of syntax-busting macros in
331 illustrate this point.</p>
334 ARGDECL4(void *, ptr, long int, nbytes)</p>
338 interpreted to be the name of the function instead of the
343 RCS version string in module */ <br>
347 example the macro invocation looks too much like a function
348 definition because it is not followed by a semicolon
349 (indeed, it could even be followed by a global variable
350 definition that would look much like a K&R style
351 function parameter declaration). In fact, this seeming
352 function definition could possibly even cause the rest of
353 the file to be skipped over while trying to complete the
358 <br>
359 // your content here <br>
360 };</p>
364 expands to something different for each platform. For
365 instance CLASS may be defined as "class
366 __declspec(dllexport)" on Win32 platforms and simply
369 incorrectly parsed. Correct behavior can be restored by
375 file names for which tags should be generated. If
377 names are read from standard input. File names read using
378 this option are processed following file names appearing on
379 the command line. Options are also accepted in this input.
380 If this option is specified more than once, only the last
382 line-oriented mode, where a new line is the only delimiter
383 and non-trailing white space is considered significant, in
384 order that file names containing spaces may be supplied
385 (however, trailing white space is stripped from lines); this
386 can affect how options are parsed if included in the
387 input.</p>
405 </td>
416 <p>Equivalent to
419 </td>
420 </table>
476 <p>This option is silently ignored for
477 backward-compatibility with the ctags of SVR4 Unix.</p></td>
488 <p>Print a tabular, human-readable cross reference (xref)
489 file to standard output instead of generating a tag file.
490 The information contained in the output includes: the tag
491 name; the kind of tag; the line number, file name, and
492 source line (with extra white space condensed) of the file
493 which defines the tag. No tag file is written and all
494 options affecting tag file output will be ignored. Example
495 applications for this feature are generating a listing of
496 all functions located in a source file (e.g. <b>ctags
498 generating a list of all externally visible global variables
502 option must appear before the first file name.</p></td>
503 </table>
509 generated from the specified files should be appended to
510 those already present in the tag file or should replace
511 them. This option is off by default. This option must appear
512 before the first file name.</p>
519 many times as desired. This supports Emacs’ capability
521 files. [Available only in etags mode]</p>
527 excluded files and directories. This option may be specified
528 as many times as desired. For each file name considered by
530 option will be compared against both the complete path (e.g.
531 some/path/base.ext) and the base name (e.g. base.ext) of the
532 file, thus allowing patterns which match a given file name
533 irrespective of its path, or match only a specific path. If
534 appropriate support is available from the runtime library of
536 shell wildcards (not regular expressions) common on Unix (be
537 sure to quote the option parameter to protect the wildcards
538 from being expanded by the shell before being passed to
541 shell wildcards are available on your platform by examining
545 names using a simple textual comparison.</p>
549 then the rest of the string is interpreted as a file name
550 from which to read exclusion patterns, one per line. If
552 cleared. Note that at program startup, the default exclude
555 directories for which it is generally not desirable to
557 option.</p>
563 command used to locate tags in the source file. [Ignored in
564 etags mode]</p>
568 letter is accepted) are:</p>
583 numbers in the tag file for locating tags. This has four
584 advantages:</p> </td>
585 </table>
600 resulting tag file.</p></td>
612 the line defining the tag has changed, causing the pattern
614 are able to recover in many such instances).</p></td>
639 mode, duplicate entries are dropped because the search
640 patterns they generate are identical, making the duplicate
641 entries useless.</p></td>
642 </table>
645 option has one significant drawback: changes to the source
646 files can cause the line numbers recorded in the tag file to
647 no longer correspond to the lines in the source file,
648 causing jumps to some tags to miss the target definition by
649 one or more lines. Basically, this option is best used when
650 the source code to which it is applied is not subject to
651 change. Selecting this option type causes the following
667 patterns for all tags, rather than the line numbers usually
668 used for macro definitions. This has the advantage of not
669 referencing obsolete line numbers when lines have been added
670 or removed since the tag file was generated.</p></td>
681 <p>In this mode, patterns are generally used with a few
682 exceptions. For C, line numbers are used for macro
683 definition tags. This was the default format generated by
685 default for this option. For Fortran, line numbers are used
686 for common blocks because their corresponding source lines
687 are generally identical, making pattern searches useless for
688 finding all matches.</p></td>
689 </table>
695 extra tag entries for certain kinds of information. The
697 representing one kind of extra tag entry to include in the
700 effect of each flag is added to, or removed from, those
701 currently enabled; otherwise the flags replace any current
702 settings. The meaning of each flag is as follows:</p>
717 for the base file name of every source file (e.g.
719 the file.</p></td>
731 class-qualified tag entry for each tag which is a member of
732 a class (for languages for which this information is
733 extracted; currently C++, Eiffel, and Java). The actual form
734 of the qualified tag depends upon the language from which
735 the tag was derived (using a form that is most natural for
736 how qualified calls are specified in the language). For C++,
739 allow easier location of a specific tags when multiple
740 occurrences of a tag name occur in the tag file. Note,
741 however, that this could potentially more than double the
742 size of the tag file.</p></td>
743 </table>
749 extension fields which are to be included in the entries of
752 one-letter flags, each representing one type of extension
753 field to include, with the following meanings (disabled by
754 default unless indicated):</p>
769 of class members</p></td>
803 [enabled]</p> </td>
870 parameter list)</p></td>
882 field</p> </td>
895 </table>
899 to add it to the default set, or ’−’ to
901 or ’−’ sign, only those kinds explicitly
903 overriding the default set). This option is ignored if the
905 specified. The default value of this option is
912 only for a single file (i.e. tags which cannot be seen
913 outside of the file in which they are defined, such as
916 enabled by default.</p>
922 as a filter, reading source file names from standard input
923 and printing their tags to standard output on a file-by-file
925 sorted only within the source file in which they are
926 defined. File names are read from standard input in
928 option) and only after file names listed on the command line
932 ignored. This option is quite esoteric and is disabled by
933 default. This option must appear before the first file
934 name.</p>
940 standard output following the tags for each file name parsed
942 may permit an application reading the output of ctags to
943 determine when the output for each file is finished. Note
944 that if the file name read is a directory and
946 printed only one once at the end of all tags found for by
947 descending the directory. This string will always be
948 separated from the last tag line for the file by its
949 terminating newline. This option is quite esoteric and is
950 empty by default. This option must appear before the first
951 file name.</p>
959 file format and level 2 specifies a new extended format
960 containing extension fields (but in a manner which retains
962 implementations). The default level is 2. This option must
963 appear before the first file name. [Ignored in etags
964 mode]</p>
969 detailed usage description, and then exits.</p>
976 preprocessor conditional should be examined for non-macro
977 tags (macro tags are always included). Because the intent of
978 this construct is to disable code, the default value of this
980 only and does not guarantee skipping code within an
982 to generate tags when preprocessor conditionals are too
983 complex follows all branches of a conditional. This option
984 is disabled by default.</p>
987 <p style="margin-left:11%;"><b>−−<LANG>−kinds</b>=<i>[+|−]kinds</i></p>
990 language-specific kinds of tags (or kinds) to include in the
991 output file for a particular language, where
993 built-in language names (see the
996 one-letter flags designating kinds of tags (particular to
997 the language) to either include or exclude from the output.
998 The specific sets of flags recognized for each language,
999 their meanings and defaults may be list using the
1002 to add it to, or ’−’ to remove it from,
1003 the default set. In the absence of any preceding
1006 the output (i.e. overriding the default for the specified
1007 language).</p>
1010 for the C language, in order to add prototypes and external
1011 variable declarations to the default set of tag kinds, but
1012 exclude macros, use
1014 include only tags for functions, use
1023 options taking language names. The typical use of this
1024 option is to first define the language, then map file names
1026 regular expressions using
1028 its tags are found.</p>
1034 mapped to languages (see the
1037 (either a built-in or user-defined language), a colon, and a
1038 list of file extensions and/or file name patterns. A file
1039 extension is specified by preceding the extension with a
1041 specified by enclosing the pattern in parentheses (e.g.
1043 available from the runtime library of your C compiler, then
1044 the file name pattern may contain the usual shell wildcards
1045 common on Unix (be sure to quote the option parameter to
1046 protect the wildcards from being expanded by the shell
1048 shell wildcards are available on your platform by examining
1051 list; otherwise, the file name patterns are matched against
1052 file names using a simple textual comparison. When mapping a
1053 file extension, it will first be unmapped from any other
1054 languages.</p>
1057 character in a map is a plus sign, then the extensions and
1058 file name patterns in that map will be appended to the
1059 current map for that language; otherwise, the map will
1060 replace the current map. For example, to specify that only
1061 files with extensions of .c and .x are to be treated as C
1062 language files, use
1064 also add files with extensions of .j as Java language files,
1065 specify
1067 To map makefiles (e.g. files named either
1072 To map files having no extension, specify a period not
1075 a particular language (thus inhibiting automatic generation
1076 of tags for that language), specify an empty extension list
1077 (e.g.
1079 To restore the default language mappings for all a
1081 for the mapping. To specify restore the default language
1082 mappings for all languages, specify
1084 Note that file extensions are tested before file name
1085 patterns when inferring the language of a file.</p>
1091 automatically selects the language of a source file,
1092 ignoring those files whose language cannot be determined
1095 or user-defined) to be used for every supplied file instead
1096 of automatically selecting the language based upon its
1098 indicates that the language should be automatically selected
1099 (which effectively disables this option).</p>
1106 a comma-separated list of language names (case-insensitive;
1107 either built-in or user-defined). If the first language of
1109 ’−’, the current list will be cleared
1111 Until a ’−’ is encountered, each language
1112 in the list will be added to the current list. As either the
1114 the list, the languages following it are added or removed
1115 from the current list, respectively. Thus, it becomes simple
1116 to replace the current list with a new one, or to add or
1117 remove languages from the current list. The actual list of
1118 files for which tags will be generated depends upon the
1119 language extension mapping in effect (see the
1121 languages, including user-defined languages are enabled
1122 unless explicitly disabled using this option. Language names
1126 valid argument. See the
1128 complete list of the built-in language names.</p>
1134 software license to standard output, and then exits.</p>
1137 <p style="margin-left:11%;"><b>−−line−directives</b>[=<i>yes</i>|<i>no</i>]</p>
1141 present in the output of preprocessors and contain the line
1142 number, and possibly the file name, of the original source
1143 file(s) from which the preprocessor output file was
1145 to generate tag entries marked with the file names and line
1146 numbers of their locations original source file(s), instead
1147 of their actual locations in the preprocessor output. The
1148 actual file names placed into the tag file will have the
1149 same leading path components as the preprocessor output
1150 file, since it is assumed that the original source files are
1151 located relative to the preprocessor output file (unless, of
1152 course, the #line directive specifies an absolute path).
1154 generally only useful when used together with the
1156 option. Also, you may have to use either the
1159 extension of the preprocessor output file is not known to
1166 links (if supported) should be followed. When disabled,
1167 symbolic links are ignored. This option is on by
1168 default.</p>
1171 <p style="margin-left:11%;"><b>−−list−kinds</b>[=<i>language</i>|<i>all</i>]</p>
1174 for either the specified language or all languages, and then
1175 exits. Each kind of tag recorded in the tag file is
1176 represented by a one-letter flag, which is also used to
1177 filter the tags placed into the output through use of the
1179 that some languages and/or tag kinds may be implemented
1180 using regular expressions and may not be available if regex
1183 kind listed is enabled unless followed by
1187 <p style="margin-left:11%;"><b>−−list−maps</b>[=<i>language</i>|<i>all</i>]</p>
1190 file name patterns which associate a file name with a
1191 language for either the specified language or all languages,
1200 language names are case insensitive and may be used in the
1212 is specified as the first option on the command line, it
1213 will disable the automatic reading of any configuration
1214 options from either a file or the environment (see
1221 encountered in the list of supplied files. If the list of
1222 supplied files is empty and no file list is specified with
1225 you don’t like these behaviors, either explicitly
1228 option is not supported on all platforms at present. It is
1230 option includes this option. See, also, the
1234 <p style="margin-left:11%;"><b>−−regex−<LANG></b>=<i>/regexp/replacement/[kind−spec/][flags]</i></p>
1237 pair define a regular expression replacement pattern,
1239 which to generate tags from source files mapped to the named
1241 built-in or user-defined language). The regular expression,
1244 locate a single source line containing a tag and may specify
1245 tab characters using \t. When a matching line is found, a
1246 tag will be generated for the name defined by
1251 to the option can actually be replaced by any character.
1252 Note that whichever separator character is used will have to
1254 wherever it is used in the parameter as something other than
1255 a separator. The regular expression defined by this option
1256 is added to the current list of regular expressions for the
1257 specified language unless the parameter is omitted, in which
1258 case the current list is cleared.</p>
1263 expand for all matching lines to a non-empty string of
1264 characters, or a warning message will be reported. An
1270 comma, a name (without spaces), a comma, a description,
1271 followed by a separator, which specify the short and long
1272 forms of the kind value and its textual description
1274 Either the kind name and/or the description may be omitted.
1277 more single-letter characters having the following effect
1293 interpreted as a Posix basic regular expression.</p></td>
1305 interpreted as a Posix extended regular expression
1306 (default).</p> </td>
1318 expression is to be applied in a case-insensitive
1319 manner.</p> </td>
1320 </table>
1324 support for regular expressions, which depends upon your
1325 platform. You can determine if support for regular
1326 expressions is compiled in by examining the output of the
1336 <p style="margin-left:11%;"><b>−−sort</b>[=<i>yes</i>|<i>no</i>|<i>foldcase</i>]</p>
1342 case-folded) sorting. Fast binary searches of tag files
1343 sorted with case-folding will require special support from
1344 tools using tag files, such as that found in the ctags
1345 readtags library, or Vim version 6.2 or higher (using
1347 the first file name. [Ignored in etags mode]</p>
1353 recorded in the tag file should be relative to the directory
1354 containing the tag file, rather than relative to the current
1355 directory, unless the files supplied on the command line are
1356 specified with absolute paths. This option must appear
1365 source files read and the tag file written during the
1367 default. This option must appear before the first file
1368 name.</p>
1374 prints out information on option processing and a brief
1375 message describing what action is being taken for each file
1377 read command line arguments until after options are read
1380 option is the first argument on the command line, it will
1381 take effect before any options are read from these sources.
1389 guaranteed to always contain the string "Exuberant
1397 considers each file name in turn, it tries to determine the
1398 language of the file by applying the following three tests
1399 in order: if the file extension has been mapped to a
1400 language, if the file name matches a shell pattern mapped to
1401 a language, and finally if the file is executable and its
1402 first line specifies an interpreter using the Unix-style
1404 If a language was identified, the file is opened and then
1405 the appropriate language parser is called to operate on the
1406 currently open file. The parser parses through the file and
1407 adds an entry to the tag file for each language object it is
1409 details on these entries.</p>
1413 requirements on C code as do legacy implementations. Older
1414 implementations of ctags tended to rely upon certain
1415 formatting assumptions in order to help it resolve coding
1416 dilemmas caused by preprocessor conditionals.</p>
1420 preprocessor directives. If a preprocessor conditional is
1421 encountered within a statement which defines a tag,
1423 conditional (except in the special case of "#if
1425 reason for this is that failing to pursue only one branch
1426 can result in ambiguous syntax, as in the following
1427 example:</p>
1430 TWO_ALTERNATIVES <br>
1431 struct { <br>
1432 #else <br>
1433 union { <br>
1434 #endif</p>
1437 long b;</p>
1442 cannot be followed, or braces become unbalanced and
1444 syntax.</p>
1447 application of this heuristic fails to properly parse a
1448 file, generally due to complicated and inconsistent pairing
1450 using a different heuristic which does not selectively
1451 follow conditional preprocessor branches, but instead falls
1453 column 1 as indicating the end of a block once any brace
1454 imbalance results from following a #if conditional
1455 branch.</p>
1458 will also try to specially handle arguments lists enclosed
1459 in double sets of parentheses in order to accept the
1460 following conditional construct:</p>
1463 __ARGS((int one, char two));</p>
1467 automatically ignored and the previous name will be
1468 used.</p>
1471 definitions are specially handled. In order for consistency
1472 with all types of operators (overloaded and conversion), the
1473 operator name in the tag file will always be preceded by the
1475 operator definition was written as
1479 or appending to the tag file, it is sorted by the tag name,
1480 removing identical tag lines.</p>
1487 running in etags mode, each entry in the tag file consists
1488 of a separate line, each looking like this in the most
1489 general case:</p>
1492 <p style="margin-left:12%; margin-top: 1em">tag_name<TAB>file_name<TAB>ex_cmd;"<TAB>extension_fields</p>
1495 separators of these lines are specified as follows:</p>
1532 associated with the tag is located</p></td>
1555 the file; generally a search pattern (either /pattern/ or
1558 this EX command under certain circumstances to include a set
1559 of extension fields (described below) embedded in an EX
1560 comment immediately appended to the EX command, which leaves
1562 implementations.</p> </td>
1563 </table>
1566 tags are written into the tag file for internal purposes.
1567 These tags are composed in such a way that they always sort
1568 to the top of the file. Therefore, the first two characters
1569 of these tags are used a magic number to detect a tag file
1570 for purposes of determining whether a valid tag file is
1571 being overwritten rather than a source file.</p>
1574 name of each source file will be recorded in the tag file
1575 exactly as it appears on the command line. Therefore, if the
1576 path you specified on the command line was relative to the
1577 current directory, then it will be recorded in that same
1578 manner in the tag file. See, however, the
1580 behavior can be modified.</p>
1583 fields are tab-separated key-value pairs appended to the end
1584 of the EX command as a comment, as described above. These
1585 key value pairs appear in the general form
1587 lines of the tag file are controlled by the
1589 the meaning of their values are as follows:</p>
1605 specific to the language.</p></td>
1616 <p>Indicates that the tag has file-limited visibility. This
1617 key has no corresponding value.</p></td>
1628 <p>Indicates the type, or kind, of tag. Its value is either
1629 one of the corresponding one-letter flags described under
1631 options above, or a full name. It is permitted (and is, in
1632 fact, the default) for the key portion of this field to be
1633 omitted. The optional behaviors are controlled with the
1635 </table>
1640 limited implementation (abstract vs. concrete) of a routine
1660 which this class is derived (i.e. inherits from).</p></td>
1672 representation of the signature of a routine. A routine
1673 signature in its complete form specifies the return type of
1674 a routine and its formal argument list. This extension field
1675 is presently supported only for C-based languages and does
1676 not include the return type.</p></td>
1677 </table>
1680 information on the scope of the tag definition may be
1681 available, with the key portion equal to some
1682 language-dependent construct name and its value the name
1683 declared for that construct in the program. This scope entry
1684 indicates the scope in which the tag was found. For example,
1685 a tag generated for a C structure member would have a scope
1694 the current directory. Once the tag file is built, the
1695 following commands exercise the tag indexing feature:</p>
1705 tag</b></p> </td>
1711 position the cursor at the file and line where
1735 the cursor.</p></td>
1747 location before jump to tag (not widely implemented).</p></td>
1748 </table>
1756 the current directory. Once the tag file is built, the
1757 following commands exercise the tag indexing feature:
1758 <b><br>
1769 TAG. The default tag is the identifier under the cursor.</p>
1786 </td>
1798 definition for the last tag.</p></td>
1800 </td>
1801 </table>
1805 document.</p>
1812 5.1 and later can handle the new extended tag file format
1815 jump to the definition for a tag, highlight the word, the
1816 press Ctrl-D. NEdit 5.1 can can read multiple tag files from
1817 different directories. Setting the X resource nedit.tagFile
1818 to the name of a tag file instructs NEdit to automatically
1819 load that tag file at startup time.</p>
1828 missing tags or improperly generating inappropriate tags.
1830 common cases, this is the single biggest cause of reported
1831 problems. In particular, the use of preprocessor constructs
1833 You can work around many such problems by using the
1839 that the wrong line may be found by your editor if there
1840 exists another source line which is identical to the line
1841 containing the tag. The following example demonstrates this
1842 condition:</p>
1845 variable;</p>
1848 void foo(variable) <br>
1849 int variable; <br>
1850 {</p>
1857 which editor you use and where in the code you happen to be,
1858 it is possible that the search pattern may locate the local
1859 parameter declaration in foo() before it finds the actual
1860 global variable definition, since the lines (and therefore
1861 their search patterns are identical). This can be avoided by
1872 C++ member function definition (e.g.
1874 determine whether the scope specifier is a class name or a
1875 namespace specifier and always lists it as a class name in
1876 the scope portion of the extension fields. Also, if a C++
1877 function is defined outside of the class declaration (the
1878 usual case), the access specification (i.e. public,
1879 protected, or private) and implementation information (e.g.
1880 virtual, pure virtual) contained in the function declaration
1881 are not known when the tag is generated for the function
1882 definition. It will, however be available for prototypes
1886 tags are generated for language objects inherited into a
1887 class.</p>
1906 variable exists, it will be expected to contain a set of
1909 are read, but before any command line options are read.
1910 Options appearing on the command line will override options
1911 specified in this variable. Only options will be read from
1912 this variable. Note that all white space in this variable is
1913 considered a separator, making it impossible to pass an
1914 option parameter containing an embedded space. If this is a
1915 problem, use a configuration file instead.</p></td>
1940 <p>On Unix-like hosts where mkstemp() is available, the
1941 value of this variable specifies the directory in which to
1942 place temporary files. This can be useful if the size of a
1943 temporary file becomes too large to fit on the partition
1944 holding the default temporary directory defined at
1946 if either (1) an emacs-style tag file is being generated,
1948 the program was compiled to use an internal sort algorithm
1949 to sort the tag files instead of the the sort utility of the
1950 operating system. If the sort utility of the operating
1951 system is being used, it will generally observe this
1953 value of TMPDIR will be ignored.</p></td>
1954 </table>
1961 (on MSDOS, MSWindows only) <br>
1962 /etc/ctags.conf <br>
1963 /usr/local/etc/ctags.conf <br>
1964 $HOME/.ctags <br>
1965 $HOME/ctags.cnf (on MSDOS, MSWindows only) <br>
1966 .ctags <br>
1967 ctags.cnf (on MSDOS, MSWindows only)</i></p>
1970 files exist, each will be expected to contain a set of
1971 default options which are read in the order listed when
1973 variable is read or any command line options are read. This
1974 makes it possible to set up site-wide, personal or
1975 project-level defaults. It is possible to compile
1977 any of those shown above, which will be indicated if the
1981 line will override options specified in these files. Only
1982 options will be read from these files. Note that the option
1983 files are read in line-oriented mode in which spaces are
1984 significant (since shell quoting is not possible). Each line
1985 of the file is read as one command line parameter (as if it
1986 were quoted with single quotes). Therefore, use new lines to
1987 indicate separate command-line arguments.</p>
2004 </td>
2018 </td>
2019 </table>
2026 Exuberant Ctags web site at:</p>
2035 at:</p>
2046 http://DarrenHiebert.com/</p>
2053 at all times of rendering some service to every member of
2057 effort and exertion put forth by man from the fullness of
2058 his heart is worship, if it is prompted by the highest
2070 ctags program by Steve Kirkendall
2072 clone (though virtually none of the original code
2073 remains).</p>
2078 both to developing the editor as a service to others, and to
2079 helping the orphans of Uganda.</p>
2083 shamelessly stolen from the info page for GNU
2085 <hr>
2086 </body>
2087 </html>