Mercurial > emacs

comparison man/building.texi @ 90180:62afea0771d8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Revision: miles@gnu.org--gnu-2005/emacs--unicode--0--patch-51 Merge from emacs--cvs-trunk--0 Patches applied: * emacs--cvs-trunk--0 (patch 289-301) - Update from CVS - Merge from gnus--rel--5.10 * gnus--rel--5.10 (patch 68) - Update from CVS
author Miles Bader <miles@gnu.org>
date Thu, 12 May 2005 03:41:19 +0000
parents 08185296b491 ebb9e325798e
children f042e7c0fe20
comparison
equal deleted inserted replaced
90179:b745036dab36 90180:62afea0771d8
115 that is running. You can also kill the compilation process with 115 that is running. You can also kill the compilation process with
116 @kbd{M-x kill-compilation}. 116 @kbd{M-x kill-compilation}.
117 117
118 @findex recompile 118 @findex recompile
119 To rerun the last compilation with the same command, type @kbd{M-x 119 To rerun the last compilation with the same command, type @kbd{M-x
120 recompile}. This automatically reuses the compilation command from the 120 recompile}. This automatically reuses the compilation command from
121 last invocation of @kbd{M-x compile}. 121 the last invocation of @kbd{M-x compile}. It also reuses the
122 @samp{*compilation*} buffer and starts the compilation in its default
123 directory, which is the directory in which the previous compilation
124 was started.
122 125
123 Emacs does not expect a compiler process to launch asynchronous 126 Emacs does not expect a compiler process to launch asynchronous
124 subprocesses; if it does, and they keep running after the main 127 subprocesses; if it does, and they keep running after the main
125 compiler process has terminated, Emacs may kill them or their output 128 compiler process has terminated, Emacs may kill them or their output
126 may not arrive in Emacs. To avoid this problem, make the main process 129 may not arrive in Emacs. To avoid this problem, make the main process
489 commands for your debugger are available, and you can use the Shell mode 492 commands for your debugger are available, and you can use the Shell mode
490 history commands to repeat them. @xref{Shell Mode}. 493 history commands to repeat them. @xref{Shell Mode}.
491 494
492 @cindex tooltips with GUD 495 @cindex tooltips with GUD
493 @vindex tooltip-gud-modes 496 @vindex tooltip-gud-modes
494 @vindex tooltip-gud-tips-p 497 @vindex gud-tooltip-mode
498 @vindex gud-tooltip-echo-area
495 The Tooltip facility (@pxref{Tooltips}) provides support for GUD@. 499 The Tooltip facility (@pxref{Tooltips}) provides support for GUD@.
496 You activate this feature by setting the variable 500 You activate this feature by turning on the minor mode
497 @code{tooltip-gud-tips-p} to @code{t}. Then you can display a 501 @code{gud-tooltip-mode}. Then you can display a variable's value in a
498 variable's value in a tooltip simply by pointing at it with the mouse. 502 tooltip simply by pointing at it with the mouse. In graphical mode,
499 In graphical mode, with a C program, you can also display the 503 with a C program, you can also display the @code{#define} directive
500 @code{#define} directive associated with an identifier when program is 504 associated with an identifier when the program is not executing. This
501 not executing. This operates in the GUD buffer and in source buffers 505 operates in the GUD buffer and in source buffers with major modes in
502 with major modes in the list @code{tooltip-gud-modes}. 506 the list @code{gud-tooltip-modes}. If the variable
507 @code{gud-tooltip-echo-area} is non-@code{nil} then the help text is
508 displayed in the echo area.
503 509
504 @node Commands of GUD 510 @node Commands of GUD
505 @subsection Commands of GUD 511 @subsection Commands of GUD
506 512
507 The GUD interaction buffer uses a variant of Shell mode, so the 513 The GUD interaction buffer uses a variant of Shell mode, so the