Commit | Line | Data |
---|---|---|
f00366c2 RS |
1 | @c This is part of the Emacs manual. |
2 | @c Copyright (C) 1985,86,87,93,94,95,97,99,00,2001 Free Software Foundation, Inc. | |
3 | @c See file emacs.texi for copying conditions. | |
4 | @node Maintaining, Abbrevs, Building, Top | |
5 | @chapter Maintaining Programs | |
6 | @cindex Lisp editing | |
7 | @cindex C editing | |
8 | @cindex program editing | |
9 | ||
10 | This chapter describes Emacs features for maintaining programs. The | |
11 | version control features,described in the chapter on files | |
12 | (@pxref{Version Control}), are also useful particularly for this | |
13 | purpose. | |
14 | ||
15 | @menu | |
16 | * Change Log:: Maintaining a change history for your program. | |
17 | * Authors:: Maintaining an @file{AUTHORS} file. | |
18 | * Tags:: Go direct to any function in your program in one | |
19 | command. Tags remembers which file it is in. | |
20 | * Emerge:: A convenient way of merging two versions of a program. | |
21 | @end menu | |
22 | ||
23 | @node Change Log | |
24 | @section Change Logs | |
25 | ||
26 | @cindex change log | |
27 | @kindex C-x 4 a | |
28 | @findex add-change-log-entry-other-window | |
29 | The Emacs command @kbd{C-x 4 a} adds a new entry to the change log | |
30 | file for the file you are editing | |
31 | (@code{add-change-log-entry-other-window}). If that file is actually | |
32 | a backup file, it makes an entry appropriate for the file's | |
33 | parent---that is useful for making log entries for functions that | |
34 | have been deleted in the current version. | |
35 | ||
36 | A change log file contains a chronological record of when and why you | |
37 | have changed a program, consisting of a sequence of entries describing | |
38 | individual changes. Normally it is kept in a file called | |
39 | @file{ChangeLog} in the same directory as the file you are editing, or | |
40 | one of its parent directories. A single @file{ChangeLog} file can | |
41 | record changes for all the files in its directory and all its | |
42 | subdirectories. | |
43 | ||
44 | A change log entry starts with a header line that contains the | |
45 | current date, your name, and your email address (taken from the | |
46 | variable @code{user-mail-address}). Aside from these header lines, | |
47 | every line in the change log starts with a space or a tab. The bulk | |
48 | of the entry consists of @dfn{items}, each of which starts with a line | |
49 | starting with whitespace and a star. Here are two entries, both dated | |
50 | in May 1993, each with two items: | |
51 | ||
52 | @iftex | |
53 | @medbreak | |
54 | @end iftex | |
55 | @smallexample | |
56 | 1993-05-25 Richard Stallman <rms@@gnu.org> | |
57 | ||
58 | * man.el: Rename symbols `man-*' to `Man-*'. | |
59 | (manual-entry): Make prompt string clearer. | |
60 | ||
61 | * simple.el (blink-matching-paren-distance): | |
62 | Change default to 12,000. | |
63 | ||
64 | 1993-05-24 Richard Stallman <rms@@gnu.org> | |
65 | ||
66 | * vc.el (minor-mode-map-alist): Don't use it if it's void. | |
67 | (vc-cancel-version): Doc fix. | |
68 | @end smallexample | |
69 | ||
70 | One entry can describe several changes; each change should have its | |
71 | own item. Normally there should be a blank line between items. When | |
72 | items are related (parts of the same change, in different places), group | |
73 | them by leaving no blank line between them. The second entry above | |
74 | contains two items grouped in this way. | |
75 | ||
76 | @kbd{C-x 4 a} visits the change log file and creates a new entry | |
77 | unless the most recent entry is for today's date and your name. It | |
78 | also creates a new item for the current file. For many languages, it | |
79 | can even guess the name of the function or other object that was | |
80 | changed. | |
81 | ||
82 | @vindex add-log-keep-changes-together | |
83 | When the option @code{add-log-keep-changes-together} is | |
84 | non-@code{nil}, @kbd{C-x 4 a} adds to any existing entry for the file | |
85 | rather than starting a new entry. | |
86 | ||
87 | @vindex change-log-version-info-enabled | |
88 | @vindex change-log-version-number-regexp-list | |
89 | @cindex file version in change log entries | |
90 | If the value of the variable @code{change-log-version-info-enabled} | |
91 | is non-@code{nil}, @kbd{C-x 4 a} adds the file's version number to the | |
92 | change log entry. It finds the version number by searching the first | |
93 | ten percent of the file, using regular expressions from the variable | |
94 | @code{change-log-version-number-regexp-list}. | |
95 | ||
96 | @cindex Change Log mode | |
97 | @findex change-log-mode | |
98 | The change log file is visited in Change Log mode. In this major | |
99 | mode, each bunch of grouped items counts as one paragraph, and each | |
100 | entry is considered a page. This facilitates editing the entries. | |
101 | @kbd{C-j} and auto-fill indent each new line like the previous line; | |
102 | this is convenient for entering the contents of an entry. | |
103 | ||
104 | @findex change-log-merge | |
105 | You can use the command @kbd{M-x change-log-merge} to merge other | |
106 | log files into a buffer in Change Log Mode, preserving the date | |
107 | ordering of entries. | |
108 | ||
109 | @findex change-log-redate | |
110 | @cindex converting change log date style | |
111 | Versions of Emacs before 20.1 used a different format for the time of | |
112 | the change log entry: | |
113 | ||
114 | @smallexample | |
115 | Fri May 25 11:23:23 1993 Richard Stallman <rms@@gnu.org> | |
116 | @end smallexample | |
117 | ||
118 | @noindent | |
119 | The @kbd{M-x change-log-redate} command converts all the old-style | |
120 | date entries in the change log file visited in the current buffer to | |
121 | the new format, to make the file uniform in style. This is handy when | |
122 | entries are contributed by many different people, some of whom use old | |
123 | versions of Emacs. | |
124 | ||
125 | Version control systems are another way to keep track of changes in your | |
126 | program and keep a change log. @xref{Log Buffer}. | |
127 | ||
128 | @node Authors | |
129 | @section @file{AUTHORS} files | |
130 | @cindex @file{AUTHORS} file | |
131 | ||
132 | Programs which have many contributors usually include a file named | |
133 | @file{AUTHORS} in their distribution, which lists the individual | |
134 | contributions. Emacs has a special command for maintaining the | |
135 | @file{AUTHORS} file that is part of the Emacs distribution. | |
136 | ||
137 | @findex authors | |
138 | The @kbd{M-x authors} command prompts for the name of the root of the | |
139 | Emacs source directory. It then scans @file{ChageLog} files and Lisp | |
140 | source files under that directory for information about authors of | |
141 | individual packages and people who made changes in source files, and | |
142 | puts the information it gleans into a buffer named @samp{*Authors*}. | |
143 | You can then edit the contents of that buffer and merge it with the | |
144 | exisiting @file{AUTHORS} file. | |
145 | ||
146 | Do not assume that this command finds all the contributors; don't | |
147 | assume that a person not listed in the output was not a contributor. | |
148 | If you merged in someone's contribution and did not put his name | |
149 | in the change log, he won't show up in @kbd{M-x authors} either. | |
150 | ||
151 | @node Tags | |
152 | @section Tags Tables | |
153 | @cindex tags table | |
154 | ||
155 | A @dfn{tags table} is a description of how a multi-file program is | |
156 | broken up into files. It lists the names of the component files and the | |
157 | names and positions of the functions (or other named subunits) in each | |
158 | file. Grouping the related files makes it possible to search or replace | |
159 | through all the files with one command. Recording the function names | |
160 | and positions makes possible the @kbd{M-.} command which finds the | |
161 | definition of a function by looking up which of the files it is in. | |
162 | ||
163 | Tags tables are stored in files called @dfn{tags table files}. The | |
164 | conventional name for a tags table file is @file{TAGS}. | |
165 | ||
166 | Each entry in the tags table records the name of one tag, the name of the | |
167 | file that the tag is defined in (implicitly), and the position in that file | |
168 | of the tag's definition. | |
169 | ||
170 | Just what names from the described files are recorded in the tags table | |
171 | depends on the programming language of the described file. They | |
172 | normally include all file names, functions and subroutines, and may | |
173 | also include global variables, data types, and anything else | |
174 | convenient. Each name recorded is called a @dfn{tag}. | |
175 | ||
176 | @cindex C++ class browser, tags | |
177 | @cindex tags, C++ | |
178 | @cindex class browser, C++ | |
179 | @cindex Ebrowse | |
180 | See also the Ebrowse facility, which is tailored for C++. | |
181 | @xref{Top,, Ebrowse, ebrowse, Ebrowse User's Manual}. | |
182 | ||
183 | @menu | |
184 | * Tag Syntax:: Tag syntax for various types of code and text files. | |
185 | * Create Tags Table:: Creating a tags table with @code{etags}. | |
186 | * Etags Regexps:: Create arbitrary tags using regular expressions. | |
187 | * Select Tags Table:: How to visit a tags table. | |
188 | * Find Tag:: Commands to find the definition of a specific tag. | |
189 | * Tags Search:: Using a tags table for searching and replacing. | |
190 | * List Tags:: Listing and finding tags defined in a file. | |
191 | @end menu | |
192 | ||
193 | @node Tag Syntax | |
194 | @subsection Source File Tag Syntax | |
195 | ||
196 | Here is how tag syntax is defined for the most popular languages: | |
197 | ||
198 | @itemize @bullet | |
199 | @item | |
200 | In C code, any C function or typedef is a tag, and so are definitions of | |
201 | @code{struct}, @code{union} and @code{enum}. | |
202 | @code{#define} macro definitions and @code{enum} constants are also | |
203 | tags, unless you specify @samp{--no-defines} when making the tags table. | |
204 | Similarly, global variables are tags, unless you specify | |
205 | @samp{--no-globals}. Use of @samp{--no-globals} and @samp{--no-defines} | |
206 | can make the tags table file much smaller. | |
207 | ||
208 | You can tag function declarations and external variables in addition | |
209 | to function definitions by giving the @samp{--declarations} option to | |
210 | @code{etags}. | |
211 | ||
212 | @item | |
213 | In C++ code, in addition to all the tag constructs of C code, member | |
214 | functions are also recognized, and optionally member variables if you | |
215 | use the @samp{--members} option. Tags for variables and functions in | |
216 | classes are named @samp{@var{class}::@var{variable}} and | |
217 | @samp{@var{class}::@var{function}}. @code{operator} definitions have | |
218 | tag names like @samp{operator+}. | |
219 | ||
220 | @item | |
221 | In Java code, tags include all the constructs recognized in C++, plus | |
222 | the @code{interface}, @code{extends} and @code{implements} constructs. | |
223 | Tags for variables and functions in classes are named | |
224 | @samp{@var{class}.@var{variable}} and @samp{@var{class}.@var{function}}. | |
225 | ||
226 | @item | |
227 | In La@TeX{} text, the argument of any of the commands @code{\chapter}, | |
228 | @code{\section}, @code{\subsection}, @code{\subsubsection}, | |
229 | @code{\eqno}, @code{\label}, @code{\ref}, @code{\cite}, @code{\bibitem}, | |
230 | @code{\part}, @code{\appendix}, @code{\entry}, or @code{\index}, is a | |
231 | tag.@refill | |
232 | ||
233 | Other commands can make tags as well, if you specify them in the | |
234 | environment variable @env{TEXTAGS} before invoking @code{etags}. The | |
235 | value of this environment variable should be a colon-separated list of | |
236 | command names. For example, | |
237 | ||
238 | @example | |
239 | TEXTAGS="def:newcommand:newenvironment" | |
240 | export TEXTAGS | |
241 | @end example | |
242 | ||
243 | @noindent | |
244 | specifies (using Bourne shell syntax) that the commands @samp{\def}, | |
245 | @samp{\newcommand} and @samp{\newenvironment} also define tags. | |
246 | ||
247 | @item | |
248 | In Lisp code, any function defined with @code{defun}, any variable | |
249 | defined with @code{defvar} or @code{defconst}, and in general the first | |
250 | argument of any expression that starts with @samp{(def} in column zero, is | |
251 | a tag. | |
252 | ||
253 | @item | |
254 | In Scheme code, tags include anything defined with @code{def} or with a | |
255 | construct whose name starts with @samp{def}. They also include variables | |
256 | set with @code{set!} at top level in the file. | |
257 | @end itemize | |
258 | ||
259 | Several other languages are also supported: | |
260 | ||
261 | @itemize @bullet | |
262 | ||
263 | @item | |
264 | In Ada code, functions, procedures, packages, tasks, and types are | |
265 | tags. Use the @samp{--packages-only} option to create tags for | |
266 | packages only. | |
267 | ||
268 | In Ada, the same name can be used for different kinds of entity | |
269 | (e.g.@:, for a procedure and for a function). Also, for things like | |
270 | packages, procedures and functions, there is the spec (i.e.@: the | |
271 | interface) and the body (i.e.@: the implementation). To make it | |
272 | easier to pick the definition you want, Ada tag name have suffixes | |
273 | indicating the type of entity: | |
274 | ||
275 | @table @samp | |
276 | @item /b | |
277 | package body. | |
278 | @item /f | |
279 | function. | |
280 | @item /k | |
281 | task. | |
282 | @item /p | |
283 | procedure. | |
284 | @item /s | |
285 | package spec. | |
286 | @item /t | |
287 | type. | |
288 | @end table | |
289 | ||
290 | Thus, @kbd{M-x find-tag @key{RET} bidule/b @key{RET}} will go | |
291 | directly to the body of the package @code{bidule}, while @kbd{M-x | |
292 | find-tag @key{RET} bidule @key{RET}} will just search for any tag | |
293 | @code{bidule}. | |
294 | ||
295 | @item | |
296 | In assembler code, labels appearing at the beginning of a line, | |
297 | followed by a colon, are tags. | |
298 | ||
299 | @item | |
300 | In Bison or Yacc input files, each rule defines as a tag the nonterminal | |
301 | it constructs. The portions of the file that contain C code are parsed | |
302 | as C code. | |
303 | ||
304 | @item | |
305 | In Cobol code, tags are paragraph names; that is, any word starting in | |
306 | column 8 and followed by a period. | |
307 | ||
308 | @item | |
309 | In Erlang code, the tags are the functions, records, and macros defined | |
310 | in the file. | |
311 | ||
312 | @item | |
313 | In Fortran code, functions, subroutines and blockdata are tags. | |
314 | ||
315 | @item | |
316 | In makefiles, targets are tags. | |
317 | ||
318 | @item | |
319 | In Objective C code, tags include Objective C definitions for classes, | |
320 | class categories, methods, and protocols. | |
321 | ||
322 | @item | |
323 | In Pascal code, the tags are the functions and procedures defined in | |
324 | the file. | |
325 | ||
326 | @item | |
327 | In Perl code, the tags are the procedures defined by the @code{sub}, | |
328 | @code{my} and @code{local} keywords. Use @samp{--globals} if you want | |
329 | to tag global variables. | |
330 | ||
331 | @item | |
332 | In PostScript code, the tags are the functions. | |
333 | ||
334 | @item | |
335 | In Prolog code, a tag name appears at the left margin. | |
336 | ||
337 | @item | |
338 | In Python code, @code{def} or @code{class} at the beginning of a line | |
339 | generate a tag. | |
340 | @end itemize | |
341 | ||
342 | You can also generate tags based on regexp matching (@pxref{Etags | |
343 | Regexps}) to handle other formats and languages. | |
344 | ||
345 | @node Create Tags Table | |
346 | @subsection Creating Tags Tables | |
347 | @cindex @code{etags} program | |
348 | ||
349 | The @code{etags} program is used to create a tags table file. It knows | |
350 | the syntax of several languages, as described in | |
351 | @iftex | |
352 | the previous section. | |
353 | @end iftex | |
354 | @ifinfo | |
355 | @ref{Tag Syntax}. | |
356 | @end ifinfo | |
357 | Here is how to run @code{etags}: | |
358 | ||
359 | @example | |
360 | etags @var{inputfiles}@dots{} | |
361 | @end example | |
362 | ||
363 | @noindent | |
364 | The @code{etags} program reads the specified files, and writes a tags | |
365 | table named @file{TAGS} in the current working directory. | |
366 | ||
367 | If the specified files don't exist, @code{etags} looks for | |
368 | compressed versions of them and uncompresses them to read them. Under | |
369 | MS-DOS, @code{etags} also looks for file names like @file{mycode.cgz} | |
370 | if it is given @samp{mycode.c} on the command line and @file{mycode.c} | |
371 | does not exist. | |
372 | ||
373 | @code{etags} recognizes the language used in an input file based on | |
374 | its file name and contents. You can specify the language with the | |
375 | @samp{--language=@var{name}} option, described below. | |
376 | ||
377 | If the tags table data become outdated due to changes in the files | |
378 | described in the table, the way to update the tags table is the same | |
379 | way it was made in the first place. But it is not necessary to do | |
380 | this very often. | |
381 | ||
382 | If the tags table fails to record a tag, or records it for the wrong | |
383 | file, then Emacs cannot possibly find its definition. However, if the | |
384 | position recorded in the tags table becomes a little bit wrong (due to | |
385 | some editing in the file that the tag definition is in), the only | |
386 | consequence is a slight delay in finding the tag. Even if the stored | |
387 | position is very wrong, Emacs will still find the tag, but it must | |
388 | search the entire file for it. | |
389 | ||
390 | So you should update a tags table when you define new tags that you want | |
391 | to have listed, or when you move tag definitions from one file to another, | |
392 | or when changes become substantial. Normally there is no need to update | |
393 | the tags table after each edit, or even every day. | |
394 | ||
395 | One tags table can virtually include another. Specify the included | |
396 | tags file name with the @samp{--include=@var{file}} option when | |
397 | creating the file that is to include it. The latter file then acts as | |
398 | if it covered all the source files specified in the included file, as | |
399 | well as the files it directly contains. | |
400 | ||
401 | If you specify the source files with relative file names when you run | |
402 | @code{etags}, the tags file will contain file names relative to the | |
403 | directory where the tags file was initially written. This way, you can | |
404 | move an entire directory tree containing both the tags file and the | |
405 | source files, and the tags file will still refer correctly to the source | |
406 | files. | |
407 | ||
408 | If you specify absolute file names as arguments to @code{etags}, then | |
409 | the tags file will contain absolute file names. This way, the tags file | |
410 | will still refer to the same files even if you move it, as long as the | |
411 | source files remain in the same place. Absolute file names start with | |
412 | @samp{/}, or with @samp{@var{device}:/} on MS-DOS and MS-Windows. | |
413 | ||
414 | When you want to make a tags table from a great number of files, you | |
415 | may have problems listing them on the command line, because some systems | |
416 | have a limit on its length. The simplest way to circumvent this limit | |
417 | is to tell @code{etags} to read the file names from its standard input, | |
418 | by typing a dash in place of the file names, like this: | |
419 | ||
420 | @smallexample | |
421 | find . -name "*.[chCH]" -print | etags - | |
422 | @end smallexample | |
423 | ||
424 | Use the option @samp{--language=@var{name}} to specify the language | |
425 | explicitly. You can intermix these options with file names; each one | |
426 | applies to the file names that follow it. Specify | |
427 | @samp{--language=auto} to tell @code{etags} to resume guessing the | |
428 | language from the file names and file contents. Specify | |
429 | @samp{--language=none} to turn off language-specific processing | |
430 | entirely; then @code{etags} recognizes tags by regexp matching alone | |
431 | (@pxref{Etags Regexps}). | |
432 | ||
433 | @samp{etags --help} prints the list of the languages @code{etags} | |
434 | knows, and the file name rules for guessing the language. It also prints | |
435 | a list of all the available @code{etags} options, together with a short | |
436 | explanation. | |
437 | ||
438 | @node Etags Regexps | |
439 | @subsection Etags Regexps | |
440 | ||
441 | The @samp{--regex} option provides a general way of recognizing tags | |
442 | based on regexp matching. You can freely intermix it with file names. | |
443 | Each @samp{--regex} option adds to the preceding ones, and applies only | |
444 | to the following files. The syntax is: | |
445 | ||
446 | @smallexample | |
447 | --regex=/@var{tagregexp}[/@var{nameregexp}]/ | |
448 | @end smallexample | |
449 | ||
450 | @noindent | |
451 | where @var{tagregexp} is used to match the lines to tag. It is always | |
452 | anchored, that is, it behaves as if preceded by @samp{^}. If you want | |
453 | to account for indentation, just match any initial number of blanks by | |
454 | beginning your regular expression with @samp{[ \t]*}. In the regular | |
455 | expressions, @samp{\} quotes the next character, and @samp{\t} stands | |
456 | for the tab character. Note that @code{etags} does not handle the other | |
457 | C escape sequences for special characters. | |
458 | ||
459 | @cindex interval operator (in regexps) | |
460 | The syntax of regular expressions in @code{etags} is the same as in | |
461 | Emacs, augmented with the @dfn{interval operator}, which works as in | |
462 | @code{grep} and @code{ed}. The syntax of an interval operator is | |
463 | @samp{\@{@var{m},@var{n}\@}}, and its meaning is to match the preceding | |
464 | expression at least @var{m} times and up to @var{n} times. | |
465 | ||
466 | You should not match more characters with @var{tagregexp} than that | |
467 | needed to recognize what you want to tag. If the match is such that | |
468 | more characters than needed are unavoidably matched by @var{tagregexp} | |
469 | (as will usually be the case), you should add a @var{nameregexp}, to | |
470 | pick out just the tag. This will enable Emacs to find tags more | |
471 | accurately and to do completion on tag names more reliably. You can | |
472 | find some examples below. | |
473 | ||
474 | The option @samp{--ignore-case-regex} (or @samp{-c}) works like | |
475 | @samp{--regex}, except that matching ignores case. This is | |
476 | appropriate for certain programming languages. | |
477 | ||
478 | The @samp{-R} option deletes all the regexps defined with | |
479 | @samp{--regex} options. It applies to the file names following it, as | |
480 | you can see from the following example: | |
481 | ||
482 | @smallexample | |
483 | etags --regex=/@var{reg1}/ voo.doo --regex=/@var{reg2}/ \ | |
484 | bar.ber -R --lang=lisp los.er | |
485 | @end smallexample | |
486 | ||
487 | @noindent | |
488 | Here @code{etags} chooses the parsing language for @file{voo.doo} and | |
489 | @file{bar.ber} according to their contents. @code{etags} also uses | |
490 | @var{reg1} to recognize additional tags in @file{voo.doo}, and both | |
491 | @var{reg1} and @var{reg2} to recognize additional tags in | |
492 | @file{bar.ber}. @code{etags} uses the Lisp tags rules, and no regexp | |
493 | matching, to recognize tags in @file{los.er}. | |
494 | ||
495 | You can specify a regular expression for a particular language, by | |
496 | writing @samp{@{lang@}} in front of it. Then @code{etags} will use | |
497 | the regular expression only for files of that language. (@samp{etags | |
498 | --help} prints the list of languages recognised by @code{etags}.) The | |
499 | following example tags the @code{DEFVAR} macros in the Emacs source | |
500 | files, for the C language only: | |
501 | ||
502 | @smallexample | |
503 | --regex='@{c@}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/' | |
504 | @end smallexample | |
505 | ||
506 | @noindent | |
507 | This feature is particularly useful when you store a list of regular | |
508 | expressions in a file. The following option syntax instructs | |
509 | @code{etags} to read two files of regular expressions. The regular | |
510 | expressions contained in the second file are matched without regard to | |
511 | case. | |
512 | ||
513 | @smallexample | |
514 | --regex=@@first-file --ignore-case-regex=@@second-file | |
515 | @end smallexample | |
516 | ||
517 | @noindent | |
518 | A regex file contains one regular expressions per line. Empty lines, | |
519 | and lines beginning with space or tab are ignored. When the first | |
520 | character in a line is @samp{@@}, @code{etags} assumes that the rest | |
521 | of the line is the name of a file of regular expressions; thus, one | |
522 | such file can include another file. All the other lines are taken to | |
523 | be regular expressions. If the first non-whitespace text on the line | |
524 | is @samp{--}, that line is a comment. | |
525 | ||
526 | For example, one can create a file called @samp{emacs.tags} with the | |
527 | following contents: | |
528 | ||
529 | @smallexample | |
530 | -- This is for GNU Emacs C source files | |
531 | @{c@}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/\1/ | |
532 | @end smallexample | |
533 | ||
534 | @noindent | |
535 | and then use it like this: | |
536 | ||
537 | @smallexample | |
538 | etags --regex=@@emacs.tags *.[ch] */*.[ch] | |
539 | @end smallexample | |
540 | ||
541 | Here are some more examples. The regexps are quoted to protect them | |
542 | from shell interpretation. | |
543 | ||
544 | @itemize @bullet | |
545 | ||
546 | @item | |
547 | Tag Octave files: | |
548 | ||
549 | @smallexample | |
550 | etags --language=none \ | |
551 | --regex='/[ \t]*function.*=[ \t]*\([^ \t]*\)[ \t]*(/\1/' \ | |
552 | --regex='/###key \(.*\)/\1/' \ | |
553 | --regex='/[ \t]*global[ \t].*/' \ | |
554 | *.m | |
555 | @end smallexample | |
556 | ||
557 | @noindent | |
558 | Note that tags are not generated for scripts, so that you have to add | |
559 | a line by yourself of the form @samp{###key @var{scriptname}} if you | |
560 | want to jump to it. | |
561 | ||
562 | @item | |
563 | Tag Tcl files: | |
564 | ||
565 | @smallexample | |
566 | etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' *.tcl | |
567 | @end smallexample | |
568 | ||
569 | @item | |
570 | Tag VHDL files: | |
571 | ||
572 | @smallexample | |
573 | etags --language=none \ | |
574 | --regex='/[ \t]*\(ARCHITECTURE\|CONFIGURATION\) +[^ ]* +OF/' \ | |
575 | --regex='/[ \t]*\(ATTRIBUTE\|ENTITY\|FUNCTION\|PACKAGE\ | |
576 | \( BODY\)?\|PROCEDURE\|PROCESS\|TYPE\)[ \t]+\([^ \t(]+\)/\3/' | |
577 | @end smallexample | |
578 | @end itemize | |
579 | ||
580 | @node Select Tags Table | |
581 | @subsection Selecting a Tags Table | |
582 | ||
583 | @vindex tags-file-name | |
584 | @findex visit-tags-table | |
585 | Emacs has at any time one @dfn{selected} tags table, and all the commands | |
586 | for working with tags tables use the selected one. To select a tags table, | |
587 | type @kbd{M-x visit-tags-table}, which reads the tags table file name as an | |
588 | argument. The name @file{TAGS} in the default directory is used as the | |
589 | default file name. | |
590 | ||
591 | All this command does is store the file name in the variable | |
592 | @code{tags-file-name}. Emacs does not actually read in the tags table | |
593 | contents until you try to use them. Setting this variable yourself is just | |
594 | as good as using @code{visit-tags-table}. The variable's initial value is | |
595 | @code{nil}; that value tells all the commands for working with tags tables | |
596 | that they must ask for a tags table file name to use. | |
597 | ||
598 | Using @code{visit-tags-table} when a tags table is already loaded | |
599 | gives you a choice: you can add the new tags table to the current list | |
600 | of tags tables, or start a new list. The tags commands use all the tags | |
601 | tables in the current list. If you start a new list, the new tags table | |
602 | is used @emph{instead} of others. If you add the new table to the | |
603 | current list, it is used @emph{as well as} the others. When the tags | |
604 | commands scan the list of tags tables, they don't always start at the | |
605 | beginning of the list; they start with the first tags table (if any) | |
606 | that describes the current file, proceed from there to the end of the | |
607 | list, and then scan from the beginning of the list until they have | |
608 | covered all the tables in the list. | |
609 | ||
610 | @vindex tags-table-list | |
611 | You can specify a precise list of tags tables by setting the variable | |
612 | @code{tags-table-list} to a list of strings, like this: | |
613 | ||
614 | @c keep this on two lines for formatting in smallbook | |
615 | @example | |
616 | @group | |
617 | (setq tags-table-list | |
618 | '("~/emacs" "/usr/local/lib/emacs/src")) | |
619 | @end group | |
620 | @end example | |
621 | ||
622 | @noindent | |
623 | This tells the tags commands to look at the @file{TAGS} files in your | |
624 | @file{~/emacs} directory and in the @file{/usr/local/lib/emacs/src} | |
625 | directory. The order depends on which file you are in and which tags | |
626 | table mentions that file, as explained above. | |
627 | ||
628 | Do not set both @code{tags-file-name} and @code{tags-table-list}. | |
629 | ||
630 | @node Find Tag | |
631 | @subsection Finding a Tag | |
632 | ||
633 | The most important thing that a tags table enables you to do is to find | |
634 | the definition of a specific tag. | |
635 | ||
636 | @table @kbd | |
637 | @item M-.@: @var{tag} @key{RET} | |
638 | Find first definition of @var{tag} (@code{find-tag}). | |
639 | @item C-u M-. | |
640 | Find next alternate definition of last tag specified. | |
641 | @item C-u - M-. | |
642 | Go back to previous tag found. | |
643 | @item C-M-. @var{pattern} @key{RET} | |
644 | Find a tag whose name matches @var{pattern} (@code{find-tag-regexp}). | |
645 | @item C-u C-M-. | |
646 | Find the next tag whose name matches the last pattern used. | |
647 | @item C-x 4 .@: @var{tag} @key{RET} | |
648 | Find first definition of @var{tag}, but display it in another window | |
649 | (@code{find-tag-other-window}). | |
650 | @item C-x 5 .@: @var{tag} @key{RET} | |
651 | Find first definition of @var{tag}, and create a new frame to select the | |
652 | buffer (@code{find-tag-other-frame}). | |
653 | @item M-* | |
654 | Pop back to where you previously invoked @kbd{M-.} and friends. | |
655 | @end table | |
656 | ||
657 | @kindex M-. | |
658 | @findex find-tag | |
659 | @kbd{M-.}@: (@code{find-tag}) is the command to find the definition of | |
660 | a specified tag. It searches through the tags table for that tag, as a | |
661 | string, and then uses the tags table info to determine the file that the | |
662 | definition is in and the approximate character position in the file of | |
663 | the definition. Then @code{find-tag} visits that file, moves point to | |
664 | the approximate character position, and searches ever-increasing | |
665 | distances away to find the tag definition. | |
666 | ||
667 | If an empty argument is given (just type @key{RET}), the balanced | |
668 | expression in the buffer before or around point is used as the | |
669 | @var{tag} argument. @xref{Expressions}. | |
670 | ||
671 | You don't need to give @kbd{M-.} the full name of the tag; a part | |
672 | will do. This is because @kbd{M-.} finds tags in the table which | |
673 | contain @var{tag} as a substring. However, it prefers an exact match | |
674 | to a substring match. To find other tags that match the same | |
675 | substring, give @code{find-tag} a numeric argument, as in @kbd{C-u | |
676 | M-.}; this does not read a tag name, but continues searching the tags | |
677 | table's text for another tag containing the same substring last used. | |
678 | If you have a real @key{META} key, @kbd{M-0 M-.}@: is an easier | |
679 | alternative to @kbd{C-u M-.}. | |
680 | ||
681 | @kindex C-x 4 . | |
682 | @findex find-tag-other-window | |
683 | @kindex C-x 5 . | |
684 | @findex find-tag-other-frame | |
685 | Like most commands that can switch buffers, @code{find-tag} has a | |
686 | variant that displays the new buffer in another window, and one that | |
687 | makes a new frame for it. The former is @kbd{C-x 4 .}, which invokes | |
688 | the command @code{find-tag-other-window}. The latter is @kbd{C-x 5 .}, | |
689 | which invokes @code{find-tag-other-frame}. | |
690 | ||
691 | To move back to places you've found tags recently, use @kbd{C-u - | |
692 | M-.}; more generally, @kbd{M-.} with a negative numeric argument. This | |
693 | command can take you to another buffer. @kbd{C-x 4 .} with a negative | |
694 | argument finds the previous tag location in another window. | |
695 | ||
696 | @kindex M-* | |
697 | @findex pop-tag-mark | |
698 | @vindex find-tag-marker-ring-length | |
699 | As well as going back to places you've found tags recently, you can go | |
700 | back to places @emph{from where} you found them. Use @kbd{M-*}, which | |
701 | invokes the command @code{pop-tag-mark}, for this. Typically you would | |
702 | find and study the definition of something with @kbd{M-.} and then | |
703 | return to where you were with @kbd{M-*}. | |
704 | ||
705 | Both @kbd{C-u - M-.} and @kbd{M-*} allow you to retrace your steps to | |
706 | a depth determined by the variable @code{find-tag-marker-ring-length}. | |
707 | ||
708 | @findex find-tag-regexp | |
709 | @kindex C-M-. | |
710 | The command @kbd{C-M-.} (@code{find-tag-regexp}) visits the tags that | |
711 | match a specified regular expression. It is just like @kbd{M-.} except | |
712 | that it does regexp matching instead of substring matching. | |
713 | ||
714 | @node Tags Search | |
715 | @subsection Searching and Replacing with Tags Tables | |
716 | @cindex search and replace in multiple files | |
717 | @cindex multiple-file search and replace | |
718 | ||
719 | The commands in this section visit and search all the files listed in the | |
720 | selected tags table, one by one. For these commands, the tags table serves | |
721 | only to specify a sequence of files to search. | |
722 | ||
723 | @table @kbd | |
724 | @item M-x tags-search @key{RET} @var{regexp} @key{RET} | |
725 | Search for @var{regexp} through the files in the selected tags | |
726 | table. | |
727 | @item M-x tags-query-replace @key{RET} @var{regexp} @key{RET} @var{replacement} @key{RET} | |
728 | Perform a @code{query-replace-regexp} on each file in the selected tags table. | |
729 | @item M-, | |
730 | Restart one of the commands above, from the current location of point | |
731 | (@code{tags-loop-continue}). | |
732 | @end table | |
733 | ||
734 | @findex tags-search | |
735 | @kbd{M-x tags-search} reads a regexp using the minibuffer, then | |
736 | searches for matches in all the files in the selected tags table, one | |
737 | file at a time. It displays the name of the file being searched so you | |
738 | can follow its progress. As soon as it finds an occurrence, | |
739 | @code{tags-search} returns. | |
740 | ||
741 | @kindex M-, | |
742 | @findex tags-loop-continue | |
743 | Having found one match, you probably want to find all the rest. To find | |
744 | one more match, type @kbd{M-,} (@code{tags-loop-continue}) to resume the | |
745 | @code{tags-search}. This searches the rest of the current buffer, followed | |
746 | by the remaining files of the tags table.@refill | |
747 | ||
748 | @findex tags-query-replace | |
749 | @kbd{M-x tags-query-replace} performs a single | |
750 | @code{query-replace-regexp} through all the files in the tags table. It | |
751 | reads a regexp to search for and a string to replace with, just like | |
752 | ordinary @kbd{M-x query-replace-regexp}. It searches much like @kbd{M-x | |
753 | tags-search}, but repeatedly, processing matches according to your | |
754 | input. @xref{Replace}, for more information on query replace. | |
755 | ||
756 | @vindex tags-case-fold-search | |
757 | @cindex case-sensitivity and tags search | |
758 | You can control the case-sensitivity of tags search commands by | |
759 | customizing the value of the variable @code{tags-case-fold-search}. The | |
760 | default is to use the same setting as the value of | |
761 | @code{case-fold-search} (@pxref{Search Case}). | |
762 | ||
763 | It is possible to get through all the files in the tags table with a | |
764 | single invocation of @kbd{M-x tags-query-replace}. But often it is | |
765 | useful to exit temporarily, which you can do with any input event that | |
766 | has no special query replace meaning. You can resume the query replace | |
767 | subsequently by typing @kbd{M-,}; this command resumes the last tags | |
768 | search or replace command that you did. | |
769 | ||
770 | The commands in this section carry out much broader searches than the | |
771 | @code{find-tag} family. The @code{find-tag} commands search only for | |
772 | definitions of tags that match your substring or regexp. The commands | |
773 | @code{tags-search} and @code{tags-query-replace} find every occurrence | |
774 | of the regexp, as ordinary search commands and replace commands do in | |
775 | the current buffer. | |
776 | ||
777 | These commands create buffers only temporarily for the files that they | |
778 | have to search (those which are not already visited in Emacs buffers). | |
779 | Buffers in which no match is found are quickly killed; the others | |
780 | continue to exist. | |
781 | ||
782 | It may have struck you that @code{tags-search} is a lot like | |
783 | @code{grep}. You can also run @code{grep} itself as an inferior of | |
784 | Emacs and have Emacs show you the matching lines one by one. This works | |
785 | much like running a compilation; finding the source locations of the | |
786 | @code{grep} matches works like finding the compilation errors. | |
787 | @xref{Compilation}. | |
788 | ||
789 | @node List Tags | |
790 | @subsection Tags Table Inquiries | |
791 | ||
792 | @table @kbd | |
793 | @item M-x list-tags @key{RET} @var{file} @key{RET} | |
794 | Display a list of the tags defined in the program file @var{file}. | |
795 | @item M-x tags-apropos @key{RET} @var{regexp} @key{RET} | |
796 | Display a list of all tags matching @var{regexp}. | |
797 | @end table | |
798 | ||
799 | @findex list-tags | |
800 | @kbd{M-x list-tags} reads the name of one of the files described by | |
801 | the selected tags table, and displays a list of all the tags defined in | |
802 | that file. The ``file name'' argument is really just a string to | |
803 | compare against the file names recorded in the tags table; it is read as | |
804 | a string rather than as a file name. Therefore, completion and | |
805 | defaulting are not available, and you must enter the file name the same | |
806 | way it appears in the tags table. Do not include a directory as part of | |
807 | the file name unless the file name recorded in the tags table includes a | |
808 | directory. | |
809 | ||
810 | @findex tags-apropos | |
811 | @vindex tags-apropos-verbose | |
812 | @kbd{M-x tags-apropos} is like @code{apropos} for tags | |
813 | (@pxref{Apropos}). It finds all the tags in the selected tags table | |
814 | whose entries match @var{regexp}, and displays them. If the variable | |
815 | @code{tags-apropos-verbose} is non-@code{nil}, it displays the names | |
816 | of the tags files together with the tag names. | |
817 | ||
818 | @vindex tags-tag-face | |
819 | @vindex tags-apropos-additional-actions | |
820 | You can customize the appearance of the output with the face | |
821 | @code{tags-tag-face}. You can display additional output with @kbd{M-x | |
822 | tags-apropos} by customizing the variable | |
823 | @code{tags-apropos-additional-actions}---see its documentation for | |
824 | details. | |
825 | ||
826 | You can also use the collection of tag names to complete a symbol | |
827 | name in the buffer. @xref{Symbol Completion}. | |
828 | ||
ebe19e1b | 829 | @node Emerge |
f00366c2 RS |
830 | @section Merging Files with Emerge |
831 | @cindex Emerge | |
832 | @cindex merging files | |
833 | ||
834 | It's not unusual for programmers to get their signals crossed and modify | |
835 | the same program in two different directions. To recover from this | |
836 | confusion, you need to merge the two versions. Emerge makes this | |
837 | easier. See also @ref{Comparing Files}, for commands to compare | |
838 | in a more manual fashion, and @ref{,Ediff,, ediff, The Ediff Manual}. | |
839 | ||
840 | @menu | |
841 | * Overview of Emerge:: How to start Emerge. Basic concepts. | |
842 | * Submodes of Emerge:: Fast mode vs. Edit mode. | |
843 | Skip Prefers mode and Auto Advance mode. | |
844 | * State of Difference:: You do the merge by specifying state A or B | |
845 | for each difference. | |
846 | * Merge Commands:: Commands for selecting a difference, | |
847 | changing states of differences, etc. | |
848 | * Exiting Emerge:: What to do when you've finished the merge. | |
849 | * Combining in Emerge:: How to keep both alternatives for a difference. | |
850 | * Fine Points of Emerge:: Misc. | |
851 | @end menu | |
852 | ||
853 | @node Overview of Emerge | |
854 | @subsection Overview of Emerge | |
855 | ||
856 | To start Emerge, run one of these four commands: | |
857 | ||
858 | @table @kbd | |
859 | @item M-x emerge-files | |
860 | @findex emerge-files | |
861 | Merge two specified files. | |
862 | ||
863 | @item M-x emerge-files-with-ancestor | |
864 | @findex emerge-files-with-ancestor | |
865 | Merge two specified files, with reference to a common ancestor. | |
866 | ||
867 | @item M-x emerge-buffers | |
868 | @findex emerge-buffers | |
869 | Merge two buffers. | |
870 | ||
871 | @item M-x emerge-buffers-with-ancestor | |
872 | @findex emerge-buffers-with-ancestor | |
873 | Merge two buffers with reference to a common ancestor in a third | |
874 | buffer. | |
875 | @end table | |
876 | ||
877 | @cindex merge buffer (Emerge) | |
878 | @cindex A and B buffers (Emerge) | |
879 | The Emerge commands compare two files or buffers, and display the | |
880 | comparison in three buffers: one for each input text (the @dfn{A buffer} | |
881 | and the @dfn{B buffer}), and one (the @dfn{merge buffer}) where merging | |
882 | takes place. The merge buffer shows the full merged text, not just the | |
883 | differences. Wherever the two input texts differ, you can choose which | |
884 | one of them to include in the merge buffer. | |
885 | ||
886 | The Emerge commands that take input from existing buffers use only the | |
887 | accessible portions of those buffers, if they are narrowed | |
888 | (@pxref{Narrowing}). | |
889 | ||
890 | If a common ancestor version is available, from which the two texts to | |
891 | be merged were both derived, Emerge can use it to guess which | |
892 | alternative is right. Wherever one current version agrees with the | |
893 | ancestor, Emerge presumes that the other current version is a deliberate | |
894 | change which should be kept in the merged version. Use the | |
895 | @samp{with-ancestor} commands if you want to specify a common ancestor | |
896 | text. These commands read three file or buffer names---variant A, | |
897 | variant B, and the common ancestor. | |
898 | ||
899 | After the comparison is done and the buffers are prepared, the | |
900 | interactive merging starts. You control the merging by typing special | |
901 | @dfn{merge commands} in the merge buffer. The merge buffer shows you a | |
902 | full merged text, not just differences. For each run of differences | |
903 | between the input texts, you can choose which one of them to keep, or | |
904 | edit them both together. | |
905 | ||
906 | The merge buffer uses a special major mode, Emerge mode, with commands | |
907 | for making these choices. But you can also edit the buffer with | |
908 | ordinary Emacs commands. | |
909 | ||
910 | At any given time, the attention of Emerge is focused on one | |
911 | particular difference, called the @dfn{selected} difference. This | |
912 | difference is marked off in the three buffers like this: | |
913 | ||
914 | @example | |
915 | vvvvvvvvvvvvvvvvvvvv | |
916 | @var{text that differs} | |
917 | ^^^^^^^^^^^^^^^^^^^^ | |
918 | @end example | |
919 | ||
920 | @noindent | |
921 | Emerge numbers all the differences sequentially and the mode | |
922 | line always shows the number of the selected difference. | |
923 | ||
924 | Normally, the merge buffer starts out with the A version of the text. | |
925 | But when the A version of a difference agrees with the common ancestor, | |
926 | then the B version is initially preferred for that difference. | |
927 | ||
928 | Emerge leaves the merged text in the merge buffer when you exit. At | |
929 | that point, you can save it in a file with @kbd{C-x C-w}. If you give a | |
930 | numeric argument to @code{emerge-files} or | |
931 | @code{emerge-files-with-ancestor}, it reads the name of the output file | |
932 | using the minibuffer. (This is the last file name those commands read.) | |
933 | Then exiting from Emerge saves the merged text in the output file. | |
934 | ||
935 | Normally, Emerge commands save the output buffer in its file when you | |
936 | exit. If you abort Emerge with @kbd{C-]}, the Emerge command does not | |
937 | save the output buffer, but you can save it yourself if you wish. | |
938 | ||
939 | @node Submodes of Emerge | |
940 | @subsection Submodes of Emerge | |
941 | ||
942 | You can choose between two modes for giving merge commands: Fast mode | |
943 | and Edit mode. In Fast mode, basic merge commands are single | |
944 | characters, but ordinary Emacs commands are disabled. This is | |
945 | convenient if you use only merge commands. In Edit mode, all merge | |
946 | commands start with the prefix key @kbd{C-c C-c}, and the normal Emacs | |
947 | commands are also available. This allows editing the merge buffer, but | |
948 | slows down Emerge operations. | |
949 | ||
950 | Use @kbd{e} to switch to Edit mode, and @kbd{C-c C-c f} to switch to | |
951 | Fast mode. The mode line indicates Edit and Fast modes with @samp{E} | |
952 | and @samp{F}. | |
953 | ||
954 | Emerge has two additional submodes that affect how particular merge | |
955 | commands work: Auto Advance mode and Skip Prefers mode. | |
956 | ||
957 | If Auto Advance mode is in effect, the @kbd{a} and @kbd{b} commands | |
958 | advance to the next difference. This lets you go through the merge | |
959 | faster as long as you simply choose one of the alternatives from the | |
960 | input. The mode line indicates Auto Advance mode with @samp{A}. | |
961 | ||
962 | If Skip Prefers mode is in effect, the @kbd{n} and @kbd{p} commands | |
963 | skip over differences in states prefer-A and prefer-B (@pxref{State of | |
964 | Difference}). Thus you see only differences for which neither version | |
965 | is presumed ``correct.'' The mode line indicates Skip Prefers mode with | |
966 | @samp{S}. | |
967 | ||
968 | @findex emerge-auto-advance-mode | |
969 | @findex emerge-skip-prefers-mode | |
970 | Use the command @kbd{s a} (@code{emerge-auto-advance-mode}) to set or | |
971 | clear Auto Advance mode. Use @kbd{s s} | |
972 | (@code{emerge-skip-prefers-mode}) to set or clear Skip Prefers mode. | |
973 | These commands turn on the mode with a positive argument, turns it off | |
974 | with a negative or zero argument, and toggle the mode with no argument. | |
975 | ||
976 | @node State of Difference | |
977 | @subsection State of a Difference | |
978 | ||
979 | In the merge buffer, a difference is marked with lines of @samp{v} and | |
980 | @samp{^} characters. Each difference has one of these seven states: | |
981 | ||
982 | @table @asis | |
983 | @item A | |
984 | The difference is showing the A version. The @kbd{a} command always | |
985 | produces this state; the mode line indicates it with @samp{A}. | |
986 | ||
987 | @item B | |
988 | The difference is showing the B version. The @kbd{b} command always | |
989 | produces this state; the mode line indicates it with @samp{B}. | |
990 | ||
991 | @item default-A | |
992 | @itemx default-B | |
993 | The difference is showing the A or the B state by default, because you | |
994 | haven't made a choice. All differences start in the default-A state | |
995 | (and thus the merge buffer is a copy of the A buffer), except those for | |
996 | which one alternative is ``preferred'' (see below). | |
997 | ||
998 | When you select a difference, its state changes from default-A or | |
999 | default-B to plain A or B. Thus, the selected difference never has | |
1000 | state default-A or default-B, and these states are never displayed in | |
1001 | the mode line. | |
1002 | ||
1003 | The command @kbd{d a} chooses default-A as the default state, and @kbd{d | |
1004 | b} chooses default-B. This chosen default applies to all differences | |
1005 | which you haven't ever selected and for which no alternative is preferred. | |
1006 | If you are moving through the merge sequentially, the differences you | |
1007 | haven't selected are those following the selected one. Thus, while | |
1008 | moving sequentially, you can effectively make the A version the default | |
1009 | for some sections of the merge buffer and the B version the default for | |
1010 | others by using @kbd{d a} and @kbd{d b} between sections. | |
1011 | ||
1012 | @item prefer-A | |
1013 | @itemx prefer-B | |
1014 | The difference is showing the A or B state because it is | |
1015 | @dfn{preferred}. This means that you haven't made an explicit choice, | |
1016 | but one alternative seems likely to be right because the other | |
1017 | alternative agrees with the common ancestor. Thus, where the A buffer | |
1018 | agrees with the common ancestor, the B version is preferred, because | |
1019 | chances are it is the one that was actually changed. | |
1020 | ||
1021 | These two states are displayed in the mode line as @samp{A*} and @samp{B*}. | |
1022 | ||
1023 | @item combined | |
1024 | The difference is showing a combination of the A and B states, as a | |
1025 | result of the @kbd{x c} or @kbd{x C} commands. | |
1026 | ||
1027 | Once a difference is in this state, the @kbd{a} and @kbd{b} commands | |
1028 | don't do anything to it unless you give them a numeric argument. | |
1029 | ||
1030 | The mode line displays this state as @samp{comb}. | |
1031 | @end table | |
1032 | ||
1033 | @node Merge Commands | |
1034 | @subsection Merge Commands | |
1035 | ||
1036 | Here are the Merge commands for Fast mode; in Edit mode, precede them | |
1037 | with @kbd{C-c C-c}: | |
1038 | ||
1039 | @table @kbd | |
1040 | @item p | |
1041 | Select the previous difference. | |
1042 | ||
1043 | @item n | |
1044 | Select the next difference. | |
1045 | ||
1046 | @item a | |
1047 | Choose the A version of this difference. | |
1048 | ||
1049 | @item b | |
1050 | Choose the B version of this difference. | |
1051 | ||
1052 | @item C-u @var{n} j | |
1053 | Select difference number @var{n}. | |
1054 | ||
1055 | @item . | |
1056 | Select the difference containing point. You can use this command in the | |
1057 | merge buffer or in the A or B buffer. | |
1058 | ||
1059 | @item q | |
1060 | Quit---finish the merge. | |
1061 | ||
1062 | @item C-] | |
1063 | Abort---exit merging and do not save the output. | |
1064 | ||
1065 | @item f | |
1066 | Go into Fast mode. (In Edit mode, this is actually @kbd{C-c C-c f}.) | |
1067 | ||
1068 | @item e | |
1069 | Go into Edit mode. | |
1070 | ||
1071 | @item l | |
1072 | Recenter (like @kbd{C-l}) all three windows. | |
1073 | ||
1074 | @item - | |
1075 | Specify part of a prefix numeric argument. | |
1076 | ||
1077 | @item @var{digit} | |
1078 | Also specify part of a prefix numeric argument. | |
1079 | ||
1080 | @item d a | |
1081 | Choose the A version as the default from here down in | |
1082 | the merge buffer. | |
1083 | ||
1084 | @item d b | |
1085 | Choose the B version as the default from here down in | |
1086 | the merge buffer. | |
1087 | ||
1088 | @item c a | |
1089 | Copy the A version of this difference into the kill ring. | |
1090 | ||
1091 | @item c b | |
1092 | Copy the B version of this difference into the kill ring. | |
1093 | ||
1094 | @item i a | |
1095 | Insert the A version of this difference at point. | |
1096 | ||
1097 | @item i b | |
1098 | Insert the B version of this difference at point. | |
1099 | ||
1100 | @item m | |
1101 | Put point and mark around the difference. | |
1102 | ||
1103 | @item ^ | |
1104 | Scroll all three windows down (like @kbd{M-v}). | |
1105 | ||
1106 | @item v | |
1107 | Scroll all three windows up (like @kbd{C-v}). | |
1108 | ||
1109 | @item < | |
1110 | Scroll all three windows left (like @kbd{C-x <}). | |
1111 | ||
1112 | @item > | |
1113 | Scroll all three windows right (like @kbd{C-x >}). | |
1114 | ||
1115 | @item | | |
1116 | Reset horizontal scroll on all three windows. | |
1117 | ||
1118 | @item x 1 | |
1119 | Shrink the merge window to one line. (Use @kbd{C-u l} to restore it | |
1120 | to full size.) | |
1121 | ||
1122 | @item x c | |
1123 | Combine the two versions of this difference (@pxref{Combining in | |
1124 | Emerge}). | |
1125 | ||
1126 | @item x f | |
1127 | Show the names of the files/buffers Emerge is operating on, in a Help | |
1128 | window. (Use @kbd{C-u l} to restore windows.) | |
1129 | ||
1130 | @item x j | |
1131 | Join this difference with the following one. | |
1132 | (@kbd{C-u x j} joins this difference with the previous one.) | |
1133 | ||
1134 | @item x s | |
1135 | Split this difference into two differences. Before you use this | |
1136 | command, position point in each of the three buffers at the place where | |
1137 | you want to split the difference. | |
1138 | ||
1139 | @item x t | |
1140 | Trim identical lines off the top and bottom of the difference. | |
1141 | Such lines occur when the A and B versions are | |
1142 | identical but differ from the ancestor version. | |
1143 | @end table | |
1144 | ||
1145 | @node Exiting Emerge | |
1146 | @subsection Exiting Emerge | |
1147 | ||
1148 | The @kbd{q} command (@code{emerge-quit}) finishes the merge, storing | |
1149 | the results into the output file if you specified one. It restores the | |
1150 | A and B buffers to their proper contents, or kills them if they were | |
1151 | created by Emerge and you haven't changed them. It also disables the | |
1152 | Emerge commands in the merge buffer, since executing them later could | |
1153 | damage the contents of the various buffers. | |
1154 | ||
1155 | @kbd{C-]} aborts the merge. This means exiting without writing the | |
1156 | output file. If you didn't specify an output file, then there is no | |
1157 | real difference between aborting and finishing the merge. | |
1158 | ||
1159 | If the Emerge command was called from another Lisp program, then its | |
1160 | return value is @code{t} for successful completion, or @code{nil} if you | |
1161 | abort. | |
1162 | ||
1163 | @node Combining in Emerge | |
1164 | @subsection Combining the Two Versions | |
1165 | ||
1166 | Sometimes you want to keep @emph{both} alternatives for a particular | |
1167 | difference. To do this, use @kbd{x c}, which edits the merge buffer | |
1168 | like this: | |
1169 | ||
1170 | @example | |
1171 | @group | |
1172 | #ifdef NEW | |
1173 | @var{version from A buffer} | |
1174 | #else /* not NEW */ | |
1175 | @var{version from B buffer} | |
1176 | #endif /* not NEW */ | |
1177 | @end group | |
1178 | @end example | |
1179 | ||
1180 | @noindent | |
1181 | @vindex emerge-combine-versions-template | |
1182 | While this example shows C preprocessor conditionals delimiting the two | |
1183 | alternative versions, you can specify the strings to use by setting | |
1184 | the variable @code{emerge-combine-versions-template} to a string of your | |
1185 | choice. In the string, @samp{%a} says where to put version A, and | |
1186 | @samp{%b} says where to put version B. The default setting, which | |
1187 | produces the results shown above, looks like this: | |
1188 | ||
1189 | @example | |
1190 | @group | |
1191 | "#ifdef NEW\n%a#else /* not NEW */\n%b#endif /* not NEW */\n" | |
1192 | @end group | |
1193 | @end example | |
1194 | ||
1195 | @node Fine Points of Emerge | |
1196 | @subsection Fine Points of Emerge | |
1197 | ||
1198 | During the merge, you mustn't try to edit the A and B buffers yourself. | |
1199 | Emerge modifies them temporarily, but ultimately puts them back the way | |
1200 | they were. | |
1201 | ||
1202 | You can have any number of merges going at once---just don't use any one | |
1203 | buffer as input to more than one merge at once, since the temporary | |
1204 | changes made in these buffers would get in each other's way. | |
1205 | ||
1206 | Starting Emerge can take a long time because it needs to compare the | |
1207 | files fully. Emacs can't do anything else until @code{diff} finishes. | |
1208 | Perhaps in the future someone will change Emerge to do the comparison in | |
1209 | the background when the input files are large---then you could keep on | |
1210 | doing other things with Emacs until Emerge is ready to accept | |
1211 | commands. | |
1212 | ||
1213 | @vindex emerge-startup-hook | |
1214 | After setting up the merge, Emerge runs the hook | |
1215 | @code{emerge-startup-hook} (@pxref{Hooks}). | |
1216 |