xemacs-beta: man/xemacs/programs.texi comparison

comparison man/xemacs/programs.texi @ 412:697ef44129c6 r21-2-14

Import from CVS: tag r21-2-14

author	cvs
date	Mon, 13 Aug 2007 11:20:41 +0200
parents	de805c49cfc1
children	11054d720c21

comparison

equal deleted inserted replaced

-:12e008d41344
+:697ef44129c6
 There are editing commands to operate on them.
 * Defuns::              Each program is made up of separate functions.
 There are editing commands to operate on them.
 * Grinding::            Adjusting indentation to show the nesting.
 * Matching::            Insertion of a close-delimiter flashes matching open.
-* Comments::            Inserting, filling and aligning comments.
+* Comments::            Inserting, illing and aligning comments.
 * Balanced Editing::    Inserting two matching parentheses at once, etc.
 * Lisp Completion::     Completion on symbol names in Lisp code.
 * Documentation::       Getting documentation of functions you plan to call.
 * Change Log::          Maintaining a change history for your program.
 * Tags::                Go direct to any function in your program in one
 indentation is computed by @kbd{C-M-q}; if the value is a number,
 @kbd{C-M-q} need not recalculate indentation for the following lines
 until the end of the list.
 @end table
-@node C Indent,  , Lisp Indent, Grinding
+@node C Indent,, Lisp Indent, Grinding
 @subsection Customizing C Indentation
 Two variables control which commands perform C indentation and when.
 @vindex c-auto-newline
 @kindex M-(
 @kindex M-)
 @findex insert-parentheses
 @findex move-over-close-and-reindent
 The commands @kbd{M-(} (@code{insert-parentheses}) and @kbd{M-)}
