aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2009-04-26 19:01:24 +0000
committerEli Zaretskii2009-04-26 19:01:24 +0000
commit6c4cfaf836b948efbffce349f5c20a0819d6bfdd (patch)
tree0784b451a9524ccbd758c668225dcf2798f01876
parent7be4f7c06d561e48c9d6d4039bf9431de2158083 (diff)
downloademacs-6c4cfaf836b948efbffce349f5c20a0819d6bfdd.tar.gz
emacs-6c4cfaf836b948efbffce349f5c20a0819d6bfdd.zip
(Tags): Clarify the text some more.
-rw-r--r--doc/emacs/maintaining.texi24
1 files 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.
1484document. In program source code, tags reference syntactic elements 1484document. In program source code, tags reference syntactic elements
1485of the program: functions, subroutines, data types, macros, etc. In a 1485of the program: functions, subroutines, data types, macros, etc. In a
1486document, tags reference chapters, sections, appendices, etc. Each 1486document, tags reference chapters, sections, appendices, etc. Each
1487tag specifies the file name on which the corresponding subunit is 1487tag specifies the name of the file where the corresponding subunit is
1488defined, and the position of the subunit's definition in that file. 1488defined, and the position of the subunit's definition in that file.
1489 1489
1490 A @dfn{tags table} records the tags extracted by scanning the source 1490 A @dfn{tags table} records the tags extracted by scanning the source
1491code of a certain program or a certain document. Tags extracted from 1491code of a certain program or a certain document. Tags extracted from
1492generated files reference subunits in the original files, rather than 1492generated files reference the original files, rather than the
1493the generated files that were scanned during tag extraction. Examples 1493generated files that were scanned during tag extraction. Examples of
1494of generated files include C files generated from Cweb source files, 1494generated files include C files generated from Cweb source files, from
1495from a Yacc parser, or from Lex scanner definitions; @file{.i} 1495a Yacc parser, or from Lex scanner definitions; @file{.i} preprocessed
1496preprocessed C files; and Fortran files produced by preprocessing 1496C files; and Fortran files produced by preprocessing @file{.fpp}
1497@file{.fpp} source files. 1497source files.
1498 1498
1499 To produce tags tables, you use the @samp{etags} command, submitting 1499 To produce a tags table, you use the @samp{etags} command,
1500it a document or the source code of a program. @samp{etags} writes 1500submitting it a document or the source code of a program.
1501the tags to files called @dfn{tags table files}, or @dfn{tags file} in 1501@samp{etags} writes the tags to a @dfn{tags table file}, or @dfn{tags
1502short. The conventional name for a tags file is @file{TAGS}. 1502file} in short. The conventional name for a tags file is @file{TAGS}.
1503 1503
1504 Emacs uses the information recorded in tags tables in commands that 1504 Emacs uses the information recorded in tags tables in commands that
1505search or replace through multiple source files: these commands use 1505search or replace through multiple source files: these commands use