comparison man/programs.texi @ 30793:ea6025935730

(Authors): New node.
author Eli Zaretskii <eliz@gnu.org>
date Tue, 15 Aug 2000 08:23:20 +0000
parents 9c402b90b24d
children 6c6b0162bae2
comparison
equal deleted inserted replaced
30792:97c0caec0a32 30793:ea6025935730
66 * Symbol Completion:: Completion on symbol names of your program or language. 66 * Symbol Completion:: Completion on symbol names of your program or language.
67 * Which Function:: Which Function mode shows which function you are in. 67 * Which Function:: Which Function mode shows which function you are in.
68 * Hideshow:: Displaying blocks selectively. 68 * Hideshow:: Displaying blocks selectively.
69 * Documentation:: Getting documentation of functions you plan to call. 69 * Documentation:: Getting documentation of functions you plan to call.
70 * Change Log:: Maintaining a change history for your program. 70 * Change Log:: Maintaining a change history for your program.
71 * Authors:: Maintaining an @file{AUTHORS} file.
71 * Tags:: Go direct to any function in your program in one 72 * Tags:: Go direct to any function in your program in one
72 command. Tags remembers which file it is in. 73 command. Tags remembers which file it is in.
73 * Imenu:: Making buffer indexes as menus. 74 * Imenu:: Making buffer indexes as menus.
74 * Emerge:: A convenient way of merging two versions of a program. 75 * Emerge:: A convenient way of merging two versions of a program.
75 * C Modes:: Special commands of C, C++, Objective-C, 76 * C Modes:: Special commands of C, C++, Objective-C,
1753 of entries with either the current or old-style date formats. 1754 of entries with either the current or old-style date formats.
1754 1755
1755 Version control systems are another way to keep track of changes in your 1756 Version control systems are another way to keep track of changes in your
1756 program and keep a change log. @xref{Log Buffer}. 1757 program and keep a change log. @xref{Log Buffer}.
1757 1758
1759 @node Authors
1760 @section @file{AUTHORS} files
1761 @cindex @file{AUTHORS} file
1762
1763 Programs which have many contributors usually include a file named
1764 @file{AUTHORS} in their distribution, which lists the individual
1765 contributions. Emacs has a special command for maintaining the
1766 @file{AUTHORS} file that is part of the Emacs distribution.
1767
1768 @findex authors
1769 The @kbd{M-x authors} command prompts for the name of the root of the
1770 Emacs source directory. It then scans @file{ChageLog} files and Lisp
1771 source files under that directory for information about authors of
1772 individual packages and people who made changes in source files, and
1773 puts the information it gleans into a buffer named @samp{*Authors*}.
1774 You can then edit the contents of that buffer and merge it with the
1775 exisiting @file{AUTHORS} file.
1776
1758 @node Tags 1777 @node Tags
1759 @section Tags Tables 1778 @section Tags Tables
1760 @cindex tags table 1779 @cindex tags table
1761 1780
1762 A @dfn{tags table} is a description of how a multi-file program is 1781 A @dfn{tags table} is a description of how a multi-file program is