Mercurial > hg > xemacs-beta

comparison man/xemacs/building.texi @ 371:cc15677e0335 r21-2b1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2b1
author cvs
date Mon, 13 Aug 2007 11:03:08 +0200
parents a4f53d9b3154
children de805c49cfc1
comparison
equal deleted inserted replaced
370:bd866891f083 371:cc15677e0335
1 1
2 @node Running, Abbrevs, Programs, Top 2 @node Running, Packages, Programs, Top
3 @chapter Compiling and Testing Programs 3 @chapter Compiling and Testing Programs
4 4
5 The previous chapter discusses the Emacs commands that are useful for 5 The previous chapter discusses the Emacs commands that are useful for
6 making changes in programs. This chapter deals with commands that assist 6 making changes in programs. This chapter deals with commands that assist
7 in the larger process of developing and maintaining programs. 7 in the larger process of developing and maintaining programs.
69 the word @samp{run} or @samp{exit} in the parentheses to tell you whether 69 the word @samp{run} or @samp{exit} in the parentheses to tell you whether
70 compilation is finished. You do not have to keep this buffer visible; 70 compilation is finished. You do not have to keep this buffer visible;
71 compilation continues in any case. 71 compilation continues in any case.
72 72
73 @findex kill-compilation 73 @findex kill-compilation
74 To kill the compilation process, type @kbd{M-x kill-compilation}. The mode 74 To kill the compilation process, type @kbd{M-x-kill-compilation}. The mode
75 line of the @samp{*compilation*} buffer changes to say @samp{signal} 75 line of the @samp{*compilation*} buffer changes to say @samp{signal}
76 instead of @samp{run}. Starting a new compilation also kills any 76 instead of @samp{run}. Starting a new compilation also kills any
77 running compilation, as only one can occur at any time. Starting a new 77 running compilation, as only one can occur at any time. Starting a new
78 compilation prompts for confirmation before actually killing a 78 compilation prompts for confirmation before actually killing a
79 compilation that is running.@refill 79 compilation that is running.@refill
478 usual Emacs editing commands are available; you can switch windows to 478 usual Emacs editing commands are available; you can switch windows to
479 examine the buffer that was being edited at the time of the error, and 479 examine the buffer that was being edited at the time of the error, and
480 you can switch buffers, visit files, and perform any other editing 480 you can switch buffers, visit files, and perform any other editing
481 operations. However, the debugger is a recursive editing level 481 operations. However, the debugger is a recursive editing level
482 (@pxref{Recursive Edit}); it is a good idea to return to the backtrace 482 (@pxref{Recursive Edit}); it is a good idea to return to the backtrace
483 buffer and explicitly exit the debugger when you don't want to use it any 483 buffer and explictly exit the debugger when you don't want to use it any
484 more. Exiting the debugger kills the backtrace buffer. 484 more. Exiting the debugger kills the backtrace buffer.
485 485
486 @cindex current stack frame 486 @cindex current stack frame
487 The contents of the backtrace buffer show you the functions that are 487 The contents of the backtrace buffer show you the functions that are
488 executing and the arguments that were given to them. It also allows you 488 executing and the arguments that were given to them. It also allows you