From 6c4cfaf836b948efbffce349f5c20a0819d6bfdd Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sun, 26 Apr 2009 19:01:24 +0000 Subject: [PATCH] (Tags): Clarify the text some more. --- doc/emacs/maintaining.texi | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/emacs/maintaining.texi b/doc/emacs/maintaining.texi index 63e748680b4..cd0a733c850 100644 --- a/doc/emacs/maintaining.texi +++ b/doc/emacs/maintaining.texi @@ -1484,22 +1484,22 @@ Of course, you should substitute the proper years and copyright holder. document. In program source code, tags reference syntactic elements of the program: functions, subroutines, data types, macros, etc. In a document, tags reference chapters, sections, appendices, etc. Each -tag specifies the file name on which the corresponding subunit is +tag specifies the name of the file where the corresponding subunit is defined, and the position of the subunit's definition in that file. A @dfn{tags table} records the tags extracted by scanning the source code of a certain program or a certain document. Tags extracted from -generated files reference subunits in the original files, rather than -the generated files that were scanned during tag extraction. Examples -of generated files include C files generated from Cweb source files, -from a Yacc parser, or from Lex scanner definitions; @file{.i} -preprocessed C files; and Fortran files produced by preprocessing -@file{.fpp} source files. - - To produce tags tables, you use the @samp{etags} command, submitting -it a document or the source code of a program. @samp{etags} writes -the tags to files called @dfn{tags table files}, or @dfn{tags file} in -short. The conventional name for a tags file is @file{TAGS}. +generated files reference the original files, rather than the +generated files that were scanned during tag extraction. Examples of +generated files include C files generated from Cweb source files, from +a Yacc parser, or from Lex scanner definitions; @file{.i} preprocessed +C files; and Fortran files produced by preprocessing @file{.fpp} +source files. + + To produce a tags table, you use the @samp{etags} command, +submitting it a document or the source code of a program. +@samp{etags} writes the tags to a @dfn{tags table file}, or @dfn{tags +file} in short. The conventional name for a tags file is @file{TAGS}. Emacs uses the information recorded in tags tables in commands that search or replace through multiple source files: these commands use -- 2.39.5