|CTAGS(1)||General Commands Manual||CTAGS(1)|
] file ...
ctagsmakes a tags file from the specified C, Pascal, Fortran, YACC, lex, and Lisp sources. A tags file gives the locations of specified objects in a group of files. Each line of the tags file contains the object name, the file in which it is defined, and a search pattern for the object definition, separated by whitespace. Using the tags file, a text editor such as ex(1) or vi(1) can quickly locate these object definitions. Indexed objects include subroutines, typedefs, defines, structs, enums, and unions. The options are as follows:
#definesthat don't take arguments;
#definesthat take arguments are tagged automatically.
/.../) (the default).
$ ctags -v files | sort -f > index $ vgrind -x index
ctagsproduces a list of object names, the line number and file name on which each is defined, as well as the text of that line and prints this on the standard output. This is a simple index which can be printed out as an off-line readable function index.
(’, or ‘
[’, otherwise, they are treated as lex files. Other files are first examined to see if they contain any Pascal or Fortran routine definitions and, if not, are searched for C style definitions. The tag
mainis treated specially in C programs. The tag formed is created by prepending ‘M’ to the name of the file, with the trailing “.c” and any leading pathname components removed. This makes use of
ctagspractical in directories with more than one program. Yacc and lex files each have a special tag. yyparse is the start of the second section of the yacc file, and yylex is the start of the second section of the lex file.
ctagsutility exits 0 on success, and >0 if an error occurs. Duplicate objects are not considered errors. mg(1), vi(1)
ctagsutility is compliant with the IEEE Std 1003.1-2008 (“POSIX.1”) specification, though its presence is optional. The flags [
ctagsis “not required to accommodate these languages, although implementors are encouraged to do so”.
ctagscommand appeared in 2BSD.
ctagsdoesn't understand about Pascal types. The method of deciding whether to look for C, Pascal or FORTRAN functions is a hack.
ctagsrelies on the input being well formed, and any syntactical errors will completely confuse it. It also finds some legal syntax confusing; for example, since it doesn't understand
#ifdef's (incidentally, that's a feature, not a bug), any code with unbalanced braces inside
#ifdef's will cause it to become somewhat disoriented. In a similar fashion, multiple line changes within a definition will cause it to enter the last line of the object, rather than the first, as the searching pattern. The last line of multiple line
typedef's will similarly be noted.
|December 31, 2015||OpenBSD-current|