-(@code{move-over-close-and-reindent}) are designed to facilitate a style of
+(@code{move-over-close-@*and-reindent}) are designed to facilitate a style of
 editing which keeps parentheses balanced at all times.  @kbd{M-(} inserts a
 pair of parentheses, either together as in @samp{()}, or, if given an
 argument, around the next several sexps, and leaves point after the open
 parenthesis.  Instead of typing @kbd{( F O O )}, you can type @kbd{M-( F O
 O}, which has the same effect except for leaving the cursor before the
 A @dfn{tags table} is a description of how a multi-file program is
 broken up into files.  It lists the names of the component files and the
 names and positions of the functions (or other named subunits) in each
 file.  Grouping the related files makes it possible to search or replace
 through all the files with one command.  Recording the function names
-and positions makes possible the @kbd{M-.} command which finds the
+and positions makes possible the @kbd{M-.}  command which finds the
 definition of a function by looking up which of the files it is in.
 Tags tables are stored in files called @dfn{tags table files}.  The
 conventional name for a tags table file is @file{TAGS}.
 normally include all functions and subroutines, and may also include
 global variables, data types, and anything else convenient.  Each name
 recorded is called a @dfn{tag}.
 @menu
 * Tag Syntax::		Tag syntax for various types of code and text files.
 * Create Tags Table::	Creating a tags table with @code{etags}.
-* Etags Regexps::       Create arbitrary tags using regular expressions.
 * Select Tags Table::	How to visit a tags table.
 * Find Tag::		Commands to find the definition of a specific tag.
 * Tags Search::		Using a tags table for searching and replacing.
 * List Tags::		Listing and finding tags defined in a file.
 @end menu
-@node Tag Syntax, Create Tags Table, Tags, Tags
+@node Tag Syntax
 @subsection Source File Tag Syntax
 Here is how tag syntax is defined for the most popular languages:
 @itemize @bullet
 @item
 In C code, any C function or typedef is a tag, and so are definitions of
-@code{struct}, @code{union} and @code{enum}.  You can tag function
+@code{struct}, @code{union} and @code{enum}.  @code{#define} macro
-declarations and external variables in addition to function definitions
+definitions and @code{enum} constants are also tags, unless you specify
-by giving the @samp{--declarations} option to @code{etags}.
+@samp{--no-defines} when making the tags table.  Similarly, global
-@code{#define} macro definitions and @code{enum} constants are also
+variables are tags, unless you specify @samp{--no-globals}.  Use of
-tags, unless you specify @samp{--no-defines} when making the tags table.
+@samp{--no-globals} and @samp{--no-defines} can make the tags table file
-Similarly, global variables are tags, unless you specify
+much smaller.
-@samp{--no-globals}.  Use of @samp{--no-globals} and @samp{--no-defines}
-can make the tags table file much smaller.
 @item
 In C++ code, in addition to all the tag constructs of C code, member
 functions are also recognized, and optionally member variables if you
 use the @samp{--members} option.  Tags for variables and functions in
 classes are named @samp{@var{class}::@var{variable}} and
-@samp{@var{class}::@var{function}}.  @code{operator} functions tags are
+@samp{@var{class}::@var{function}}.
-named, for example @samp{operator+}.
 @item
 In Java code, tags include all the constructs recognized in C++, plus
-the @code{interface}, @code{extends} and @code{implements} constructs.
+the @code{extends} and @code{implements} constructs.  Tags for variables
-Tags for variables and functions in classes are named
+and functions in classes are named @samp{@var{class}.@var{variable}} and
-@samp{@var{class}.@var{variable}} and @samp{@var{class}.@var{function}}.
+@samp{@var{class}.@var{function}}.
 @item
 In La@TeX{} text, the argument of any of the commands @code{\chapter},
 @code{\section}, @code{\subsection}, @code{\subsubsection},
 @code{\eqno}, @code{\label}, @code{\ref}, @code{\cite}, @code{\bibitem},
 tag.@refill
 Other commands can make tags as well, if you specify them in the
 environment variable @code{TEXTAGS} before invoking @code{etags}.  The
 value of this environment variable should be a colon-separated list of
-command names.  For example,
+commands names.  For example,
 @example
 TEXTAGS="def:newcommand:newenvironment"
 export TEXTAGS
 @end example
 @end itemize
 Several other languages are also supported:
 @itemize @bullet
-@item
-In Ada code, functions, procedures, packages, tasks, and types are
-tags.  Use the @samp{--packages-only} option to create tags for packages
-only.
 @item
 In assembler code, labels appearing at the beginning of a line,
 followed by a colon, are tags.
 @item
 In Bison or Yacc input files, each rule defines as a tag the nonterminal
 it constructs.  The portions of the file that contain C code are parsed
 as C code.
 @item
-In Cobol code, tags are paragraph names; that is, any word starting in
+In Cobol code, paragraphs names are the tags, i.e. any word starting in
-column 8 and followed by a period.
+column 8 and followed by a full stop.
 @item
 In Erlang code, the tags are the functions, records, and macros defined
 in the file.
 @item
-In Fortran code, functions, subroutines and blockdata are tags.
+In Fortran code, functions and subroutines are tags.
 @item
 In Objective C code, tags include Objective C definitions for classes,
-class categories, methods, and protocols.
+class categories, methods and protocols.
 @item
 In Pascal code, the tags are the functions and procedures defined in
 the file.
 @item
-In Perl code, the tags are the procedures defined by the @code{sub},
+In Perl code, the tags are the procedures defined by the @code{sub}
-@code{my} and @code{local} keywords.  Use @samp{--globals} if you want
+keyword.
-to tag global variables.
 @item
 In Postscript code, the tags are the functions.
 @item
 In Prolog code, a tag name appears at the left margin.
-@item
-In Python code, @code{def} or @code{class} at the beginning of a line
-generate a tag.
 @end itemize
-You can also generate tags based on regexp matching
+You can also generate tags based on regexp matching (@pxref{Create
-(@pxref{Etags Regexps}) to handle other formats and languages.
+Tags Table}) to handle other formats and languages.
-@node Create Tags Table, Etags Regexps, Tag Syntax, Tags
+@node Create Tags Table
 @subsection Creating Tags Tables
 @cindex @code{etags} program
 The @code{etags} program is used to create a tags table file.  It knows
 the syntax of several languages, as described in
 @example
 etags @var{inputfiles}@dots{}
 @end example
 @noindent
-The @code{etags} program reads the specified files, and writes a tags
+The @code{etags} program reads the specified files, and writes a tags table
-table named @file{TAGS} in the current working directory.  You can
+named @file{TAGS} in the current working directory.  @code{etags}
-intermix compressed and plain text source file names.  @code{etags}
+recognizes the language used in an input file based on its file name and
-knows about the most common compression formats, and does the right
+contents.  You can specify the language with the
-thing.  So you can compress all your source files and have @code{etags}
-look for compressed versions of its file name arguments, if it does not
-find uncompressed versions.  Under MS-DOS, @code{etags} also looks for
-file names like @samp{mycode.cgz} if it is given @samp{mycode.c} on the
-command line and @samp{mycode.c} does not exist.
-@code{etags} recognizes the language used in an input file based on
-its file name and contents.  You can specify the language with the
 @samp{--language=@var{name}} option, described below.
 If the tags table data become outdated due to changes in the files
 described in the table, the way to update the tags table is the same way it
 was made in the first place.  It is not necessary to do this often.
 If you specify absolute file names as arguments to @code{etags}, then
 the tags file will contain absolute file names.  This way, the tags file
 will still refer to the same files even if you move it, as long as the
 source files remain in the same place.  Absolute file names start with
-@samp{/}, or with @samp{@var{device}:/} on MS-DOS and MS-Windows.
+@samp{/}, or with @samp{@var{device}:/} on MS-DOS and Windows.
 When you want to make a tags table from a great number of files, you
 may have problems listing them on the command line, because some systems
 have a limit on its length.  The simplest way to circumvent this limit
 is to tell @code{etags} to read the file names from its standard input,
 by typing a dash in place of the file names, like this:
-@smallexample
+@example
 find . -name "*.[chCH]" -print | etags -
-@end smallexample
+@end example
 Use the option @samp{--language=@var{name}} to specify the language
 explicitly.  You can intermix these options with file names; each one
 applies to the file names that follow it.  Specify
 @samp{--language=auto} to tell @code{etags} to resume guessing the
 language from the file names and file contents.  Specify
 @samp{--language=none} to turn off language-specific processing
-entirely; then @code{etags} recognizes tags by regexp matching alone
+entirely; then @code{etags} recognizes tags by regexp matching alone.
-(@pxref{Etags Regexps}).
+@samp{etags --help} prints the list of the languages @code{etags} knows,
+and the file name rules for guessing the language.
-@samp{etags --help} prints the list of the languages @code{etags}
-knows, and the file name rules for guessing the language. It also prints
-a list of all the available @code{etags} options, together with a short
-explanation.
-@node Etags Regexps, Select Tags Table, Create Tags Table, Tags
-@subsection Etags Regexps
 The @samp{--regex} option provides a general way of recognizing tags
 based on regexp matching.  You can freely intermix it with file names.
 Each @samp{--regex} option adds to the preceding ones, and applies only
 to the following files.  The syntax is:
-@smallexample
+@example
 --regex=/@var{tagregexp}[/@var{nameregexp}]/
-@end smallexample
+@end example
 @noindent
 where @var{tagregexp} is used to match the lines to tag.  It is always
 anchored, that is, it behaves as if preceded by @samp{^}.  If you want
 to account for indentation, just match any initial number of blanks by
 @samp{\@{@var{m},@var{n}\@}}, and its meaning is to match the preceding
 expression at least @var{m} times and up to @var{n} times.
 You should not match more characters with @var{tagregexp} than that
 needed to recognize what you want to tag.  If the match is such that
-more characters than needed are unavoidably matched by @var{tagregexp}
+more characters than needed are unavoidably matched by @var{tagregexp},
-(as will usually be the case), you should add a @var{nameregexp}, to
+you may find useful to add a @var{nameregexp}, in order to narrow the tag
-pick out just the tag.  This will enable Emacs to find tags more
+scope.  You can find some examples below.
-accurately and to do completion on tag names more reliably.  You can
-find some examples below.
-The option @samp{--ignore-case-regex} (or @samp{-c}) is like
-@samp{--regex}, except that the regular expression provided will be
-matched without regard to case, which is appropriate for various
-programming languages.
 The @samp{-R} option deletes all the regexps defined with
 @samp{--regex} options.  It applies to the file names following it, as
 you can see from the following example:
-@smallexample
+@example
 etags --regex=/@var{reg1}/ voo.doo --regex=/@var{reg2}/ \
 bar.ber -R --lang=lisp los.er
-@end smallexample
+@end example
 @noindent
 Here @code{etags} chooses the parsing language for @file{voo.doo} and
 @file{bar.ber} according to their contents.  @code{etags} also uses
 @var{reg1} to recognize additional tags in @file{voo.doo}, and both
 @var{reg1} and @var{reg2} to recognize additional tags in
 @file{bar.ber}.  @code{etags} uses the Lisp tags rules, and no regexp
 matching, to recognize tags in @file{los.er}.
-A regular expression can be bound to a given language, by prepending
-it with @samp{@{lang@}}.  When you do this, @code{etags} will use the
-regular expression only for files of that language.  @samp{etags --help}
-prints the list of languages recognised by @code{etags}.  The following
-example tags the @code{DEFVAR} macros in the Emacs source files.
-@code{etags} applies this regular expression to C files only:
-@smallexample
---regex='@{c@}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/'
-@end smallexample
-@noindent
-This feature is particularly useful when storing a list of regular
-expressions in a file.  The following option syntax instructs
-@code{etags} to read two files of regular expressions.  The regular
-expressions contained in the second file are matched without regard to
-case.
-@smallexample
---regex=@@first-file --ignore-case-regex=@@second-file
-@end smallexample
-@noindent
-A regex file contains one regular expressions per line.  Empty lines,
-and lines beginning with space or tab are ignored.  When the first
-character in a line is @samp{@@}, @code{etags} assumes that the rest of
-the line is the name of a file of regular expressions.  This means that
-such files can be nested.  All the other lines are taken to be regular
-expressions.  For example, one can create a file called
-@samp{emacs.tags} with the following contents (the first line in the
-file is a comment):
-@smallexample
--- This is for GNU Emacs source files
-@{c@}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/\1/
-@end smallexample
-@noindent
-and then use it like this:
-@smallexample
-etags --regex=@@emacs.tags *.[ch] */*.[ch]
-@end smallexample
 Here are some more examples.  The regexps are quoted to protect them
 from shell interpretation.
-@itemize @bullet
-@item
-Tag Octave files:
-@smallexample
-etags --language=none \
---regex='/[ \t]*function.*=[ \t]*\([^ \t]*\)[ \t]*(/\1/' \
---regex='/###key \(.*\)/\1/' \
---regex='/[ \t]*global[ \t].*/' \
-*.m
-@end smallexample
 @noindent
-Note that tags are not generated for scripts so that you have to add a
+Tag the @code{DEFVAR} macros in the emacs source files:
-line by yourself of the form `###key <script-name>' if you want to jump
-to it.
+@example
+--regex='/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/'
-@item
+@end example
-Tag Tcl files:
+@noindent
-@smallexample
+Tag VHDL files (this example is a single long line, broken here for
-etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' *.tcl
+formatting reasons):
-@end smallexample
+@example
-@item
+--language=none
-Tag VHDL files:
+--regex='/[ \t]*\(ARCHITECTURE\|CONFIGURATION\) +[^ ]* +OF/'
-@smallexample
---language=none \
---regex='/[ \t]*\(ARCHITECTURE\|CONFIGURATION\) +[^ ]* +OF/' \
 --regex='/[ \t]*\(ATTRIBUTE\|ENTITY\|FUNCTION\|PACKAGE\
 \( BODY\)?\|PROCEDURE\|PROCESS\|TYPE\)[ \t]+\([^ \t(]+\)/\3/'
-@end smallexample
+@end example
-@end itemize
+@noindent
-@node Select Tags Table, Find Tag, Etags Regexps, Tags
+Tag TCL files (this last example shows the usage of a @var{nameregexp}):
+@example
+--lang=none --regex='/proc[ \t]+\([^ \t]+\)/\1/'
+@end example
+For a list of the other available @code{etags} options, execute
+@code{etags --help}.
+@node Select Tags Table, Find Tag, Create Tags Table, Tags
 @subsection Selecting a Tags Table
 @vindex tag-table-alist
 At any time Emacs has one @dfn{selected} tags table, and all the commands
 for working with tags tables use the selected one.  To select a tags table,
 For example:
 @example
 (setq tag-table-alist
-'(("/usr/src/public/perl/" . "/usr/src/public/perl/perl-3.0/")
+	'(("/usr/src/public/perl/" . "/usr/src/public/perl/perl-3.0/")
-("\\.el$" . "/usr/local/emacs/src/")
+	  ("\\.el$" . "/usr/local/emacs/src/")
-("/jbw/gnu/" . "/usr15/degree/stud/jbw/gnu/")
+	  ("/jbw/gnu/" . "/usr15/degree/stud/jbw/gnu/")
-("" . "/usr/local/emacs/src/")
+	  ("" . "/usr/local/emacs/src/")
-))
+	  ))
 @end example
 The example defines the tags table alist in the following way:
 @itemize @bullet
 @vindex tag-mark-stack-max
 @table @kbd
 @item tag-table-alist
 Controls which tables apply to which buffers.
 @item tags-file-name
 Stores a default tags table.
 @item tags-build-completion-table
 Controls completion behavior.
 @item buffer-tag-table
 Specifies a buffer-local table.
 @item make-tags-files-invisible
 Sets whether tags tables should be very hidden.
 @item tag-mark-stack-max
 Specifies how many tags-based hops to remember.
 @end table
 @kindex C-x 4 .
 @findex find-tag-other-window
 file in the tags table and prepare to advance sequentially by files.
 @item M-x next-file
 Visit the next file in the selected tags table.
 @end table
-@node List Tags,  , Tags Search, Tags
+@node List Tags,, Tags Search, Tags
 @subsection Tags Table Inquiries
 @table @kbd
 @item M-x list-tags
 Display a list of the tags defined in a specific program file.
 If you fail to follow these conventions, the indentation commands may
 indent some lines unaesthetically.  However, a correct Fortran program will
 retain its meaning when reindented even if the conventions are not
 followed.
-@node ForIndent Vars,  , ForIndent Conv, Fortran Indent
+@node ForIndent Vars,, ForIndent Conv, Fortran Indent
 @subsubsection Variables for Fortran Indentation
 @vindex fortran-do-indent
 @vindex fortran-if-indent
 @vindex fortran-continuation-indent
 For even more help, use @kbd{C-c C-w} (@code{fortran-window-create}), a
 command which splits the current window horizontally, resulting in a window 72
 columns wide.  When you edit in this window, you can immediately see
 when a line gets too wide to be correct Fortran.
-@node Fortran Abbrev,  , Fortran Columns, Fortran
+@node Fortran Abbrev,, Fortran Columns, Fortran
 @subsection Fortran Keyword Abbrevs
 Fortran mode provides many built-in abbrevs for common keywords and
 declarations.  These are the same sort of abbrevs that you can define
 yourself.  To use them, you must turn on Abbrev mode.  @pxref{Abbrevs}.
 automatically to @samp{continue}, provided Abbrev mode is enabled.@refill
 Type @samp{;?} or @samp{;C-h} to display a list of all built-in
 Fortran abbrevs and what they stand for.
-@node Asm Mode,  , Fortran, Programs
+@node Asm Mode,, Fortran, Programs
 @section Asm Mode
 @cindex Asm mode
 Asm mode is a major mode for editing files of assembler code.  It
 defines these commands:

Mercurial > hg > xemacs-beta

comparison man/xemacs/programs.texi @ 412:697ef44129c6 r21-2-14