Mercurial > emacs
annotate man/building.texi @ 47347:28bab21524d4
(Fdiscard_input): If defining keyboard macro,
end and save it instead of discarding it.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Mon, 09 Sep 2002 22:33:36 +0000 |
parents | 36ac28961e4f |
children | 6be0f6ca3d49 |
rev | line source |
---|---|
25829 | 1 @c This is part of the Emacs manual. |
39287 | 2 @c Copyright (C) 1985,86,87,93,94,95,97,2000,2001 Free Software Foundation, Inc. |
25829 | 3 @c See file emacs.texi for copying conditions. |
38202 | 4 @node Building, Maintaining, Programs, Top |
25829 | 5 @chapter Compiling and Testing Programs |
6 @cindex building programs | |
7 @cindex program building | |
8 @cindex running Lisp functions | |
9 | |
10 The previous chapter discusses the Emacs commands that are useful for | |
11 making changes in programs. This chapter deals with commands that assist | |
12 in the larger process of developing and maintaining programs. | |
13 | |
14 @menu | |
15 * Compilation:: Compiling programs in languages other | |
16 than Lisp (C, Pascal, etc.). | |
17 * Grep Searching:: Running grep as if it were a compiler. | |
18 * Compilation Mode:: The mode for visiting compiler errors. | |
19 * Compilation Shell:: Customizing your shell properly | |
20 for use in the compilation buffer. | |
21 * Debuggers:: Running symbolic debuggers for non-Lisp programs. | |
22 * Executing Lisp:: Various modes for editing Lisp programs, | |
23 with different facilities for running | |
24 the Lisp programs. | |
25 * Libraries: Lisp Libraries. Creating Lisp programs to run in Emacs. | |
26 * Interaction: Lisp Interaction. Executing Lisp in an Emacs buffer. | |
27 * Eval: Lisp Eval. Executing a single Lisp expression in Emacs. | |
28 * External Lisp:: Communicating through Emacs with a separate Lisp. | |
29 @end menu | |
30 | |
31 @node Compilation | |
32 @section Running Compilations under Emacs | |
33 @cindex inferior process | |
34 @cindex make | |
35 @cindex compilation errors | |
36 @cindex error log | |
37 | |
38 Emacs can run compilers for noninteractive languages such as C and | |
39 Fortran as inferior processes, feeding the error log into an Emacs buffer. | |
40 It can also parse the error messages and show you the source lines where | |
41 compilation errors occurred. | |
42 | |
43 @table @kbd | |
44 @item M-x compile | |
37482
4b43d9f652aa
Correct typo on pdb-mode-hook.
Richard M. Stallman <rms@gnu.org>
parents:
37346
diff
changeset
|
45 Run a compiler asynchronously under Emacs, with error messages going to |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
46 the @samp{*compilation*} buffer. |
39820
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
47 @item M-x recompile |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
48 Invoke a compiler with the same command as in the last invocation of |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
49 @kbd{M-x compile}. |
25829 | 50 @item M-x grep |
51 Run @code{grep} asynchronously under Emacs, with matching lines | |
52 listed in the buffer named @samp{*grep*}. | |
53 @item M-x grep-find | |
54 Run @code{grep} via @code{find}, with user-specified arguments, and | |
55 collect output in the buffer named @samp{*grep*}. | |
56 @item M-x kill-compilation | |
57 @itemx M-x kill-grep | |
58 Kill the running compilation or @code{grep} subprocess. | |
59 @end table | |
60 | |
61 @findex compile | |
62 To run @code{make} or another compilation command, do @kbd{M-x | |
63 compile}. This command reads a shell command line using the minibuffer, | |
64 and then executes the command in an inferior shell, putting output in | |
65 the buffer named @samp{*compilation*}. The current buffer's default | |
66 directory is used as the working directory for the execution of the | |
67 command; normally, therefore, the compilation happens in this | |
68 directory. | |
69 | |
70 @vindex compile-command | |
71 When the shell command line is read, the minibuffer appears containing | |
72 a default command line, which is the command you used the last time you | |
73 did @kbd{M-x compile}. If you type just @key{RET}, the same command | |
74 line is used again. For the first @kbd{M-x compile}, the default is | |
75 @samp{make -k}. The default compilation command comes from the variable | |
76 @code{compile-command}; if the appropriate compilation command for a | |
77 file is something other than @samp{make -k}, it can be useful for the | |
78 file to specify a local value for @code{compile-command} (@pxref{File | |
79 Variables}). | |
80 | |
81 Starting a compilation displays the buffer @samp{*compilation*} in | |
82 another window but does not select it. The buffer's mode line tells you | |
83 whether compilation is finished, with the word @samp{run} or @samp{exit} | |
84 inside the parentheses. You do not have to keep this buffer visible; | |
85 compilation continues in any case. While a compilation is going on, the | |
86 string @samp{Compiling} appears in the mode lines of all windows. When | |
87 this string disappears, the compilation is finished. | |
88 | |
89 If you want to watch the compilation transcript as it appears, switch | |
90 to the @samp{*compilation*} buffer and move point to the end of the | |
91 buffer. When point is at the end, new compilation output is inserted | |
92 above point, which remains at the end. If point is not at the end of | |
93 the buffer, it remains fixed while more compilation output is added at | |
94 the end of the buffer. | |
95 | |
34935
390058c38d27
Add a cindex entry for compilation-scroll-output. Duplicate the variable's
Eli Zaretskii <eliz@gnu.org>
parents:
31027
diff
changeset
|
96 @cindex compilation buffer, keeping current position at the end |
25829 | 97 @vindex compilation-scroll-output |
98 If you set the variable @code{compilation-scroll-output} to a | |
99 non-@code{nil} value, then the compilation buffer always scrolls to | |
100 follow output as it comes in. | |
101 | |
102 @findex kill-compilation | |
103 To kill the compilation process, do @kbd{M-x kill-compilation}. When | |
104 the compiler process terminates, the mode line of the | |
105 @samp{*compilation*} buffer changes to say @samp{signal} instead of | |
106 @samp{run}. Starting a new compilation also kills any running | |
107 compilation, as only one can exist at any time. However, @kbd{M-x | |
108 compile} asks for confirmation before actually killing a compilation | |
109 that is running. | |
110 | |
39820
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
111 @findex recompile |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
112 To rerun the last compilation with the same command, type @kbd{M-x |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
113 recompile}. This automatically reuses the compilation command from the |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
114 last invocation of @kbd{M-x compile}. |
f0947afcdf4c
(Compilation): Document "M-x recompile".
Eli Zaretskii <eliz@gnu.org>
parents:
39287
diff
changeset
|
115 |
46362
36ac28961e4f
Say that output from asynch subprocesses of a compiler may be lost.
Richard M. Stallman <rms@gnu.org>
parents:
46238
diff
changeset
|
116 Emacs does not expect a compiler to launch asynchronous |
36ac28961e4f
Say that output from asynch subprocesses of a compiler may be lost.
Richard M. Stallman <rms@gnu.org>
parents:
46238
diff
changeset
|
117 subprocesses; if it does, and they keep running after the main |
36ac28961e4f
Say that output from asynch subprocesses of a compiler may be lost.
Richard M. Stallman <rms@gnu.org>
parents:
46238
diff
changeset
|
118 compiler process has terminated, their output may not arrive in Emacs. |
36ac28961e4f
Say that output from asynch subprocesses of a compiler may be lost.
Richard M. Stallman <rms@gnu.org>
parents:
46238
diff
changeset
|
119 |
25829 | 120 @node Grep Searching |
121 @section Searching with Grep under Emacs | |
122 | |
123 @findex grep | |
124 Just as you can run a compiler from Emacs and then visit the lines | |
125 where there were compilation errors, you can also run @code{grep} and | |
126 then visit the lines on which matches were found. This works by | |
127 treating the matches reported by @code{grep} as if they were ``errors.'' | |
128 | |
129 To do this, type @kbd{M-x grep}, then enter a command line that | |
130 specifies how to run @code{grep}. Use the same arguments you would give | |
131 @code{grep} when running it normally: a @code{grep}-style regexp | |
132 (usually in single-quotes to quote the shell's special characters) | |
133 followed by file names, which may use wildcards. The output from | |
134 @code{grep} goes in the @samp{*grep*} buffer. You can find the | |
135 corresponding lines in the original files using @kbd{C-x `} and | |
136 @key{RET}, as with compilation errors. | |
137 | |
138 If you specify a prefix argument for @kbd{M-x grep}, it figures out | |
139 the tag (@pxref{Tags}) around point, and puts that into the default | |
140 @code{grep} command. | |
141 | |
142 @findex grep-find | |
143 The command @kbd{M-x grep-find} is similar to @kbd{M-x grep}, but it | |
144 supplies a different initial default for the command---one that runs | |
145 both @code{find} and @code{grep}, so as to search every file in a | |
146 directory tree. See also the @code{find-grep-dired} command, | |
147 in @ref{Dired and Find}. | |
148 | |
149 @node Compilation Mode | |
150 @section Compilation Mode | |
151 | |
152 @findex compile-goto-error | |
153 @cindex Compilation mode | |
154 @cindex mode, Compilation | |
155 The @samp{*compilation*} buffer uses a special major mode, Compilation | |
156 mode, whose main feature is to provide a convenient way to look at the | |
157 source line where the error happened. | |
158 | |
34935
390058c38d27
Add a cindex entry for compilation-scroll-output. Duplicate the variable's
Eli Zaretskii <eliz@gnu.org>
parents:
31027
diff
changeset
|
159 If you set the variable @code{compilation-scroll-output} to a |
390058c38d27
Add a cindex entry for compilation-scroll-output. Duplicate the variable's
Eli Zaretskii <eliz@gnu.org>
parents:
31027
diff
changeset
|
160 non-@code{nil} value, then the compilation buffer always scrolls to |
390058c38d27
Add a cindex entry for compilation-scroll-output. Duplicate the variable's
Eli Zaretskii <eliz@gnu.org>
parents:
31027
diff
changeset
|
161 follow output as it comes in. |
390058c38d27
Add a cindex entry for compilation-scroll-output. Duplicate the variable's
Eli Zaretskii <eliz@gnu.org>
parents:
31027
diff
changeset
|
162 |
25829 | 163 @table @kbd |
164 @item C-x ` | |
165 Visit the locus of the next compiler error message or @code{grep} match. | |
166 @item @key{RET} | |
167 Visit the locus of the error message that point is on. | |
168 This command is used in the compilation buffer. | |
169 @item Mouse-2 | |
170 Visit the locus of the error message that you click on. | |
171 @end table | |
172 | |
173 @kindex C-x ` | |
174 @findex next-error | |
175 You can visit the source for any particular error message by moving | |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
176 point in the @samp{*compilation*} buffer to that error message and |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
177 typing @key{RET} (@code{compile-goto-error}). Alternatively, you can |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
178 click @kbd{Mouse-2} on the error message; you need not switch to the |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
179 @samp{*compilation*} buffer first. |
25829 | 180 |
181 To parse the compiler error messages sequentially, type @kbd{C-x `} | |
182 (@code{next-error}). The character following the @kbd{C-x} is the | |
183 backquote or ``grave accent,'' not the single-quote. This command is | |
184 available in all buffers, not just in @samp{*compilation*}; it displays | |
185 the next error message at the top of one window and source location of | |
186 the error in another window. | |
187 | |
188 The first time @kbd{C-x `} is used after the start of a compilation, | |
189 it moves to the first error's location. Subsequent uses of @kbd{C-x `} | |
190 advance down to subsequent errors. If you visit a specific error | |
191 message with @key{RET} or @kbd{Mouse-2}, subsequent @kbd{C-x `} | |
192 commands advance from there. When @kbd{C-x `} gets to the end of the | |
193 buffer and finds no more error messages to visit, it fails and signals | |
194 an Emacs error. | |
195 | |
196 @kbd{C-u C-x `} starts scanning from the beginning of the compilation | |
197 buffer. This is one way to process the same set of errors again. | |
198 | |
37983
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
199 @vindex compilation-error-regexp-alist |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
200 @vindex grep-regexp-alist |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
201 To parse messages from the compiler, Compilation mode uses the |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
202 variable @code{compilation-error-regexp-alist} which lists various |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
203 formats of error messages and tells Emacs how to extract the source file |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
204 and the line number from the text of a message. If your compiler isn't |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
205 supported, you can tailor Compilation mode to it by adding elements to |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
206 that list. A similar variable @code{grep-regexp-alist} tells Emacs how |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
207 to parse output of a @code{grep} command. |
081777df34a7
(Compilation Mode): Document compilation-error-regexp-alist.
Eli Zaretskii <eliz@gnu.org>
parents:
37482
diff
changeset
|
208 |
25829 | 209 Compilation mode also redefines the keys @key{SPC} and @key{DEL} to |
210 scroll by screenfuls, and @kbd{M-n} and @kbd{M-p} to move to the next or | |
211 previous error message. You can also use @kbd{M-@{} and @kbd{M-@}} to | |
212 move up or down to an error message for a different source file. | |
213 | |
214 The features of Compilation mode are also available in a minor mode | |
215 called Compilation Minor mode. This lets you parse error messages in | |
216 any buffer, not just a normal compilation output buffer. Type @kbd{M-x | |
217 compilation-minor-mode} to enable the minor mode. This defines the keys | |
218 @key{RET} and @kbd{Mouse-2}, as in the Compilation major mode. | |
219 | |
220 Compilation minor mode works in any buffer, as long as the contents | |
221 are in a format that it understands. In an Rlogin buffer (@pxref{Remote | |
222 Host}), Compilation minor mode automatically accesses remote source | |
223 files by FTP (@pxref{File Names}). | |
224 | |
225 @node Compilation Shell | |
226 @section Subshells for Compilation | |
227 | |
228 Emacs uses a shell to run the compilation command, but specifies | |
229 the option for a noninteractive shell. This means, in particular, that | |
230 the shell should start with no prompt. If you find your usual shell | |
231 prompt making an unsightly appearance in the @samp{*compilation*} | |
232 buffer, it means you have made a mistake in your shell's init file by | |
233 setting the prompt unconditionally. (This init file's name may be | |
234 @file{.bashrc}, @file{.profile}, @file{.cshrc}, @file{.shrc}, or various | |
235 other things, depending on the shell you use.) The shell init file | |
236 should set the prompt only if there already is a prompt. In csh, here | |
237 is how to do it: | |
238 | |
239 @example | |
240 if ($?prompt) set prompt = @dots{} | |
241 @end example | |
242 | |
243 @noindent | |
244 And here's how to do it in bash: | |
245 | |
246 @example | |
247 if [ "$@{PS1+set@}" = set ] | |
248 then PS1=@dots{} | |
249 fi | |
250 @end example | |
251 | |
252 There may well be other things that your shell's init file | |
253 ought to do only for an interactive shell. You can use the same | |
254 method to conditionalize them. | |
255 | |
256 The MS-DOS ``operating system'' does not support asynchronous | |
257 subprocesses; to work around this lack, @kbd{M-x compile} runs the | |
258 compilation command synchronously on MS-DOS. As a consequence, you must | |
259 wait until the command finishes before you can do anything else in | |
260 Emacs. @xref{MS-DOS}. | |
261 | |
262 @node Debuggers | |
263 @section Running Debuggers Under Emacs | |
264 @cindex debuggers | |
265 @cindex GUD library | |
266 @cindex GDB | |
267 @cindex DBX | |
268 @cindex SDB | |
269 @cindex XDB | |
270 @cindex Perldb | |
271 @cindex JDB | |
272 @cindex PDB | |
273 | |
274 @c Do you believe in GUD? | |
275 The GUD (Grand Unified Debugger) library provides an interface to | |
276 various symbolic debuggers from within Emacs. We recommend the debugger | |
277 GDB, which is free software, but you can also run DBX, SDB or XDB if you | |
278 have them. GUD can also serve as an interface to the Perl's debugging | |
279 mode, the Python debugger PDB, and to JDB, the Java Debugger. | |
37346
e80fc3e25af8
Add Lisp Debugger xref.
Richard M. Stallman <rms@gnu.org>
parents:
36144
diff
changeset
|
280 @xref{Debugger,, The Lisp Debugger, elisp, the Emacs Lisp Reference Manual}, |
e80fc3e25af8
Add Lisp Debugger xref.
Richard M. Stallman <rms@gnu.org>
parents:
36144
diff
changeset
|
281 for information on debugging Emacs Lisp programs. |
25829 | 282 |
283 @menu | |
284 * Starting GUD:: How to start a debugger subprocess. | |
285 * Debugger Operation:: Connection between the debugger and source buffers. | |
286 * Commands of GUD:: Key bindings for common commands. | |
287 * GUD Customization:: Defining your own commands for GUD. | |
27223 | 288 * GUD Tooltips:: Showing variable values by pointing with the mouse. |
25829 | 289 @end menu |
290 | |
291 @node Starting GUD | |
292 @subsection Starting GUD | |
293 | |
294 There are several commands for starting a debugger, each corresponding | |
295 to a particular debugger program. | |
296 | |
297 @table @kbd | |
298 @item M-x gdb @key{RET} @var{file} @key{RET} | |
299 @findex gdb | |
38490 | 300 Run GDB as a subprocess of Emacs. This command creates a buffer |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
301 for input and output to GDB, and switches to it. If a GDB buffer |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
302 already exists, it just switches to that buffer. |
25829 | 303 |
304 @item M-x dbx @key{RET} @var{file} @key{RET} | |
305 @findex dbx | |
38490 | 306 Similar, but run DBX instead of GDB. |
25829 | 307 |
308 @item M-x xdb @key{RET} @var{file} @key{RET} | |
309 @findex xdb | |
310 @vindex gud-xdb-directories | |
38490 | 311 Similar, but run XDB instead of GDB. Use the variable |
25829 | 312 @code{gud-xdb-directories} to specify directories to search for source |
313 files. | |
314 | |
315 @item M-x sdb @key{RET} @var{file} @key{RET} | |
316 @findex sdb | |
38490 | 317 Similar, but run SDB instead of GDB. |
25829 | 318 |
319 Some versions of SDB do not mention source file names in their | |
320 messages. When you use them, you need to have a valid tags table | |
321 (@pxref{Tags}) in order for GUD to find functions in the source code. | |
322 If you have not visited a tags table or the tags table doesn't list one | |
323 of the functions, you get a message saying @samp{The sdb support | |
324 requires a valid tags table to work}. If this happens, generate a valid | |
325 tags table in the working directory and try again. | |
326 | |
327 @item M-x perldb @key{RET} @var{file} @key{RET} | |
328 @findex perldb | |
329 Run the Perl interpreter in debug mode to debug @var{file}, a Perl program. | |
330 | |
331 @item M-x jdb @key{RET} @var{file} @key{RET} | |
332 @findex jdb | |
333 Run the Java debugger to debug @var{file}. | |
334 | |
335 @item M-x pdb @key{RET} @var{file} @key{RET} | |
336 @findex pdb | |
337 Run the Python debugger to debug @var{file}. | |
338 @end table | |
339 | |
340 Each of these commands takes one argument: a command line to invoke | |
341 the debugger. In the simplest case, specify just the name of the | |
342 executable file you want to debug. You may also use options that the | |
343 debugger supports. However, shell wildcards and variables are not | |
344 allowed. GUD assumes that the first argument not starting with a | |
345 @samp{-} is the executable file name. | |
346 | |
347 Emacs can only run one debugger process at a time. | |
348 | |
349 @node Debugger Operation | |
350 @subsection Debugger Operation | |
351 | |
42904
0e87fd2f82b4
(Debugger Operation): Add index entries for fringe usage.
Eli Zaretskii <eliz@gnu.org>
parents:
39820
diff
changeset
|
352 @cindex fringes, and current execution line in GUD |
25829 | 353 When you run a debugger with GUD, the debugger uses an Emacs buffer |
354 for its ordinary input and output. This is called the GUD buffer. The | |
355 debugger displays the source files of the program by visiting them in | |
356 Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates | |
42913 | 357 the current execution line.@footnote{Under a window system, the arrow |
358 appears in the left fringe of the Emacs window.} Moving point in this | |
359 buffer does not move the arrow. | |
25829 | 360 |
361 You can start editing these source files at any time in the buffers | |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
362 that display them. The arrow is not part of the file's |
25829 | 363 text; it appears only on the screen. If you do modify a source file, |
364 keep in mind that inserting or deleting lines will throw off the arrow's | |
365 positioning; GUD has no way of figuring out which line corresponded | |
366 before your changes to the line number in a debugger message. Also, | |
367 you'll typically have to recompile and restart the program for your | |
368 changes to be reflected in the debugger's tables. | |
369 | |
370 If you wish, you can control your debugger process entirely through the | |
371 debugger buffer, which uses a variant of Shell mode. All the usual | |
372 commands for your debugger are available, and you can use the Shell mode | |
373 history commands to repeat them. @xref{Shell Mode}. | |
374 | |
375 @node Commands of GUD | |
376 @subsection Commands of GUD | |
377 | |
378 The GUD interaction buffer uses a variant of Shell mode, so the | |
379 commands of Shell mode are available (@pxref{Shell Mode}). GUD mode | |
380 also provides commands for setting and clearing breakpoints, for | |
381 selecting stack frames, and for stepping through the program. These | |
382 commands are available both in the GUD buffer and globally, but with | |
383 different key bindings. | |
384 | |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
385 The breakpoint commands are normally used in source file buffers, |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
386 because that is the easiest way to specify where to set or clear the |
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
387 breakpoint. Here's the global command to set a breakpoint: |
25829 | 388 |
389 @table @kbd | |
390 @item C-x @key{SPC} | |
391 @kindex C-x SPC | |
392 Set a breakpoint on the source line that point is on. | |
393 @end table | |
394 | |
395 @kindex C-x C-a @r{(GUD)} | |
396 Here are the other special commands provided by GUD. The keys | |
397 starting with @kbd{C-c} are available only in the GUD interaction | |
398 buffer. The key bindings that start with @kbd{C-x C-a} are available in | |
399 the GUD interaction buffer and also in source files. | |
400 | |
401 @table @kbd | |
402 @item C-c C-l | |
403 @kindex C-c C-l @r{(GUD)} | |
404 @itemx C-x C-a C-l | |
405 @findex gud-refresh | |
406 Display in another window the last line referred to in the GUD | |
407 buffer (that is, the line indicated in the last location message). | |
408 This runs the command @code{gud-refresh}. | |
409 | |
410 @item C-c C-s | |
411 @kindex C-c C-s @r{(GUD)} | |
412 @itemx C-x C-a C-s | |
413 @findex gud-step | |
414 Execute a single line of code (@code{gud-step}). If the line contains | |
415 a function call, execution stops after entering the called function. | |
416 | |
417 @item C-c C-n | |
418 @kindex C-c C-n @r{(GUD)} | |
419 @itemx C-x C-a C-n | |
420 @findex gud-next | |
421 Execute a single line of code, stepping across entire function calls | |
422 at full speed (@code{gud-next}). | |
423 | |
424 @item C-c C-i | |
425 @kindex C-c C-i @r{(GUD)} | |
426 @itemx C-x C-a C-i | |
427 @findex gud-stepi | |
428 Execute a single machine instruction (@code{gud-stepi}). | |
429 | |
430 @need 3000 | |
431 @item C-c C-r | |
432 @kindex C-c C-r @r{(GUD)} | |
433 @itemx C-x C-a C-r | |
434 @findex gud-cont | |
435 Continue execution without specifying any stopping point. The program | |
436 will run until it hits a breakpoint, terminates, or gets a signal that | |
437 the debugger is checking for (@code{gud-cont}). | |
438 | |
439 @need 1000 | |
440 @item C-c C-d | |
441 @kindex C-c C-d @r{(GUD)} | |
442 @itemx C-x C-a C-d | |
443 @findex gud-remove | |
444 Delete the breakpoint(s) on the current source line, if any | |
445 (@code{gud-remove}). If you use this command in the GUD interaction | |
446 buffer, it applies to the line where the program last stopped. | |
447 | |
448 @item C-c C-t | |
449 @kindex C-c C-t @r{(GUD)} | |
450 @itemx C-x C-a C-t | |
451 @findex gud-tbreak | |
452 Set a temporary breakpoint on the current source line, if any. | |
453 If you use this command in the GUD interaction buffer, | |
454 it applies to the line where the program last stopped. | |
455 @end table | |
456 | |
457 The above commands are common to all supported debuggers. If you are | |
458 using GDB or (some versions of) DBX, these additional commands are available: | |
459 | |
460 @table @kbd | |
461 @item C-c < | |
462 @kindex C-c < @r{(GUD)} | |
463 @itemx C-x C-a < | |
464 @findex gud-up | |
465 Select the next enclosing stack frame (@code{gud-up}). This is | |
466 equivalent to the @samp{up} command. | |
467 | |
468 @item C-c > | |
469 @kindex C-c > @r{(GUD)} | |
470 @itemx C-x C-a > | |
471 @findex gud-down | |
472 Select the next inner stack frame (@code{gud-down}). This is | |
473 equivalent to the @samp{down} command. | |
474 @end table | |
475 | |
476 If you are using GDB, these additional key bindings are available: | |
477 | |
478 @table @kbd | |
479 @item @key{TAB} | |
480 @kindex TAB @r{(GUD)} | |
481 @findex gud-gdb-complete-command | |
482 With GDB, complete a symbol name (@code{gud-gdb-complete-command}). | |
483 This key is available only in the GUD interaction buffer, and requires | |
484 GDB versions 4.13 and later. | |
485 | |
486 @item C-c C-f | |
487 @kindex C-c C-f @r{(GUD)} | |
488 @itemx C-x C-a C-f | |
489 @findex gud-finish | |
490 Run the program until the selected stack frame returns (or until it | |
491 stops for some other reason). | |
43137
bc055bf06a94
(Commands of GUD): Add gud-jump.
Richard M. Stallman <rms@gnu.org>
parents:
42913
diff
changeset
|
492 |
46238
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
493 @item C-x C-a C-j |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
494 @kindex C-x C-a C-j @r{(GUD)} |
43137
bc055bf06a94
(Commands of GUD): Add gud-jump.
Richard M. Stallman <rms@gnu.org>
parents:
42913
diff
changeset
|
495 @findex gud-jump |
46238
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
496 Only useful in a source buffer, (@code{gud-jump}) transfers the |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
497 program's execution point to the current line. In other words, the |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
498 next line that the program executes will be the one where you gave the |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
499 command. If the new execution line is in a different function from |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
500 the previously one, GDB prompts for confirmation since the results may |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
501 be bizarre. See the GDB manual entry regarding @code{jump} for |
f5ac68c7cc15
Clarify gud-jump description.
Richard M. Stallman <rms@gnu.org>
parents:
44116
diff
changeset
|
502 details. |
25829 | 503 @end table |
504 | |
505 These commands interpret a numeric argument as a repeat count, when | |
506 that makes sense. | |
507 | |
508 Because @key{TAB} serves as a completion command, you can't use it to | |
509 enter a tab as input to the program you are debugging with GDB. | |
510 Instead, type @kbd{C-q @key{TAB}} to enter a tab. | |
511 | |
512 @node GUD Customization | |
513 @subsection GUD Customization | |
514 | |
515 @vindex gdb-mode-hook | |
516 @vindex dbx-mode-hook | |
517 @vindex sdb-mode-hook | |
518 @vindex xdb-mode-hook | |
519 @vindex perldb-mode-hook | |
520 @vindex pdb-mode-hook | |
521 @vindex jdb-mode-hook | |
522 On startup, GUD runs one of the following hooks: @code{gdb-mode-hook}, | |
523 if you are using GDB; @code{dbx-mode-hook}, if you are using DBX; | |
524 @code{sdb-mode-hook}, if you are using SDB; @code{xdb-mode-hook}, if you | |
525 are using XDB; @code{perldb-mode-hook}, for Perl debugging mode; | |
37482
4b43d9f652aa
Correct typo on pdb-mode-hook.
Richard M. Stallman <rms@gnu.org>
parents:
37346
diff
changeset
|
526 @code{pdb-mode-hook}, for PDB; @code{jdb-mode-hook}, for JDB. You can |
25829 | 527 use these hooks to define custom key bindings for the debugger |
528 interaction buffer. @xref{Hooks}. | |
529 | |
530 Here is a convenient way to define a command that sends a particular | |
531 command string to the debugger, and set up a key binding for it in the | |
532 debugger interaction buffer: | |
533 | |
534 @findex gud-def | |
535 @example | |
536 (gud-def @var{function} @var{cmdstring} @var{binding} @var{docstring}) | |
537 @end example | |
538 | |
539 This defines a command named @var{function} which sends | |
540 @var{cmdstring} to the debugger process, and gives it the documentation | |
38743 | 541 string @var{docstring}. You can then use the command @var{function} in any |
25829 | 542 buffer. If @var{binding} is non-@code{nil}, @code{gud-def} also binds |
543 the command to @kbd{C-c @var{binding}} in the GUD buffer's mode and to | |
544 @kbd{C-x C-a @var{binding}} generally. | |
545 | |
546 The command string @var{cmdstring} may contain certain | |
547 @samp{%}-sequences that stand for data to be filled in at the time | |
548 @var{function} is called: | |
549 | |
550 @table @samp | |
551 @item %f | |
552 The name of the current source file. If the current buffer is the GUD | |
553 buffer, then the ``current source file'' is the file that the program | |
554 stopped in. | |
555 @c This said, ``the name of the file the program counter was in at the last breakpoint.'' | |
556 @c But I suspect it is really the last stop file. | |
557 | |
558 @item %l | |
559 The number of the current source line. If the current buffer is the GUD | |
560 buffer, then the ``current source line'' is the line that the program | |
561 stopped in. | |
562 | |
563 @item %e | |
564 The text of the C lvalue or function-call expression at or adjacent to point. | |
565 | |
566 @item %a | |
567 The text of the hexadecimal address at or adjacent to point. | |
568 | |
569 @item %p | |
570 The numeric argument of the called function, as a decimal number. If | |
571 the command is used without a numeric argument, @samp{%p} stands for the | |
572 empty string. | |
573 | |
574 If you don't use @samp{%p} in the command string, the command you define | |
575 ignores any numeric argument. | |
576 @end table | |
577 | |
27223 | 578 @node GUD Tooltips |
579 @subsection GUD Tooltips | |
580 | |
581 @cindex tooltips with GUD | |
582 The Tooltip facility (@pxref{Tooltips}) provides support for GUD@. If | |
583 GUD support is activated by customizing the @code{tooltip} group, | |
584 variable values can be displayed in tooltips by pointing at them with | |
585 the mouse in the GUD buffer or in source buffers with major modes in the | |
586 customizable list @code{tooltip-gud-modes}. | |
587 | |
25829 | 588 @node Executing Lisp |
589 @section Executing Lisp Expressions | |
590 | |
591 Emacs has several different major modes for Lisp and Scheme. They are | |
592 the same in terms of editing commands, but differ in the commands for | |
593 executing Lisp expressions. Each mode has its own purpose. | |
594 | |
595 @table @asis | |
596 @item Emacs-Lisp mode | |
597 The mode for editing source files of programs to run in Emacs Lisp. | |
598 This mode defines @kbd{C-M-x} to evaluate the current defun. | |
599 @xref{Lisp Libraries}. | |
600 @item Lisp Interaction mode | |
601 The mode for an interactive session with Emacs Lisp. It defines | |
602 @kbd{C-j} to evaluate the sexp before point and insert its value in the | |
603 buffer. @xref{Lisp Interaction}. | |
604 @item Lisp mode | |
605 The mode for editing source files of programs that run in Lisps other | |
606 than Emacs Lisp. This mode defines @kbd{C-M-x} to send the current defun | |
607 to an inferior Lisp process. @xref{External Lisp}. | |
608 @item Inferior Lisp mode | |
609 The mode for an interactive session with an inferior Lisp process. | |
610 This mode combines the special features of Lisp mode and Shell mode | |
611 (@pxref{Shell Mode}). | |
612 @item Scheme mode | |
613 Like Lisp mode but for Scheme programs. | |
614 @item Inferior Scheme mode | |
615 The mode for an interactive session with an inferior Scheme process. | |
616 @end table | |
617 | |
618 Most editing commands for working with Lisp programs are in fact | |
619 available globally. @xref{Programs}. | |
620 | |
621 @node Lisp Libraries | |
622 @section Libraries of Lisp Code for Emacs | |
623 @cindex libraries | |
624 @cindex loading Lisp code | |
625 | |
626 Lisp code for Emacs editing commands is stored in files whose names | |
627 conventionally end in @file{.el}. This ending tells Emacs to edit them in | |
628 Emacs-Lisp mode (@pxref{Executing Lisp}). | |
629 | |
630 @findex load-file | |
631 To execute a file of Emacs Lisp code, use @kbd{M-x load-file}. This | |
632 command reads a file name using the minibuffer and then executes the | |
633 contents of that file as Lisp code. It is not necessary to visit the | |
634 file first; in any case, this command reads the file as found on disk, | |
635 not text in an Emacs buffer. | |
636 | |
637 @findex load | |
638 @findex load-library | |
639 Once a file of Lisp code is installed in the Emacs Lisp library | |
640 directories, users can load it using @kbd{M-x load-library}. Programs can | |
641 load it by calling @code{load-library}, or with @code{load}, a more primitive | |
642 function that is similar but accepts some additional arguments. | |
643 | |
644 @kbd{M-x load-library} differs from @kbd{M-x load-file} in that it | |
645 searches a sequence of directories and tries three file names in each | |
646 directory. Suppose your argument is @var{lib}; the three names are | |
647 @file{@var{lib}.elc}, @file{@var{lib}.el}, and lastly just | |
648 @file{@var{lib}}. If @file{@var{lib}.elc} exists, it is by convention | |
649 the result of compiling @file{@var{lib}.el}; it is better to load the | |
650 compiled file, since it will load and run faster. | |
651 | |
652 If @code{load-library} finds that @file{@var{lib}.el} is newer than | |
38943
4dd9aeae2f84
Don't use "prints" except for printers.
Richard M. Stallman <rms@gnu.org>
parents:
38743
diff
changeset
|
653 @file{@var{lib}.elc} file, it issues a warning, because it's likely that |
25829 | 654 somebody made changes to the @file{.el} file and forgot to recompile |
655 it. | |
656 | |
657 Because the argument to @code{load-library} is usually not in itself | |
658 a valid file name, file name completion is not available. Indeed, when | |
659 using this command, you usually do not know exactly what file name | |
660 will be used. | |
661 | |
662 @vindex load-path | |
663 The sequence of directories searched by @kbd{M-x load-library} is | |
664 specified by the variable @code{load-path}, a list of strings that are | |
665 directory names. The default value of the list contains the directory where | |
666 the Lisp code for Emacs itself is stored. If you have libraries of | |
667 your own, put them in a single directory and add that directory | |
668 to @code{load-path}. @code{nil} in this list stands for the current default | |
669 directory, but it is probably not a good idea to put @code{nil} in the | |
670 list. If you find yourself wishing that @code{nil} were in the list, | |
671 most likely what you really want to do is use @kbd{M-x load-file} | |
672 this once. | |
673 | |
674 @cindex autoload | |
675 Often you do not have to give any command to load a library, because | |
676 the commands defined in the library are set up to @dfn{autoload} that | |
677 library. Trying to run any of those commands calls @code{load} to load | |
678 the library; this replaces the autoload definitions with the real ones | |
679 from the library. | |
680 | |
681 @cindex byte code | |
682 Emacs Lisp code can be compiled into byte-code which loads faster, | |
683 takes up less space when loaded, and executes faster. @xref{Byte | |
684 Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference Manual}. | |
685 By convention, the compiled code for a library goes in a separate file | |
686 whose name consists of the library source file with @samp{c} appended. | |
687 Thus, the compiled code for @file{foo.el} goes in @file{foo.elc}. | |
688 That's why @code{load-library} searches for @samp{.elc} files first. | |
689 | |
31027
561ef681eab5
Document load-dangerous-libraries.
Eli Zaretskii <eliz@gnu.org>
parents:
28431
diff
changeset
|
690 @vindex load-dangerous-libraries |
561ef681eab5
Document load-dangerous-libraries.
Eli Zaretskii <eliz@gnu.org>
parents:
28431
diff
changeset
|
691 @cindex Lisp files byte-compiled by XEmacs |
36144
22f75550e788
Rewrite discussion of load-dangerous-libraries.
Richard M. Stallman <rms@gnu.org>
parents:
34935
diff
changeset
|
692 By default, Emacs refuses to load compiled Lisp files which were |
22f75550e788
Rewrite discussion of load-dangerous-libraries.
Richard M. Stallman <rms@gnu.org>
parents:
34935
diff
changeset
|
693 compiled with XEmacs, a modified versions of Emacs---they can cause |
22f75550e788
Rewrite discussion of load-dangerous-libraries.
Richard M. Stallman <rms@gnu.org>
parents:
34935
diff
changeset
|
694 Emacs to crash. Set the variable @code{load-dangerous-libraries} to |
22f75550e788
Rewrite discussion of load-dangerous-libraries.
Richard M. Stallman <rms@gnu.org>
parents:
34935
diff
changeset
|
695 @code{t} if you want to try loading them. |
31027
561ef681eab5
Document load-dangerous-libraries.
Eli Zaretskii <eliz@gnu.org>
parents:
28431
diff
changeset
|
696 |
25829 | 697 @node Lisp Eval |
698 @section Evaluating Emacs-Lisp Expressions | |
699 @cindex Emacs-Lisp mode | |
700 @cindex mode, Emacs-Lisp | |
701 | |
702 @findex emacs-lisp-mode | |
703 Lisp programs intended to be run in Emacs should be edited in | |
704 Emacs-Lisp mode; this happens automatically for file names ending in | |
705 @file{.el}. By contrast, Lisp mode itself is used for editing Lisp | |
706 programs intended for other Lisp systems. To switch to Emacs-Lisp mode | |
707 explicitly, use the command @kbd{M-x emacs-lisp-mode}. | |
708 | |
709 For testing of Lisp programs to run in Emacs, it is often useful to | |
710 evaluate part of the program as it is found in the Emacs buffer. For | |
711 example, after changing the text of a Lisp function definition, | |
712 evaluating the definition installs the change for future calls to the | |
713 function. Evaluation of Lisp expressions is also useful in any kind of | |
714 editing, for invoking noninteractive functions (functions that are | |
715 not commands). | |
716 | |
717 @table @kbd | |
718 @item M-: | |
719 Read a single Lisp expression in the minibuffer, evaluate it, and print | |
720 the value in the echo area (@code{eval-expression}). | |
721 @item C-x C-e | |
722 Evaluate the Lisp expression before point, and print the value in the | |
723 echo area (@code{eval-last-sexp}). | |
724 @item C-M-x | |
725 Evaluate the defun containing or after point, and print the value in | |
726 the echo area (@code{eval-defun}). | |
727 @item M-x eval-region | |
728 Evaluate all the Lisp expressions in the region. | |
729 @item M-x eval-current-buffer | |
730 Evaluate all the Lisp expressions in the buffer. | |
731 @end table | |
732 | |
44116
1fc0cc0bb3ab
Use `colon' instead of `:' in an index only in the Info version.
Eli Zaretskii <eliz@gnu.org>
parents:
43889
diff
changeset
|
733 @ifinfo |
43889
c5ea7e769ffd
(Electric C, Lisp Eval): Avoid makeinfo warnings about colons in indices.
Eli Zaretskii <eliz@gnu.org>
parents:
43151
diff
changeset
|
734 @c This uses ``colon'' instead of a literal `:' because Info cannot |
c5ea7e769ffd
(Electric C, Lisp Eval): Avoid makeinfo warnings about colons in indices.
Eli Zaretskii <eliz@gnu.org>
parents:
43151
diff
changeset
|
735 @c cope with a `:' in a menu |
c5ea7e769ffd
(Electric C, Lisp Eval): Avoid makeinfo warnings about colons in indices.
Eli Zaretskii <eliz@gnu.org>
parents:
43151
diff
changeset
|
736 @kindex M-@key{colon} |
44116
1fc0cc0bb3ab
Use `colon' instead of `:' in an index only in the Info version.
Eli Zaretskii <eliz@gnu.org>
parents:
43889
diff
changeset
|
737 @end ifinfo |
1fc0cc0bb3ab
Use `colon' instead of `:' in an index only in the Info version.
Eli Zaretskii <eliz@gnu.org>
parents:
43889
diff
changeset
|
738 @ifnotinfo |
1fc0cc0bb3ab
Use `colon' instead of `:' in an index only in the Info version.
Eli Zaretskii <eliz@gnu.org>
parents:
43889
diff
changeset
|
739 @kindex M-: |
1fc0cc0bb3ab
Use `colon' instead of `:' in an index only in the Info version.
Eli Zaretskii <eliz@gnu.org>
parents:
43889
diff
changeset
|
740 @end ifnotinfo |
25829 | 741 @findex eval-expression |
742 @kbd{M-:} (@code{eval-expression}) is the most basic command for evaluating | |
743 a Lisp expression interactively. It reads the expression using the | |
744 minibuffer, so you can execute any expression on a buffer regardless of | |
745 what the buffer contains. When the expression is evaluated, the current | |
746 buffer is once again the buffer that was current when @kbd{M-:} was | |
747 typed. | |
748 | |
749 @kindex C-M-x @r{(Emacs-Lisp mode)} | |
750 @findex eval-defun | |
751 In Emacs-Lisp mode, the key @kbd{C-M-x} is bound to the command | |
752 @code{eval-defun}, which parses the defun containing or following point | |
753 as a Lisp expression and evaluates it. The value is printed in the echo | |
754 area. This command is convenient for installing in the Lisp environment | |
755 changes that you have just made in the text of a function definition. | |
756 | |
757 @kbd{C-M-x} treats @code{defvar} expressions specially. Normally, | |
758 evaluating a @code{defvar} expression does nothing if the variable it | |
759 defines already has a value. But @kbd{C-M-x} unconditionally resets the | |
760 variable to the initial value specified in the @code{defvar} expression. | |
28431
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
761 @code{defcustom} expressions are treated similarly. |
25829 | 762 This special feature is convenient for debugging Lisp programs. |
763 | |
764 @kindex C-x C-e | |
765 @findex eval-last-sexp | |
766 The command @kbd{C-x C-e} (@code{eval-last-sexp}) evaluates the Lisp | |
767 expression preceding point in the buffer, and displays the value in the | |
768 echo area. It is available in all major modes, not just Emacs-Lisp | |
769 mode. It does not treat @code{defvar} specially. | |
770 | |
771 If @kbd{C-M-x}, @kbd{C-x C-e}, or @kbd{M-:} is given a numeric | |
772 argument, it inserts the value into the current buffer at point, rather | |
773 than displaying it in the echo area. The argument's value does not | |
774 matter. | |
775 | |
776 @findex eval-region | |
777 @findex eval-current-buffer | |
778 The most general command for evaluating Lisp expressions from a buffer | |
779 is @code{eval-region}. @kbd{M-x eval-region} parses the text of the | |
780 region as one or more Lisp expressions, evaluating them one by one. | |
781 @kbd{M-x eval-current-buffer} is similar but evaluates the entire | |
782 buffer. This is a reasonable way to install the contents of a file of | |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38202
diff
changeset
|
783 Lisp code that you are ready to test. Later, as you find bugs and |
25829 | 784 change individual functions, use @kbd{C-M-x} on each function that you |
785 change. This keeps the Lisp world in step with the source file. | |
786 | |
28431
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
787 @vindex eval-expression-print-level |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
788 @vindex eval-expression-print-length |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
789 @vindex eval-expression-debug-on-error |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
790 The customizable variables @code{eval-expression-print-level} and |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
791 @code{eval-expression-print-length} control the maximum depth and length |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
792 of lists to print in the result of the evaluation commands before |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
793 abbreviating them. @code{eval-expression-debug-on-error} controls |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
794 whether evaluation errors invoke the debugger when these commands are |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
795 used. |
315d6e79ea38
Overlay arrow in margin. eval-expression variables.
Dave Love <fx@gnu.org>
parents:
27223
diff
changeset
|
796 |
25829 | 797 @node Lisp Interaction |
798 @section Lisp Interaction Buffers | |
799 | |
800 The buffer @samp{*scratch*} which is selected when Emacs starts up is | |
801 provided for evaluating Lisp expressions interactively inside Emacs. | |
802 | |
803 The simplest way to use the @samp{*scratch*} buffer is to insert Lisp | |
804 expressions and type @kbd{C-j} after each expression. This command | |
805 reads the Lisp expression before point, evaluates it, and inserts the | |
806 value in printed representation before point. The result is a complete | |
807 typescript of the expressions you have evaluated and their values. | |
808 | |
809 The @samp{*scratch*} buffer's major mode is Lisp Interaction mode, which | |
810 is the same as Emacs-Lisp mode except for the binding of @kbd{C-j}. | |
811 | |
812 @findex lisp-interaction-mode | |
813 The rationale for this feature is that Emacs must have a buffer when | |
814 it starts up, but that buffer is not useful for editing files since a | |
815 new buffer is made for every file that you visit. The Lisp interpreter | |
816 typescript is the most useful thing I can think of for the initial | |
817 buffer to do. Type @kbd{M-x lisp-interaction-mode} to put the current | |
818 buffer in Lisp Interaction mode. | |
819 | |
820 @findex ielm | |
821 An alternative way of evaluating Emacs Lisp expressions interactively | |
822 is to use Inferior Emacs-Lisp mode, which provides an interface rather | |
823 like Shell mode (@pxref{Shell Mode}) for evaluating Emacs Lisp | |
824 expressions. Type @kbd{M-x ielm} to create an @samp{*ielm*} buffer | |
825 which uses this mode. | |
826 | |
827 @node External Lisp | |
828 @section Running an External Lisp | |
829 | |
830 Emacs has facilities for running programs in other Lisp systems. You can | |
831 run a Lisp process as an inferior of Emacs, and pass expressions to it to | |
832 be evaluated. You can also pass changed function definitions directly from | |
833 the Emacs buffers in which you edit the Lisp programs to the inferior Lisp | |
834 process. | |
835 | |
836 @findex run-lisp | |
837 @vindex inferior-lisp-program | |
838 @kindex C-x C-z | |
839 To run an inferior Lisp process, type @kbd{M-x run-lisp}. This runs | |
840 the program named @code{lisp}, the same program you would run by typing | |
841 @code{lisp} as a shell command, with both input and output going through | |
842 an Emacs buffer named @samp{*lisp*}. That is to say, any ``terminal | |
843 output'' from Lisp will go into the buffer, advancing point, and any | |
844 ``terminal input'' for Lisp comes from text in the buffer. (You can | |
845 change the name of the Lisp executable file by setting the variable | |
846 @code{inferior-lisp-program}.) | |
847 | |
848 To give input to Lisp, go to the end of the buffer and type the input, | |
849 terminated by @key{RET}. The @samp{*lisp*} buffer is in Inferior Lisp | |
850 mode, which combines the special characteristics of Lisp mode with most | |
851 of the features of Shell mode (@pxref{Shell Mode}). The definition of | |
852 @key{RET} to send a line to a subprocess is one of the features of Shell | |
853 mode. | |
854 | |
855 @findex lisp-mode | |
856 For the source files of programs to run in external Lisps, use Lisp | |
857 mode. This mode can be selected with @kbd{M-x lisp-mode}, and is used | |
858 automatically for files whose names end in @file{.l}, @file{.lsp}, or | |
859 @file{.lisp}, as most Lisp systems usually expect. | |
860 | |
861 @kindex C-M-x @r{(Lisp mode)} | |
862 @findex lisp-eval-defun | |
863 When you edit a function in a Lisp program you are running, the easiest | |
864 way to send the changed definition to the inferior Lisp process is the key | |
865 @kbd{C-M-x}. In Lisp mode, this runs the function @code{lisp-eval-defun}, | |
866 which finds the defun around or following point and sends it as input to | |
867 the Lisp process. (Emacs can send input to any inferior process regardless | |
868 of what buffer is current.) | |
869 | |
870 Contrast the meanings of @kbd{C-M-x} in Lisp mode (for editing programs | |
871 to be run in another Lisp system) and Emacs-Lisp mode (for editing Lisp | |
872 programs to be run in Emacs): in both modes it has the effect of installing | |
873 the function definition that point is in, but the way of doing so is | |
874 different according to where the relevant Lisp environment is found. | |
875 @xref{Executing Lisp}. |