mirror of
https://github.com/GnoConsortium/gno.git
synced 2024-08-29 08:29:03 +00:00
200 lines
6.4 KiB
Groff
200 lines
6.4 KiB
Groff
.\" Copyright (c) 1987, 1990, 1993
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
.\" must display the following acknowledgement:
|
|
.\" This product includes software developed by the University of
|
|
.\" California, Berkeley and its contributors.
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
.\" may be used to endorse or promote products derived from this software
|
|
.\" without specific prior written permission.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" @(#)ctags.1 8.1 (Berkeley) 6/6/93
|
|
.\"
|
|
.TH CTAGS 1 "October 1997" GNO "Commands and Applications"
|
|
.SH NAME
|
|
.BR ctags
|
|
\- create a tags file
|
|
.SH SYNOPSIS
|
|
.BR ctags
|
|
.RB [ -BFadtuwvx ]
|
|
.RB [ -f
|
|
.IR tagsfile ]
|
|
.IR name ...
|
|
.SH DESCRIPTION
|
|
.BR Ctags
|
|
makes a tags file for
|
|
.BR ex (1)
|
|
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
|
|
white-space.
|
|
Using the
|
|
.BR tags
|
|
file,
|
|
.BR ex (1)
|
|
can quickly locate these object definitions.
|
|
Depending upon the options provided to
|
|
.BR ctags ,
|
|
objects will consist of subroutines, typedefs, defines, structs,
|
|
enums and unions.
|
|
.IP "\fB-B\fR"
|
|
use backward searching patterns
|
|
.RB ( "?...?" ).
|
|
.IP "\fB-F\fR"
|
|
use forward searching patterns
|
|
.RB ( "/.../" )
|
|
(the default).
|
|
.IP "\fB-a\fR"
|
|
append to
|
|
.BR tags
|
|
file.
|
|
.IP "\fB-d\fR"
|
|
create tags for #defines that don't take arguments; #defines
|
|
that take arguments are tagged automatically.
|
|
.IP "\fB-f\fR"
|
|
Places the tag descriptions in a file called
|
|
.IR tagsfile .
|
|
The default behaviour is to place them in a file called
|
|
.BR tags .
|
|
.IP "\fB-t\fR"
|
|
create tags for typedefs, structs, unions, and enums.
|
|
.IP "\fB-u\fR"
|
|
update the specified files in the
|
|
.BR tags
|
|
file, that is, all
|
|
references to them are deleted, and the new values are appended to the
|
|
file. (Beware: this option is implemented in a way which is rather
|
|
slow; it is usually faster to simply rebuild the
|
|
.BR tags
|
|
file.)
|
|
.IP "\fB-v\fR"
|
|
An index of the form expected by
|
|
.BR vgrind (1)
|
|
is produced on the standard output. This listing
|
|
contains the object name, file name, and page number (assuming 64
|
|
line pages). Since the output will be sorted into lexicographic order,
|
|
it may be desired to run the output through
|
|
.BR sort (1).
|
|
Sample use:
|
|
.nf
|
|
|
|
ctags \-v files \&| sort \-f > index
|
|
vgrind \-x index
|
|
.fi
|
|
.IP "\fB-w\fR"
|
|
suppress warning diagnostics.
|
|
.IP "\fB-x\fR"
|
|
.BR ctags
|
|
produces 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.
|
|
.LP
|
|
Files whose names end in
|
|
.BR \&.c
|
|
or
|
|
.BR \&.h
|
|
are assumed to be C
|
|
source files and are searched for C style routine and macro definitions.
|
|
Files whose names end in
|
|
.BR \&.y
|
|
are assumed to be YACC source files.
|
|
Files whose names end in
|
|
.BR \&.l
|
|
are assumed to be lisp files if their
|
|
first non-blank character is `;', `(', 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.
|
|
.LP
|
|
The tag
|
|
.BR main
|
|
is treated specially in C programs. The tag formed
|
|
is created by prepending
|
|
.BR M
|
|
to the name of the file, with the
|
|
trailing
|
|
.BR \&.c
|
|
and any leading pathname components removed. This
|
|
makes use of
|
|
.BR ctags
|
|
practical in directories with more than one
|
|
program.
|
|
.LP
|
|
Yacc and lex files each have a special tag.
|
|
.BR Yyparse
|
|
is the start
|
|
of the second section of the yacc file, and
|
|
.BR yylex
|
|
is the start of
|
|
the second section of the lex file.
|
|
.SH FILES
|
|
.IP "\fBtags\fR"
|
|
default output tags file
|
|
.SH DIAGNOSTICS
|
|
.BR Ctags
|
|
exits with a value of 1 if an error occurred, 0 otherwise.
|
|
Duplicate objects are not considered errors.
|
|
.SH ATTRIBUTIONS
|
|
This command was ported from FreeBSD source code
|
|
for distribution with GNO/ME 2.0.6.
|
|
.SH SEE ALSO
|
|
.BR ex (1),
|
|
.BR vi (1)
|
|
.SH BUGS
|
|
Recognition of
|
|
.BR functions ,
|
|
.BR subroutines
|
|
and
|
|
.BR procedures
|
|
for FORTRAN
|
|
and Pascal is done is a very simpleminded way. No attempt
|
|
is made to deal with block structure; if you have two Pascal procedures
|
|
in different blocks with the same name you lose.
|
|
.BR Ctags
|
|
doesn't
|
|
understand about Pascal types.
|
|
.LP
|
|
The method of deciding whether to look for C, Pascal or FORTRAN
|
|
functions is a hack.
|
|
.LP
|
|
.BR Ctags
|
|
relies 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.
|
|
.SH HISTORY
|
|
The
|
|
.BR Ctags
|
|
command appeared in 3.0BSD.
|