Commit | Line | Data |
---|---|---|
a44af9f2 RS |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
fd897522 | 3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1998, 1999 |
88510b17 | 4 | @c Free Software Foundation, Inc. |
a44af9f2 RS |
5 | @c See the file elisp.texi for copying conditions. |
6 | @setfilename ../info/internals | |
7 | @node GNU Emacs Internals, Standard Errors, Tips, Top | |
8 | @comment node-name, next, previous, up | |
9 | @appendix GNU Emacs Internals | |
10 | ||
11 | This chapter describes how the runnable Emacs executable is dumped with | |
12 | the preloaded Lisp libraries in it, how storage is allocated, and some | |
13 | internal aspects of GNU Emacs that may be of interest to C programmers. | |
14 | ||
15 | @menu | |
969fe9b5 | 16 | * Building Emacs:: How to the dumped Emacs is made. |
a44af9f2 RS |
17 | * Pure Storage:: A kludge to make preloaded Lisp functions sharable. |
18 | * Garbage Collection:: Reclaiming space for Lisp objects no longer used. | |
969fe9b5 | 19 | * Memory Usage:: Info about total size of Lisp objects made so far. |
a44af9f2 RS |
20 | * Writing Emacs Primitives:: Writing C code for Emacs. |
21 | * Object Internals:: Data formats of buffers, windows, processes. | |
22 | @end menu | |
23 | ||
969fe9b5 | 24 | @node Building Emacs |
a44af9f2 RS |
25 | @appendixsec Building Emacs |
26 | @cindex building Emacs | |
27 | @pindex temacs | |
28 | ||
29 | This section explains the steps involved in building the Emacs | |
30 | executable. You don't have to know this material to build and install | |
31 | Emacs, since the makefiles do all these things automatically. This | |
32 | information is pertinent to Emacs maintenance. | |
33 | ||
34 | Compilation of the C source files in the @file{src} directory | |
35 | produces an executable file called @file{temacs}, also called a | |
36 | @dfn{bare impure Emacs}. It contains the Emacs Lisp interpreter and I/O | |
37 | routines, but not the editing commands. | |
38 | ||
39 | @cindex @file{loadup.el} | |
40 | The command @w{@samp{temacs -l loadup}} uses @file{temacs} to create | |
41 | the real runnable Emacs executable. These arguments direct | |
42 | @file{temacs} to evaluate the Lisp files specified in the file | |
43 | @file{loadup.el}. These files set up the normal Emacs editing | |
574efc83 | 44 | environment, resulting in an Emacs that is still impure but no longer |
a44af9f2 RS |
45 | bare. |
46 | ||
47 | It takes a substantial time to load the standard Lisp files. Luckily, | |
48 | you don't have to do this each time you run Emacs; @file{temacs} can | |
574efc83 | 49 | dump out an executable program called @file{emacs} that has these files |
a44af9f2 RS |
50 | preloaded. @file{emacs} starts more quickly because it does not need to |
51 | load the files. This is the Emacs executable that is normally | |
52 | installed. | |
53 | ||
54 | To create @file{emacs}, use the command @samp{temacs -batch -l loadup | |
55 | dump}. The purpose of @samp{-batch} here is to prevent @file{temacs} | |
56 | from trying to initialize any of its data on the terminal; this ensures | |
57 | that the tables of terminal information are empty in the dumped Emacs. | |
58 | The argument @samp{dump} tells @file{loadup.el} to dump a new executable | |
59 | named @file{emacs}. | |
60 | ||
61 | Some operating systems don't support dumping. On those systems, you | |
62 | must start Emacs with the @samp{temacs -l loadup} command each time you | |
a890e1b0 RS |
63 | use it. This takes a substantial time, but since you need to start |
64 | Emacs once a day at most---or once a week if you never log out---the | |
65 | extra time is not too severe a problem. | |
a44af9f2 RS |
66 | |
67 | @cindex @file{site-load.el} | |
95260b26 | 68 | |
a44af9f2 | 69 | You can specify additional files to preload by writing a library named |
95260b26 GM |
70 | @file{site-load.el} that loads them. You may need to add a definition |
71 | ||
72 | @example | |
73 | #define SITELOAD_PURESIZE_EXTRA @var{n} | |
74 | @end example | |
75 | ||
76 | @noindent | |
77 | to make @var{n} added bytes of pure space to hold the additional files. | |
78 | (Try adding increments of 20000 until it is big enough.) However, the | |
79 | advantage of preloading additional files decreases as machines get | |
80 | faster. On modern machines, it is usually not advisable. | |
a44af9f2 | 81 | |
2a664e73 RS |
82 | After @file{loadup.el} reads @file{site-load.el}, it finds the |
83 | documentation strings for primitive and preloaded functions (and | |
84 | variables) in the file @file{etc/DOC} where they are stored, by calling | |
85 | @code{Snarf-documentation} (@pxref{Accessing Documentation}). | |
86 | ||
a44af9f2 | 87 | @cindex @file{site-init.el} |
a890e1b0 | 88 | You can specify other Lisp expressions to execute just before dumping |
2a664e73 RS |
89 | by putting them in a library named @file{site-init.el}. This file is |
90 | executed after the documentation strings are found. | |
a44af9f2 | 91 | |
2a664e73 RS |
92 | If you want to preload function or variable definitions, there are |
93 | three ways you can do this and make their documentation strings | |
94 | accessible when you subsequently run Emacs: | |
95 | ||
96 | @itemize @bullet | |
97 | @item | |
98 | Arrange to scan these files when producing the @file{etc/DOC} file, | |
99 | and load them with @file{site-load.el}. | |
100 | ||
101 | @item | |
102 | Load the files with @file{site-init.el}, then copy the files into the | |
103 | installation directory for Lisp files when you install Emacs. | |
104 | ||
105 | @item | |
106 | Specify a non-@code{nil} value for | |
8241495d | 107 | @code{byte-compile-dynamic-docstrings} as a local variable in each of these |
2a664e73 RS |
108 | files, and load them with either @file{site-load.el} or |
109 | @file{site-init.el}. (This method has the drawback that the | |
110 | documentation strings take up space in Emacs all the time.) | |
111 | @end itemize | |
112 | ||
113 | It is not advisable to put anything in @file{site-load.el} or | |
114 | @file{site-init.el} that would alter any of the features that users | |
115 | expect in an ordinary unmodified Emacs. If you feel you must override | |
116 | normal features for your site, do it with @file{default.el}, so that | |
8241495d | 117 | users can override your changes if they wish. @xref{Startup Summary}. |
a44af9f2 RS |
118 | |
119 | @defun dump-emacs to-file from-file | |
120 | @cindex unexec | |
cb017dde | 121 | This function dumps the current state of Emacs into an executable file |
a44af9f2 RS |
122 | @var{to-file}. It takes symbols from @var{from-file} (this is normally |
123 | the executable file @file{temacs}). | |
124 | ||
cb017dde RS |
125 | If you want to use this function in an Emacs that was already dumped, |
126 | you must run Emacs with @samp{-batch}. | |
a44af9f2 RS |
127 | @end defun |
128 | ||
969fe9b5 | 129 | @node Pure Storage |
a44af9f2 RS |
130 | @appendixsec Pure Storage |
131 | @cindex pure storage | |
132 | ||
a890e1b0 RS |
133 | Emacs Lisp uses two kinds of storage for user-created Lisp objects: |
134 | @dfn{normal storage} and @dfn{pure storage}. Normal storage is where | |
8241495d | 135 | all the new data created during an Emacs session are kept; see the |
574efc83 RS |
136 | following section for information on normal storage. Pure storage is |
137 | used for certain data in the preloaded standard Lisp files---data that | |
138 | should never change during actual use of Emacs. | |
a44af9f2 RS |
139 | |
140 | Pure storage is allocated only while @file{temacs} is loading the | |
141 | standard preloaded Lisp libraries. In the file @file{emacs}, it is | |
574efc83 | 142 | marked as read-only (on operating systems that permit this), so that |
a44af9f2 RS |
143 | the memory space can be shared by all the Emacs jobs running on the |
144 | machine at once. Pure storage is not expandable; a fixed amount is | |
145 | allocated when Emacs is compiled, and if that is not sufficient for the | |
a890e1b0 RS |
146 | preloaded libraries, @file{temacs} crashes. If that happens, you must |
147 | increase the compilation parameter @code{PURESIZE} in the file | |
a44af9f2 RS |
148 | @file{src/puresize.h}. This normally won't happen unless you try to |
149 | preload additional libraries or add features to the standard ones. | |
150 | ||
151 | @defun purecopy object | |
8241495d RS |
152 | This function makes a copy in pure storage of @var{object}, and returns |
153 | it. It copies a string by simply making a new string with the same | |
a44af9f2 | 154 | characters in pure storage. It recursively copies the contents of |
a890e1b0 RS |
155 | vectors and cons cells. It does not make copies of other objects such |
156 | as symbols, but just returns them unchanged. It signals an error if | |
a44af9f2 RS |
157 | asked to copy markers. |
158 | ||
c2cd5fb7 RS |
159 | This function is a no-op except while Emacs is being built and dumped; |
160 | it is usually called only in the file @file{emacs/lisp/loaddefs.el}, but | |
161 | a few packages call it just in case you decide to preload them. | |
a44af9f2 RS |
162 | @end defun |
163 | ||
164 | @defvar pure-bytes-used | |
a890e1b0 | 165 | The value of this variable is the number of bytes of pure storage |
a44af9f2 RS |
166 | allocated so far. Typically, in a dumped Emacs, this number is very |
167 | close to the total amount of pure storage available---if it were not, | |
168 | we would preallocate less. | |
169 | @end defvar | |
170 | ||
171 | @defvar purify-flag | |
a890e1b0 | 172 | This variable determines whether @code{defun} should make a copy of the |
a44af9f2 RS |
173 | function definition in pure storage. If it is non-@code{nil}, then the |
174 | function definition is copied into pure storage. | |
175 | ||
a890e1b0 | 176 | This flag is @code{t} while loading all of the basic functions for |
a44af9f2 | 177 | building Emacs initially (allowing those functions to be sharable and |
a890e1b0 RS |
178 | non-collectible). Dumping Emacs as an executable always writes |
179 | @code{nil} in this variable, regardless of the value it actually has | |
180 | before and after dumping. | |
a44af9f2 | 181 | |
a890e1b0 | 182 | You should not change this flag in a running Emacs. |
a44af9f2 RS |
183 | @end defvar |
184 | ||
969fe9b5 | 185 | @node Garbage Collection |
a44af9f2 RS |
186 | @appendixsec Garbage Collection |
187 | @cindex garbage collector | |
188 | ||
189 | @cindex memory allocation | |
190 | When a program creates a list or the user defines a new function (such | |
a890e1b0 RS |
191 | as by loading a library), that data is placed in normal storage. If |
192 | normal storage runs low, then Emacs asks the operating system to | |
a44af9f2 | 193 | allocate more memory in blocks of 1k bytes. Each block is used for one |
a890e1b0 RS |
194 | type of Lisp object, so symbols, cons cells, markers, etc., are |
195 | segregated in distinct blocks in memory. (Vectors, long strings, | |
196 | buffers and certain other editing types, which are fairly large, are | |
197 | allocated in individual blocks, one per object, while small strings are | |
198 | packed into blocks of 8k bytes.) | |
199 | ||
200 | It is quite common to use some storage for a while, then release it by | |
201 | (for example) killing a buffer or deleting the last pointer to an | |
a44af9f2 RS |
202 | object. Emacs provides a @dfn{garbage collector} to reclaim this |
203 | abandoned storage. (This name is traditional, but ``garbage recycler'' | |
204 | might be a more intuitive metaphor for this facility.) | |
205 | ||
a890e1b0 RS |
206 | The garbage collector operates by finding and marking all Lisp objects |
207 | that are still accessible to Lisp programs. To begin with, it assumes | |
208 | all the symbols, their values and associated function definitions, and | |
574efc83 | 209 | any data presently on the stack, are accessible. Any objects that can |
a890e1b0 RS |
210 | be reached indirectly through other accessible objects are also |
211 | accessible. | |
a44af9f2 | 212 | |
a890e1b0 | 213 | When marking is finished, all objects still unmarked are garbage. No |
a44af9f2 | 214 | matter what the Lisp program or the user does, it is impossible to refer |
a890e1b0 | 215 | to them, since there is no longer a way to reach them. Their space |
574efc83 RS |
216 | might as well be reused, since no one will miss them. The second |
217 | (``sweep'') phase of the garbage collector arranges to reuse them. | |
a44af9f2 | 218 | |
05aea714 | 219 | @c ??? Maybe add something describing weak hash tables here? |
95260b26 | 220 | |
a44af9f2 | 221 | @cindex free list |
a890e1b0 RS |
222 | The sweep phase puts unused cons cells onto a @dfn{free list} |
223 | for future allocation; likewise for symbols and markers. It compacts | |
224 | the accessible strings so they occupy fewer 8k blocks; then it frees the | |
574efc83 | 225 | other 8k blocks. Vectors, buffers, windows, and other large objects are |
a890e1b0 | 226 | individually allocated and freed using @code{malloc} and @code{free}. |
a44af9f2 RS |
227 | |
228 | @cindex CL note---allocate more storage | |
229 | @quotation | |
574efc83 | 230 | @b{Common Lisp note:} Unlike other Lisps, GNU Emacs Lisp does not |
a44af9f2 RS |
231 | call the garbage collector when the free list is empty. Instead, it |
232 | simply requests the operating system to allocate more storage, and | |
233 | processing continues until @code{gc-cons-threshold} bytes have been | |
234 | used. | |
235 | ||
236 | This means that you can make sure that the garbage collector will not | |
237 | run during a certain portion of a Lisp program by calling the garbage | |
238 | collector explicitly just before it (provided that portion of the | |
239 | program does not use so much space as to force a second garbage | |
240 | collection). | |
241 | @end quotation | |
242 | ||
243 | @deffn Command garbage-collect | |
a890e1b0 | 244 | This command runs a garbage collection, and returns information on |
a44af9f2 RS |
245 | the amount of space in use. (Garbage collection can also occur |
246 | spontaneously if you use more than @code{gc-cons-threshold} bytes of | |
247 | Lisp data since the previous garbage collection.) | |
248 | ||
a890e1b0 | 249 | @code{garbage-collect} returns a list containing the following |
a44af9f2 RS |
250 | information: |
251 | ||
a890e1b0 | 252 | @example |
a44af9f2 RS |
253 | @group |
254 | ((@var{used-conses} . @var{free-conses}) | |
255 | (@var{used-syms} . @var{free-syms}) | |
a890e1b0 | 256 | @end group |
969fe9b5 | 257 | (@var{used-miscs} . @var{free-miscs}) |
40d48fe9 | 258 | @var{used-string-chars} |
a44af9f2 | 259 | @var{used-vector-slots} |
f9f59935 | 260 | (@var{used-floats} . @var{free-floats}) |
40d48fe9 EZ |
261 | (@var{used-intervals} . @var{free-intervals}) |
262 | (@var{used-strings} . @var{free-strings})) | |
969fe9b5 RS |
263 | @end example |
264 | ||
265 | Here is an example: | |
266 | ||
267 | @example | |
a890e1b0 | 268 | @group |
a44af9f2 | 269 | (garbage-collect) |
f9f59935 RS |
270 | @result{} ((106886 . 13184) (9769 . 0) |
271 | (7731 . 4651) 347543 121628 | |
40d48fe9 EZ |
272 | (31 . 94) (1273 . 168) |
273 | (25474 . 3569)) | |
a44af9f2 | 274 | @end group |
a890e1b0 | 275 | @end example |
a44af9f2 RS |
276 | |
277 | Here is a table explaining each element: | |
278 | ||
279 | @table @var | |
280 | @item used-conses | |
281 | The number of cons cells in use. | |
282 | ||
283 | @item free-conses | |
284 | The number of cons cells for which space has been obtained from the | |
285 | operating system, but that are not currently being used. | |
286 | ||
287 | @item used-syms | |
288 | The number of symbols in use. | |
289 | ||
290 | @item free-syms | |
291 | The number of symbols for which space has been obtained from the | |
292 | operating system, but that are not currently being used. | |
293 | ||
969fe9b5 RS |
294 | @item used-miscs |
295 | The number of miscellaneous objects in use. These include markers and | |
296 | overlays, plus certain objects not visible to users. | |
a44af9f2 | 297 | |
969fe9b5 RS |
298 | @item free-miscs |
299 | The number of miscellaneous objects for which space has been obtained | |
300 | from the operating system, but that are not currently being used. | |
a44af9f2 RS |
301 | |
302 | @item used-string-chars | |
303 | The total size of all strings, in characters. | |
304 | ||
305 | @item used-vector-slots | |
306 | The total number of elements of existing vectors. | |
307 | ||
308 | @item used-floats | |
309 | @c Emacs 19 feature | |
310 | The number of floats in use. | |
311 | ||
312 | @item free-floats | |
313 | @c Emacs 19 feature | |
314 | The number of floats for which space has been obtained from the | |
315 | operating system, but that are not currently being used. | |
a9f0a989 RS |
316 | |
317 | @item used-intervals | |
318 | The number of intervals in use. Intervals are an internal | |
319 | data structure used for representing text properties. | |
320 | ||
321 | @item free-intervals | |
322 | The number of intervals for which space has been obtained | |
323 | from the operating system, but that are not currently being used. | |
40d48fe9 EZ |
324 | |
325 | @item used-strings | |
326 | The number of strings in use. | |
327 | ||
328 | @item free-strings | |
329 | The number of string headers for which the space was obtained from the | |
330 | operating system, but which are currently not in use. (A string | |
331 | object consists of a header and the storage for the string text | |
332 | itself; the latter is only allocated when the string is created.) | |
a44af9f2 RS |
333 | @end table |
334 | @end deffn | |
335 | ||
d64c55d8 RS |
336 | @defopt garbage-collection-messages |
337 | If this variable is non-@code{nil}, Emacs displays a message at the | |
338 | beginning and end of garbage collection. The default value is | |
339 | @code{nil}, meaning there are no such messages. | |
340 | @end defopt | |
341 | ||
e73c3ec4 RS |
342 | @defvar post-gc-hook |
343 | This is a normal hook that is run at the end of garbage collection. | |
344 | Garbage collection is inhibited while the hook functions run, so be | |
345 | careful writing them. | |
346 | @end defvar | |
347 | ||
a44af9f2 | 348 | @defopt gc-cons-threshold |
a890e1b0 | 349 | The value of this variable is the number of bytes of storage that must |
a44af9f2 | 350 | be allocated for Lisp objects after one garbage collection in order to |
a890e1b0 | 351 | trigger another garbage collection. A cons cell counts as eight bytes, |
a44af9f2 | 352 | a string as one byte per character plus a few bytes of overhead, and so |
a890e1b0 RS |
353 | on; space allocated to the contents of buffers does not count. Note |
354 | that the subsequent garbage collection does not happen immediately when | |
355 | the threshold is exhausted, but only the next time the Lisp evaluator is | |
a44af9f2 RS |
356 | called. |
357 | ||
f9f59935 | 358 | The initial threshold value is 400,000. If you specify a larger |
a44af9f2 RS |
359 | value, garbage collection will happen less often. This reduces the |
360 | amount of time spent garbage collecting, but increases total memory use. | |
574efc83 | 361 | You may want to do this when running a program that creates lots of |
a44af9f2 RS |
362 | Lisp data. |
363 | ||
a890e1b0 | 364 | You can make collections more frequent by specifying a smaller value, |
a44af9f2 RS |
365 | down to 10,000. A value less than 10,000 will remain in effect only |
366 | until the subsequent garbage collection, at which time | |
367 | @code{garbage-collect} will set the threshold back to 10,000. | |
368 | @end defopt | |
369 | ||
969fe9b5 RS |
370 | The value return by @code{garbage-collect} describes the amount of |
371 | memory used by Lisp data, broken down by data type. By contrast, the | |
372 | function @code{memory-limit} provides information on the total amount of | |
373 | memory Emacs is currently using. | |
374 | ||
a44af9f2 RS |
375 | @c Emacs 19 feature |
376 | @defun memory-limit | |
377 | This function returns the address of the last byte Emacs has allocated, | |
378 | divided by 1024. We divide the value by 1024 to make sure it fits in a | |
379 | Lisp integer. | |
380 | ||
381 | You can use this to get a general idea of how your actions affect the | |
382 | memory usage. | |
383 | @end defun | |
384 | ||
969fe9b5 RS |
385 | @node Memory Usage |
386 | @section Memory Usage | |
387 | ||
388 | These functions and variables give information about the total amount | |
389 | of memory allocation that Emacs has done, broken down by data type. | |
390 | Note the difference between these and the values returned by | |
391 | @code{(garbage-collect)}; those count objects that currently exist, but | |
392 | these count the number or size of all allocations, including those for | |
393 | objects that have since been freed. | |
394 | ||
395 | @defvar cons-cells-consed | |
396 | The total number of cons cells that have been allocated so far | |
397 | in this Emacs session. | |
398 | @end defvar | |
399 | ||
400 | @defvar floats-consed | |
401 | The total number of floats that have been allocated so far | |
402 | in this Emacs session. | |
403 | @end defvar | |
404 | ||
405 | @defvar vector-cells-consed | |
406 | The total number of vector cells that have been allocated so far | |
407 | in this Emacs session. | |
408 | @end defvar | |
409 | ||
410 | @defvar symbols-consed | |
411 | The total number of symbols that have been allocated so far | |
412 | in this Emacs session. | |
413 | @end defvar | |
414 | ||
415 | @defvar string-chars-consed | |
416 | The total number of string characters that have been allocated so far | |
417 | in this Emacs session. | |
418 | @end defvar | |
419 | ||
420 | @defvar misc-objects-consed | |
421 | The total number of miscellaneous objects that have been allocated so | |
422 | far in this Emacs session. These include markers and overlays, plus | |
423 | certain objects not visible to users. | |
424 | @end defvar | |
425 | ||
426 | @defvar intervals-consed | |
427 | The total number of intervals that have been allocated so far | |
428 | in this Emacs session. | |
429 | @end defvar | |
430 | ||
40d48fe9 EZ |
431 | @defvar strings-consed |
432 | The total number of strings that have been allocated so far in this | |
433 | Emacs session. | |
434 | @end defvar | |
435 | ||
969fe9b5 | 436 | @node Writing Emacs Primitives |
a44af9f2 RS |
437 | @appendixsec Writing Emacs Primitives |
438 | @cindex primitive function internals | |
439 | ||
440 | Lisp primitives are Lisp functions implemented in C. The details of | |
441 | interfacing the C function so that Lisp can call it are handled by a few | |
442 | C macros. The only way to really understand how to write new C code is | |
443 | to read the source, but we can explain some things here. | |
444 | ||
445 | An example of a special form is the definition of @code{or}, from | |
446 | @file{eval.c}. (An ordinary function would have the same general | |
447 | appearance.) | |
448 | ||
449 | @cindex garbage collection protection | |
450 | @smallexample | |
451 | @group | |
452 | DEFUN ("or", For, Sor, 0, UNEVALLED, 0, | |
f1842270 RS |
453 | doc: /* Eval args until one of them yields non-nil, then return that value. |
454 | The remaining args are not evalled at all. | |
455 | If all args return nil, return nil. | |
a44af9f2 RS |
456 | @end group |
457 | @group | |
f1842270 | 458 | usage: (or CONDITIONS ...) */) |
a44af9f2 RS |
459 | (args) |
460 | Lisp_Object args; | |
461 | @{ | |
462 | register Lisp_Object val; | |
463 | Lisp_Object args_left; | |
464 | struct gcpro gcpro1; | |
465 | @end group | |
466 | ||
467 | @group | |
95260b26 | 468 | if (NILP (args)) |
a44af9f2 RS |
469 | return Qnil; |
470 | ||
471 | args_left = args; | |
472 | GCPRO1 (args_left); | |
473 | @end group | |
474 | ||
475 | @group | |
476 | do | |
477 | @{ | |
478 | val = Feval (Fcar (args_left)); | |
95260b26 | 479 | if (!NILP (val)) |
a44af9f2 RS |
480 | break; |
481 | args_left = Fcdr (args_left); | |
482 | @} | |
95260b26 | 483 | while (!NILP (args_left)); |
a44af9f2 RS |
484 | @end group |
485 | ||
486 | @group | |
487 | UNGCPRO; | |
488 | return val; | |
489 | @} | |
490 | @end group | |
491 | @end smallexample | |
492 | ||
493 | Let's start with a precise explanation of the arguments to the | |
a890e1b0 | 494 | @code{DEFUN} macro. Here is a template for them: |
a44af9f2 RS |
495 | |
496 | @example | |
497 | DEFUN (@var{lname}, @var{fname}, @var{sname}, @var{min}, @var{max}, @var{interactive}, @var{doc}) | |
498 | @end example | |
499 | ||
500 | @table @var | |
501 | @item lname | |
a890e1b0 RS |
502 | This is the name of the Lisp symbol to define as the function name; in |
503 | the example above, it is @code{or}. | |
a44af9f2 RS |
504 | |
505 | @item fname | |
506 | This is the C function name for this function. This is | |
507 | the name that is used in C code for calling the function. The name is, | |
508 | by convention, @samp{F} prepended to the Lisp name, with all dashes | |
509 | (@samp{-}) in the Lisp name changed to underscores. Thus, to call this | |
510 | function from C code, call @code{For}. Remember that the arguments must | |
511 | be of type @code{Lisp_Object}; various macros and functions for creating | |
512 | values of type @code{Lisp_Object} are declared in the file | |
513 | @file{lisp.h}. | |
514 | ||
515 | @item sname | |
516 | This is a C variable name to use for a structure that holds the data for | |
517 | the subr object that represents the function in Lisp. This structure | |
518 | conveys the Lisp symbol name to the initialization routine that will | |
519 | create the symbol and store the subr object as its definition. By | |
520 | convention, this name is always @var{fname} with @samp{F} replaced with | |
521 | @samp{S}. | |
522 | ||
523 | @item min | |
a890e1b0 RS |
524 | This is the minimum number of arguments that the function requires. The |
525 | function @code{or} allows a minimum of zero arguments. | |
a44af9f2 RS |
526 | |
527 | @item max | |
a890e1b0 RS |
528 | This is the maximum number of arguments that the function accepts, if |
529 | there is a fixed maximum. Alternatively, it can be @code{UNEVALLED}, | |
530 | indicating a special form that receives unevaluated arguments, or | |
531 | @code{MANY}, indicating an unlimited number of evaluated arguments (the | |
532 | equivalent of @code{&rest}). Both @code{UNEVALLED} and @code{MANY} are | |
533 | macros. If @var{max} is a number, it may not be less than @var{min} and | |
534 | it may not be greater than seven. | |
a44af9f2 RS |
535 | |
536 | @item interactive | |
537 | This is an interactive specification, a string such as might be used as | |
538 | the argument of @code{interactive} in a Lisp function. In the case of | |
539 | @code{or}, it is 0 (a null pointer), indicating that @code{or} cannot be | |
a890e1b0 RS |
540 | called interactively. A value of @code{""} indicates a function that |
541 | should receive no arguments when called interactively. | |
a44af9f2 RS |
542 | |
543 | @item doc | |
f1842270 RS |
544 | This is the documentation string. It uses C comment syntax rather |
545 | than C string syntax because comment syntax requires nothing special | |
546 | to include multiple lines. The @samp{doc:} identifies the comment | |
547 | that follows as the documentation string. The @samp{/*} and @samp{*/} | |
548 | delimiters that begin and end the comment are not part of the | |
549 | documentation string. | |
550 | ||
551 | If the last line of the documentation string begins with the keyword | |
552 | @samp{usage:}, the rest of the line is treated as the argument list | |
553 | for documentation purposes. This way, you can use different argument | |
554 | names in the documentation string from the ones used in the C code. | |
555 | ||
556 | All the usual rules for documentation strings in Lisp code | |
557 | (@pxref{Documentation Tips}) apply to C code documentation strings | |
558 | too. | |
a44af9f2 RS |
559 | @end table |
560 | ||
a890e1b0 RS |
561 | After the call to the @code{DEFUN} macro, you must write the argument |
562 | name list that every C function must have, followed by ordinary C | |
563 | declarations for the arguments. For a function with a fixed maximum | |
564 | number of arguments, declare a C argument for each Lisp argument, and | |
574efc83 RS |
565 | give them all type @code{Lisp_Object}. When a Lisp function has no |
566 | upper limit on the number of arguments, its implementation in C actually | |
567 | receives exactly two arguments: the first is the number of Lisp | |
568 | arguments, and the second is the address of a block containing their | |
569 | values. They have types @code{int} and @w{@code{Lisp_Object *}}. | |
a44af9f2 RS |
570 | |
571 | Within the function @code{For} itself, note the use of the macros | |
572 | @code{GCPRO1} and @code{UNGCPRO}. @code{GCPRO1} is used to ``protect'' | |
573 | a variable from garbage collection---to inform the garbage collector that | |
574 | it must look in that variable and regard its contents as an accessible | |
575 | object. This is necessary whenever you call @code{Feval} or anything | |
576 | that can directly or indirectly call @code{Feval}. At such a time, any | |
577 | Lisp object that you intend to refer to again must be protected somehow. | |
578 | @code{UNGCPRO} cancels the protection of the variables that are | |
579 | protected in the current function. It is necessary to do this explicitly. | |
580 | ||
70bb4402 RS |
581 | It suffices to ensure that at least one pointer to each object is |
582 | GC-protected; as long as the object is not recycled, all pointers to | |
583 | it remain valid. So if you are sure that a local variable points to | |
584 | an object that will be preserved by some other pointer, that local | |
585 | variable does not need a GCPRO. (Formerly, strings were an exception | |
586 | to this rule; in older Emacs versions, every pointer to a string | |
587 | needed to be marked by GC.) | |
588 | ||
589 | The macro @code{GCPRO1} protects just one local variable. If you | |
590 | want to protect two, use @code{GCPRO2} instead; repeating | |
591 | @code{GCPRO1} will not work. Macros, @code{GCPRO3}, @code{GCPRO4}, | |
592 | @code{GCPRO5}, and @code{GCPRO6} also exist. These macros implicitly | |
593 | use local variables such as @code{gcpro1}; you must declare these | |
594 | explicitly, with type @code{struct gcpro}. Thus, if you use | |
595 | @code{GCPRO2}, you must declare @code{gcpro1} and @code{gcpro2}. | |
a890e1b0 RS |
596 | Alas, we can't explain all the tricky details here. |
597 | ||
70bb4402 RS |
598 | Built-in functions that take a variable number of arguments actually |
599 | accept two arguments at the C level: the number of Lisp arguments, and | |
600 | a @code{Lisp_Object *} pointer to a C vector containing those Lisp | |
601 | arguments. This C vector may be part of a Lisp vector, but it need | |
236a1914 RS |
602 | not be. The responsibility for using GCPRO to protecting the Lisp |
603 | arguments from GC if necessary rests with the caller in this case, | |
604 | since the caller allocated or found the storage for them. | |
70bb4402 | 605 | |
e610024b | 606 | You must not use C initializers for static or global variables unless |
05aea714 | 607 | the variables are never written once Emacs is dumped. These variables |
8241495d RS |
608 | with initializers are allocated in an area of memory that becomes |
609 | read-only (on certain operating systems) as a result of dumping Emacs. | |
610 | @xref{Pure Storage}. | |
e610024b RS |
611 | |
612 | Do not use static variables within functions---place all static | |
613 | variables at top level in the file. This is necessary because Emacs on | |
614 | some operating systems defines the keyword @code{static} as a null | |
615 | macro. (This definition is used because those systems put all variables | |
616 | declared static in a place that becomes read-only after dumping, whether | |
617 | they have initializers or not.) | |
77223f05 | 618 | |
a890e1b0 RS |
619 | Defining the C function is not enough to make a Lisp primitive |
620 | available; you must also create the Lisp symbol for the primitive and | |
621 | store a suitable subr object in its function cell. The code looks like | |
622 | this: | |
a44af9f2 RS |
623 | |
624 | @example | |
625 | defsubr (&@var{subr-structure-name}); | |
626 | @end example | |
627 | ||
628 | @noindent | |
a890e1b0 RS |
629 | Here @var{subr-structure-name} is the name you used as the third |
630 | argument to @code{DEFUN}. | |
631 | ||
632 | If you add a new primitive to a file that already has Lisp primitives | |
633 | defined in it, find the function (near the end of the file) named | |
634 | @code{syms_of_@var{something}}, and add the call to @code{defsubr} | |
635 | there. If the file doesn't have this function, or if you create a new | |
636 | file, add to it a @code{syms_of_@var{filename}} (e.g., | |
637 | @code{syms_of_myfile}). Then find the spot in @file{emacs.c} where all | |
638 | of these functions are called, and add a call to | |
639 | @code{syms_of_@var{filename}} there. | |
a44af9f2 | 640 | |
8241495d | 641 | @vindex byte-boolean-vars |
574efc83 RS |
642 | The function @code{syms_of_@var{filename}} is also the place to define |
643 | any C variables that are to be visible as Lisp variables. | |
a890e1b0 RS |
644 | @code{DEFVAR_LISP} makes a C variable of type @code{Lisp_Object} visible |
645 | in Lisp. @code{DEFVAR_INT} makes a C variable of type @code{int} | |
646 | visible in Lisp with a value that is always an integer. | |
647 | @code{DEFVAR_BOOL} makes a C variable of type @code{int} visible in Lisp | |
8241495d RS |
648 | with a value that is either @code{t} or @code{nil}. Note that variables |
649 | defined with @code{DEFVAR_BOOL} are automatically added to the list | |
650 | @code{byte-boolean-vars} used by the byte compiler. | |
a44af9f2 | 651 | |
969fe9b5 | 652 | If you define a file-scope C variable of type @code{Lisp_Object}, |
8241495d | 653 | you must protect it from garbage-collection by calling @code{staticpro} |
969fe9b5 RS |
654 | in @code{syms_of_@var{filename}}, like this: |
655 | ||
656 | @example | |
657 | staticpro (&@var{variable}); | |
658 | @end example | |
659 | ||
a890e1b0 | 660 | Here is another example function, with more complicated arguments. |
969fe9b5 RS |
661 | This comes from the code in @file{window.c}, and it demonstrates the use |
662 | of macros and functions to manipulate Lisp objects. | |
a44af9f2 RS |
663 | |
664 | @smallexample | |
665 | @group | |
666 | DEFUN ("coordinates-in-window-p", Fcoordinates_in_window_p, | |
667 | Scoordinates_in_window_p, 2, 2, | |
668 | "xSpecify coordinate pair: \nXExpression which evals to window: ", | |
88510b17 | 669 | "Return non-nil if COORDINATES is in WINDOW.\n\ |
969fe9b5 RS |
670 | COORDINATES is a cons of the form (X . Y), X and Y being distances\n\ |
671 | ... | |
a44af9f2 RS |
672 | @end group |
673 | @group | |
969fe9b5 RS |
674 | If they are on the border between WINDOW and its right sibling,\n\ |
675 | `vertical-line' is returned.") | |
676 | (coordinates, window) | |
677 | register Lisp_Object coordinates, window; | |
a44af9f2 | 678 | @{ |
969fe9b5 | 679 | int x, y; |
a44af9f2 RS |
680 | @end group |
681 | ||
682 | @group | |
969fe9b5 RS |
683 | CHECK_LIVE_WINDOW (window, 0); |
684 | CHECK_CONS (coordinates, 1); | |
685 | x = XINT (Fcar (coordinates)); | |
686 | y = XINT (Fcdr (coordinates)); | |
a44af9f2 | 687 | @end group |
969fe9b5 | 688 | |
a44af9f2 | 689 | @group |
969fe9b5 RS |
690 | switch (coordinates_in_window (XWINDOW (window), &x, &y)) |
691 | @{ | |
692 | case 0: /* NOT in window at all. */ | |
693 | return Qnil; | |
a44af9f2 | 694 | @end group |
969fe9b5 | 695 | |
a44af9f2 | 696 | @group |
969fe9b5 RS |
697 | case 1: /* In text part of window. */ |
698 | return Fcons (make_number (x), make_number (y)); | |
a44af9f2 | 699 | @end group |
969fe9b5 | 700 | |
a44af9f2 | 701 | @group |
969fe9b5 RS |
702 | case 2: /* In mode line of window. */ |
703 | return Qmode_line; | |
a44af9f2 | 704 | @end group |
969fe9b5 | 705 | |
a44af9f2 | 706 | @group |
969fe9b5 RS |
707 | case 3: /* On right border of window. */ |
708 | return Qvertical_line; | |
709 | @end group | |
710 | ||
711 | @group | |
712 | default: | |
713 | abort (); | |
714 | @} | |
a44af9f2 RS |
715 | @} |
716 | @end group | |
717 | @end smallexample | |
718 | ||
a890e1b0 RS |
719 | Note that C code cannot call functions by name unless they are defined |
720 | in C. The way to call a function written in Lisp is to use | |
721 | @code{Ffuncall}, which embodies the Lisp function @code{funcall}. Since | |
722 | the Lisp function @code{funcall} accepts an unlimited number of | |
723 | arguments, in C it takes two: the number of Lisp-level arguments, and a | |
724 | one-dimensional array containing their values. The first Lisp-level | |
725 | argument is the Lisp function to call, and the rest are the arguments to | |
726 | pass to it. Since @code{Ffuncall} can call the evaluator, you must | |
727 | protect pointers from garbage collection around the call to | |
728 | @code{Ffuncall}. | |
729 | ||
730 | The C functions @code{call0}, @code{call1}, @code{call2}, and so on, | |
731 | provide handy ways to call a Lisp function conveniently with a fixed | |
732 | number of arguments. They work by calling @code{Ffuncall}. | |
a44af9f2 RS |
733 | |
734 | @file{eval.c} is a very good file to look through for examples; | |
735 | @file{lisp.h} contains the definitions for some important macros and | |
736 | functions. | |
737 | ||
8241495d RS |
738 | If you define a function which is side-effect free, update the code in |
739 | @file{byte-opt.el} which binds @code{side-effect-free-fns} and | |
740 | @code{side-effect-and-error-free-fns} to include it. This will help the | |
741 | optimizer. | |
742 | ||
969fe9b5 | 743 | @node Object Internals |
a44af9f2 RS |
744 | @appendixsec Object Internals |
745 | @cindex object internals | |
746 | ||
747 | GNU Emacs Lisp manipulates many different types of data. The actual | |
f9f59935 RS |
748 | data are stored in a heap and the only access that programs have to it |
749 | is through pointers. Pointers are thirty-two bits wide in most | |
a44af9f2 | 750 | implementations. Depending on the operating system and type of machine |
f9f59935 RS |
751 | for which you compile Emacs, twenty-eight bits are used to address the |
752 | object, and the remaining four bits are used for a GC mark bit and the | |
a44af9f2 RS |
753 | tag that identifies the object's type. |
754 | ||
a890e1b0 RS |
755 | Because Lisp objects are represented as tagged pointers, it is always |
756 | possible to determine the Lisp data type of any object. The C data type | |
757 | @code{Lisp_Object} can hold any Lisp object of any data type. Ordinary | |
758 | variables have type @code{Lisp_Object}, which means they can hold any | |
759 | type of Lisp value; you can determine the actual data type only at run | |
760 | time. The same is true for function arguments; if you want a function | |
761 | to accept only a certain type of argument, you must check the type | |
762 | explicitly using a suitable predicate (@pxref{Type Predicates}). | |
a44af9f2 RS |
763 | @cindex type checking internals |
764 | ||
765 | @menu | |
766 | * Buffer Internals:: Components of a buffer structure. | |
767 | * Window Internals:: Components of a window structure. | |
768 | * Process Internals:: Components of a process structure. | |
769 | @end menu | |
770 | ||
969fe9b5 | 771 | @node Buffer Internals |
a44af9f2 RS |
772 | @appendixsubsec Buffer Internals |
773 | @cindex internals, of buffer | |
774 | @cindex buffer internals | |
775 | ||
776 | Buffers contain fields not directly accessible by the Lisp programmer. | |
777 | We describe them here, naming them by the names used in the C code. | |
778 | Many are accessible indirectly in Lisp programs via Lisp primitives. | |
779 | ||
95260b26 GM |
780 | Two structures are used to represent buffers in C. The |
781 | @code{buffer_text} structure contains fields describing the text of a | |
782 | buffer; the @code{buffer} structure holds other fields. In the case | |
783 | of indirect buffers, two or more @code{buffer} structures reference | |
784 | the same @code{buffer_text} structure. | |
785 | ||
786 | Here is a list of the @code{struct buffer_text} fields: | |
787 | ||
a44af9f2 | 788 | @table @code |
95260b26 | 789 | @item beg |
05aea714 | 790 | This field contains the actual address of the buffer contents. |
95260b26 | 791 | |
d7255d62 | 792 | @item gpt |
95260b26 | 793 | This holds the character position of the gap in the buffer. |
88510b17 | 794 | @xref{Buffer Gap}. |
95260b26 GM |
795 | |
796 | @item z | |
797 | This field contains the character position of the end of the buffer | |
798 | text. | |
799 | ||
800 | @item gpt_byte | |
801 | Contains the byte position of the gap. | |
802 | ||
803 | @item z_byte | |
804 | Holds the byte position of the end of the buffer text. | |
805 | ||
806 | @item gap_size | |
88510b17 | 807 | Contains the size of buffer's gap. @xref{Buffer Gap}. |
95260b26 GM |
808 | |
809 | @item modiff | |
810 | This field counts buffer-modification events for this buffer. It is | |
811 | incremented for each such event, and never otherwise changed. | |
812 | ||
813 | @item save_modiff | |
814 | Contains the previous value of @code{modiff}, as of the last time a | |
815 | buffer was visited or saved in a file. | |
88510b17 | 816 | |
95260b26 GM |
817 | @item overlay_modiff |
818 | Counts modifications to overlays analogous to @code{modiff}. | |
88510b17 | 819 | |
95260b26 GM |
820 | @item beg_unchanged |
821 | Holds the number of characters at the start of the text that are known | |
822 | to be unchanged since the last redisplay that finished. | |
88510b17 | 823 | |
95260b26 GM |
824 | @item end_unchanged |
825 | Holds the number of characters at the end of the text that are known to | |
826 | be unchanged since the last redisplay that finished. | |
88510b17 | 827 | |
95260b26 GM |
828 | @item unchanged_modified |
829 | Contains the value of @code{modiff} at the time of the last redisplay | |
830 | that finished. If this value matches @code{modiff}, | |
831 | @code{beg_unchanged} and @code{end_unchanged} contain no useful | |
832 | information. | |
88510b17 | 833 | |
95260b26 GM |
834 | @item overlay_unchanged_modified |
835 | Contains the value of @code{overlay_modiff} at the time of the last | |
836 | redisplay that finished. If this value matches @code{overlay_modiff}, | |
837 | @code{beg_unchanged} and @code{end_unchanged} contain no useful | |
838 | information. | |
88510b17 | 839 | |
95260b26 GM |
840 | @item markers |
841 | The markers that refer to this buffer. This is actually a single | |
842 | marker, and successive elements in its marker @code{chain} are the other | |
843 | markers referring to this buffer text. | |
a44af9f2 | 844 | |
95260b26 GM |
845 | @item intervals |
846 | Contains the interval tree which records the text properties of this | |
847 | buffer. | |
848 | @end table | |
849 | ||
850 | The fields of @code{struct buffer} are: | |
851 | ||
852 | @table @code | |
853 | @item next | |
854 | Points to the next buffer, in the chain of all buffers including killed | |
855 | buffers. This chain is used only for garbage collection, in order to | |
856 | collect killed buffers properly. Note that vectors, and most kinds of | |
857 | objects allocated as vectors, are all on one chain, but buffers are on a | |
858 | separate chain of their own. | |
859 | ||
860 | @item own_text | |
861 | This is a @code{struct buffer_text} structure. In an ordinary buffer, | |
862 | it holds the buffer contents. In indirect buffers, this field is not | |
863 | used. | |
864 | ||
865 | @item text | |
866 | This points to the @code{buffer_text} structure that is used for this | |
867 | buffer. In an ordinary buffer, this is the @code{own_text} field above. | |
868 | In an indirect buffer, this is the @code{own_text} field of the base | |
869 | buffer. | |
870 | ||
871 | @item pt | |
872 | Contains the character position of point in a buffer. | |
873 | ||
874 | @item pt_byte | |
875 | Contains the byte position of point in a buffer. | |
876 | ||
877 | @item begv | |
88510b17 | 878 | This field contains the character position of the beginning of the |
95260b26 GM |
879 | accessible range of text in the buffer. |
880 | ||
881 | @item begv_byte | |
88510b17 | 882 | This field contains the byte position of the beginning of the |
95260b26 GM |
883 | accessible range of text in the buffer. |
884 | ||
885 | @item zv | |
88510b17 | 886 | This field contains the character position of the end of the |
95260b26 GM |
887 | accessible range of text in the buffer. |
888 | ||
889 | @item zv_byte | |
88510b17 | 890 | This field contains the byte position of the end of the |
95260b26 GM |
891 | accessible range of text in the buffer. |
892 | ||
893 | @item base_buffer | |
894 | In an indirect buffer, this points to the base buffer. In an ordinary | |
895 | buffer, it is null. | |
896 | ||
897 | @item local_var_flags | |
898 | This field contains flags indicating that certain variables are local in | |
899 | this buffer. Such variables are declared in the C code using | |
900 | @code{DEFVAR_PER_BUFFER}, and their buffer-local bindings are stored in | |
901 | fields in the buffer structure itself. (Some of these fields are | |
902 | described in this table.) | |
a44af9f2 RS |
903 | |
904 | @item modtime | |
905 | This field contains the modification time of the visited file. It is | |
8241495d RS |
906 | set when the file is written or read. Before writing the buffer into a |
907 | file, this field is compared to the modification time of the file to see | |
908 | if the file has changed on disk. @xref{Buffer Modification}. | |
a44af9f2 RS |
909 | |
910 | @item auto_save_modified | |
911 | This field contains the time when the buffer was last auto-saved. | |
912 | ||
95260b26 GM |
913 | @item auto_save_failure_time |
914 | The time at which we detected a failure to auto-save, or -1 if we didn't | |
915 | have a failure. | |
916 | ||
a44af9f2 RS |
917 | @item last_window_start |
918 | This field contains the @code{window-start} position in the buffer as of | |
919 | the last time the buffer was displayed in a window. | |
920 | ||
95260b26 GM |
921 | @item clip_changed |
922 | This flag is set when narrowing changes in a buffer. | |
923 | ||
924 | @item prevent_redisplay_optimizations_p | |
88510b17 | 925 | this flag indicates that redisplay optimizations should not be used |
95260b26 GM |
926 | to display this buffer. |
927 | ||
a890e1b0 RS |
928 | @item undo_list |
929 | This field points to the buffer's undo list. @xref{Undo}. | |
a44af9f2 | 930 | |
95260b26 GM |
931 | @item name |
932 | The buffer name is a string that names the buffer. It is guaranteed to | |
933 | be unique. @xref{Buffer Names}. | |
934 | ||
935 | @item filename | |
936 | The name of the file visited in this buffer, or @code{nil}. | |
88510b17 | 937 | |
95260b26 GM |
938 | @item directory |
939 | The directory for expanding relative file names. | |
940 | ||
941 | @item save_length | |
942 | Length of the file this buffer is visiting, when last read or saved. | |
943 | This and other fields concerned with saving are not kept in the | |
944 | @code{buffer_text} structure because indirect buffers are never saved. | |
945 | ||
946 | @item auto_save_file_name | |
88510b17 | 947 | File name used for auto-saving this buffer. This is not in the |
95260b26 GM |
948 | @code{buffer_text} because it's not used in indirect buffers at all. |
949 | ||
950 | @item read_only | |
951 | Non-@code{nil} means this buffer is read-only. | |
952 | ||
953 | @item mark | |
954 | This field contains the mark for the buffer. The mark is a marker, | |
955 | hence it is also included on the list @code{markers}. @xref{The Mark}. | |
956 | ||
957 | @item local_var_alist | |
958 | This field contains the association list describing the buffer-local | |
959 | variable bindings of this buffer, not including the built-in | |
960 | buffer-local bindings that have special slots in the buffer object. | |
961 | (Those slots are omitted from this table.) @xref{Buffer-Local | |
962 | Variables}. | |
963 | ||
964 | @item major_mode | |
965 | Symbol naming the major mode of this buffer, e.g., @code{lisp-mode}. | |
966 | ||
967 | @item mode_name | |
968 | Pretty name of major mode, e.g., @code{"Lisp"}. | |
969 | ||
970 | @item mode_line_format | |
971 | Mode line element that controls the format of the mode line. If this | |
972 | is @code{nil}, no mode line will be displayed. | |
973 | ||
974 | @item header_line_format | |
88510b17 | 975 | This field is analoguous to @code{mode_line_format} for the mode |
95260b26 GM |
976 | line displayed at the top of windows. |
977 | ||
978 | @item keymap | |
979 | This field holds the buffer's local keymap. @xref{Keymaps}. | |
980 | ||
981 | @item abbrev_table | |
982 | This buffer's local abbrevs. | |
983 | ||
984 | @item syntax_table | |
a44af9f2 RS |
985 | This field contains the syntax table for the buffer. @xref{Syntax Tables}. |
986 | ||
95260b26 GM |
987 | @item category_table |
988 | This field contains the category table for the buffer. | |
989 | ||
990 | @item case_fold_search | |
991 | The value of @code{case-fold-search} in this buffer. | |
992 | ||
993 | @item tab_width | |
994 | The value of @code{tab-width} in this buffer. | |
995 | ||
996 | @item fill_column | |
997 | The value of @code{fill-column} in this buffer. | |
998 | ||
999 | @item left_margin | |
1000 | The value of @code{left-margin} in this buffer. | |
1001 | ||
1002 | @item auto_fill_function | |
1003 | The value of @code{auto-fill-function} in this buffer. | |
1004 | ||
a44af9f2 RS |
1005 | @item downcase_table |
1006 | This field contains the conversion table for converting text to lower case. | |
969fe9b5 | 1007 | @xref{Case Tables}. |
a44af9f2 RS |
1008 | |
1009 | @item upcase_table | |
1010 | This field contains the conversion table for converting text to upper case. | |
969fe9b5 | 1011 | @xref{Case Tables}. |
a44af9f2 RS |
1012 | |
1013 | @item case_canon_table | |
1014 | This field contains the conversion table for canonicalizing text for | |
969fe9b5 | 1015 | case-folding search. @xref{Case Tables}. |
a44af9f2 RS |
1016 | |
1017 | @item case_eqv_table | |
1018 | This field contains the equivalence table for case-folding search. | |
969fe9b5 | 1019 | @xref{Case Tables}. |
a44af9f2 | 1020 | |
95260b26 GM |
1021 | @item truncate_lines |
1022 | The value of @code{truncate-lines} in this buffer. | |
a44af9f2 | 1023 | |
95260b26 GM |
1024 | @item ctl_arrow |
1025 | The value of @code{ctl-arrow} in this buffer. | |
a44af9f2 | 1026 | |
95260b26 GM |
1027 | @item selective_display |
1028 | The value of @code{selective-display} in this buffer. | |
a44af9f2 | 1029 | |
95260b26 GM |
1030 | @item selective_display_ellipsis |
1031 | The value of @code{selective-display-ellipsis} in this buffer. | |
a44af9f2 | 1032 | |
95260b26 GM |
1033 | @item minor_modes |
1034 | An alist of the minor modes of this buffer. | |
a890e1b0 | 1035 | |
95260b26 GM |
1036 | @item overwrite_mode |
1037 | The value of @code{overwrite_mode} in this buffer. | |
a890e1b0 | 1038 | |
95260b26 GM |
1039 | @item abbrev_mode |
1040 | The value of @code{abbrev-mode} in this buffer. | |
bfe721d1 | 1041 | |
95260b26 GM |
1042 | @item display_table |
1043 | This field contains the buffer's display table, or @code{nil} if it doesn't | |
1044 | have one. @xref{Display Tables}. | |
a890e1b0 | 1045 | |
95260b26 GM |
1046 | @item save_modified |
1047 | This field contains the time when the buffer was last saved, as an integer. | |
1048 | @xref{Buffer Modification}. | |
1049 | ||
1050 | @item mark_active | |
1051 | This field is non-@code{nil} if the buffer's mark is active. | |
a890e1b0 RS |
1052 | |
1053 | @item overlays_before | |
1054 | This field holds a list of the overlays in this buffer that end at or | |
1055 | before the current overlay center position. They are sorted in order of | |
1056 | decreasing end position. | |
1057 | ||
1058 | @item overlays_after | |
1059 | This field holds a list of the overlays in this buffer that end after | |
1060 | the current overlay center position. They are sorted in order of | |
1061 | increasing beginning position. | |
969fe9b5 | 1062 | |
95260b26 GM |
1063 | @item overlay_center |
1064 | This field holds the current overlay center position. @xref{Overlays}. | |
1065 | ||
969fe9b5 RS |
1066 | @item enable_multibyte_characters |
1067 | This field holds the buffer's local value of | |
1068 | @code{enable-multibyte-characters}---either @code{t} or @code{nil}. | |
95260b26 GM |
1069 | |
1070 | @item buffer_file_coding_system | |
1071 | The value of @code{buffer-file-coding-system} in this buffer. | |
1072 | ||
1073 | @item file_format | |
1074 | The value of @code{buffer-file-format} in this buffer. | |
1075 | ||
1076 | @item pt_marker | |
1077 | In an indirect buffer, or a buffer that is the base of an indirect | |
1078 | buffer, this holds a marker that records point for this buffer when the | |
1079 | buffer is not current. | |
1080 | ||
1081 | @item begv_marker | |
1082 | In an indirect buffer, or a buffer that is the base of an indirect | |
1083 | buffer, this holds a marker that records @code{begv} for this buffer | |
1084 | when the buffer is not current. | |
88510b17 | 1085 | |
95260b26 GM |
1086 | @item zv_marker |
1087 | In an indirect buffer, or a buffer that is the base of an indirect | |
1088 | buffer, this holds a marker that records @code{zv} for this buffer when | |
1089 | the buffer is not current. | |
1090 | ||
1091 | @item file_truename | |
1092 | The truename of the visited file, or @code{nil}. | |
1093 | ||
1094 | @item invisibility_spec | |
1095 | The value of @code{buffer-invisibility-spec} in this buffer. | |
1096 | ||
1097 | @item last_selected_window | |
1098 | This is the last window that was selected with this buffer in it, or @code{nil} | |
1099 | if that window no longer displays this buffer. | |
1100 | ||
1101 | @item display_count | |
1102 | This field is incremented each time the buffer is displayed in a window. | |
1103 | ||
1104 | @item left_margin_width | |
1105 | The value of @code{left-margin-width} in this buffer. | |
1106 | ||
1107 | @item right_margin_width | |
1108 | The value of @code{right-margin-width} in this buffer. | |
1109 | ||
1110 | @item indicate_empty_lines | |
1111 | Non-@code{nil} means indicate empty lines (lines with no text) with a | |
1112 | small bitmap in the fringe, when using a window system that can do it. | |
1113 | ||
1114 | @item display_time | |
1115 | This holds a time stamp that is updated each time this buffer is | |
1116 | displayed in a window. | |
1117 | ||
1118 | @item scroll_up_aggressively | |
1119 | The value of @code{scroll-up-aggressively} in this buffer. | |
88510b17 | 1120 | |
95260b26 GM |
1121 | @item scroll_down_aggressively |
1122 | The value of @code{scroll-down-aggressively} in this buffer. | |
a44af9f2 RS |
1123 | @end table |
1124 | ||
969fe9b5 | 1125 | @node Window Internals |
a44af9f2 RS |
1126 | @appendixsubsec Window Internals |
1127 | @cindex internals, of window | |
1128 | @cindex window internals | |
1129 | ||
1130 | Windows have the following accessible fields: | |
1131 | ||
1132 | @table @code | |
1133 | @item frame | |
a890e1b0 | 1134 | The frame that this window is on. |
a44af9f2 RS |
1135 | |
1136 | @item mini_p | |
a890e1b0 | 1137 | Non-@code{nil} if this window is a minibuffer window. |
a44af9f2 | 1138 | |
95260b26 GM |
1139 | @item parent |
1140 | Internally, Emacs arranges windows in a tree; each group of siblings has | |
1141 | a parent window whose area includes all the siblings. This field points | |
1142 | to a window's parent. | |
1143 | ||
1144 | Parent windows do not display buffers, and play little role in display | |
1145 | except to shape their child windows. Emacs Lisp programs usually have | |
1146 | no access to the parent windows; they operate on the windows at the | |
1147 | leaves of the tree, which actually display buffers. | |
1148 | ||
1149 | The following four fields also describe the window tree structure. | |
1150 | ||
1151 | @item hchild | |
1152 | In a window subdivided horizontally by child windows, the leftmost child. | |
1153 | Otherwise, @code{nil}. | |
1154 | ||
1155 | @item vchild | |
1156 | In a window subdivided vertically by child windows, the topmost child. | |
1157 | Otherwise, @code{nil}. | |
1158 | ||
1159 | @item next | |
1160 | The next sibling of this window. It is @code{nil} in a window that is | |
1161 | the rightmost or bottommost of a group of siblings. | |
1162 | ||
1163 | @item prev | |
1164 | The previous sibling of this window. It is @code{nil} in a window that | |
1165 | is the leftmost or topmost of a group of siblings. | |
1166 | ||
1167 | @item left | |
1168 | This is the left-hand edge of the window, measured in columns. (The | |
1169 | leftmost column on the screen is @w{column 0}.) | |
1170 | ||
1171 | @item top | |
1172 | This is the top edge of the window, measured in lines. (The top line on | |
1173 | the screen is @w{line 0}.) | |
1174 | ||
1175 | @item height | |
1176 | The height of the window, measured in lines. | |
1177 | ||
1178 | @item width | |
1179 | The width of the window, measured in columns. This width includes the | |
1180 | scroll bar and fringes, and/or the separator line on the right of the | |
1181 | window (if any). | |
1182 | ||
a44af9f2 | 1183 | @item buffer |
574efc83 | 1184 | The buffer that the window is displaying. This may change often during |
a44af9f2 RS |
1185 | the life of the window. |
1186 | ||
95260b26 GM |
1187 | @item start |
1188 | The position in the buffer that is the first character to be displayed | |
1189 | in the window. | |
a44af9f2 RS |
1190 | |
1191 | @item pointm | |
1192 | @cindex window point internals | |
a890e1b0 | 1193 | This is the value of point in the current buffer when this window is |
a44af9f2 RS |
1194 | selected; when it is not selected, it retains its previous value. |
1195 | ||
a890e1b0 RS |
1196 | @item force_start |
1197 | If this flag is non-@code{nil}, it says that the window has been | |
1198 | scrolled explicitly by the Lisp program. This affects what the next | |
1199 | redisplay does if point is off the screen: instead of scrolling the | |
1200 | window to show the text around point, it moves point to a location that | |
1201 | is on the screen. | |
1202 | ||
95260b26 | 1203 | @item frozen_window_start_p |
88510b17 | 1204 | This field is set temporarily to 1 to indicate to redisplay that |
95260b26 GM |
1205 | @code{start} of this window should not be changed, even if point |
1206 | gets invisible. | |
1207 | ||
1208 | @item start_at_line_beg | |
1209 | Non-@code{nil} means current value of @code{start} was the beginning of a line | |
1210 | when it was chosen. | |
1211 | ||
1212 | @item too_small_ok | |
1213 | Non-@code{nil} means don't delete this window for becoming ``too small''. | |
1214 | ||
1215 | @item height_fixed_p | |
1216 | This field is temporarily set to 1 to fix the height of the selected | |
1217 | window when the echo area is resized. | |
1218 | ||
1219 | @item use_time | |
1220 | This is the last time that the window was selected. The function | |
1221 | @code{get-lru-window} uses this field. | |
1222 | ||
1223 | @item sequence_number | |
1224 | A unique number assigned to this window when it was created. | |
1225 | ||
a890e1b0 | 1226 | @item last_modified |
95260b26 | 1227 | The @code{modiff} field of the window's buffer, as of the last time |
a890e1b0 RS |
1228 | a redisplay completed in this window. |
1229 | ||
95260b26 GM |
1230 | @item last_overlay_modified |
1231 | The @code{overlay_modiff} field of the window's buffer, as of the last | |
1232 | time a redisplay completed in this window. | |
1233 | ||
a890e1b0 | 1234 | @item last_point |
95260b26 GM |
1235 | The buffer's value of point, as of the last time a redisplay completed |
1236 | in this window. | |
a890e1b0 | 1237 | |
95260b26 GM |
1238 | @item last_had_star |
1239 | A non-@code{nil} value means the window's buffer was ``modified'' when the | |
1240 | window was last updated. | |
a44af9f2 | 1241 | |
95260b26 GM |
1242 | @item vertical_scroll_bar |
1243 | This window's vertical scroll bar. | |
a44af9f2 | 1244 | |
95260b26 GM |
1245 | @item left_margin_width |
1246 | The width of the left margin in this window, or @code{nil} not to | |
1247 | specify it (in which case the buffer's value of @code{left-margin-width} | |
1248 | is used. | |
a890e1b0 | 1249 | |
95260b26 GM |
1250 | @item right_margin_width |
1251 | Likewise for the right margin. | |
a890e1b0 | 1252 | |
13ede7fc | 1253 | @ignore |
95260b26 GM |
1254 | @item last_mark_x |
1255 | @item last_mark_y | |
1256 | ???Not used. | |
1257 | @end ignore | |
a44af9f2 | 1258 | |
95260b26 GM |
1259 | @item window_end_pos |
1260 | This is computed as @code{z} minus the buffer position of the last glyph | |
1261 | in the current matrix of the window. The value is only valid if | |
1262 | @code{window_end_valid} is not @code{nil}. | |
a44af9f2 | 1263 | |
95260b26 GM |
1264 | @item window_end_bytepos |
1265 | The byte position corresponding to @code{window_end_pos}. | |
a890e1b0 | 1266 | |
95260b26 GM |
1267 | @item window_end_vpos |
1268 | The window-relative vertical position of the line containing | |
1269 | @code{window_end_pos}. | |
a44af9f2 | 1270 | |
95260b26 GM |
1271 | @item window_end_valid |
1272 | This field is set to a non-@code{nil} value if @code{window_end_pos} is truly | |
1273 | valid. This is @code{nil} if nontrivial redisplay is preempted since in that | |
1274 | case the display that @code{window_end_pos} was computed for did not get | |
1275 | onto the screen. | |
1276 | ||
1277 | @item redisplay_end_trigger | |
1278 | If redisplay in this window goes beyond this buffer position, it runs | |
1279 | run the @code{redisplay-end-trigger-hook}. | |
1280 | ||
13ede7fc | 1281 | @ignore |
95260b26 GM |
1282 | @item orig_height |
1283 | @item orig_top | |
1284 | ??? Are temporary storage areas. | |
1285 | @end ignore | |
1286 | ||
1287 | @item cursor | |
1288 | A structure describing where the cursor is in this window. | |
1289 | ||
1290 | @item last_cursor | |
1291 | The value of @code{cursor} as of the last redisplay that finished. | |
1292 | ||
1293 | @item phys_cursor | |
1294 | A structure describing where the cursor of this window physically is. | |
1295 | ||
1296 | @item phys_cursor_type | |
1297 | The type of cursor that was last displayed on this window. | |
1298 | ||
1299 | @item phys_cursor_on_p | |
1300 | This field is non-zero if the cursor is physically on. | |
1301 | ||
1302 | @item cursor_off_p | |
1303 | Non-zero means the cursor in this window is logically on. | |
1304 | ||
1305 | @item last_cursor_off_p | |
1306 | This field contains the value of @code{cursor_off_p} as of the time of | |
1307 | the last redisplay. | |
1308 | ||
1309 | @item must_be_updated_p | |
1310 | This is set to 1 during redisplay when this window must be updated. | |
1311 | ||
a44af9f2 | 1312 | @item hscroll |
a890e1b0 | 1313 | This is the number of columns that the display in the window is scrolled |
a44af9f2 RS |
1314 | horizontally to the left. Normally, this is 0. |
1315 | ||
95260b26 GM |
1316 | @item vscroll |
1317 | Vertical scroll amount, in pixels. Normally, this is 0. | |
1318 | ||
1319 | @item dedicated | |
1320 | Non-@code{nil} if this window is dedicated to its buffer. | |
a44af9f2 RS |
1321 | |
1322 | @item display_table | |
a890e1b0 RS |
1323 | The window's display table, or @code{nil} if none is specified for it. |
1324 | ||
1325 | @item update_mode_line | |
1326 | Non-@code{nil} means this window's mode line needs to be updated. | |
1327 | ||
1328 | @item base_line_number | |
1329 | The line number of a certain position in the buffer, or @code{nil}. | |
1330 | This is used for displaying the line number of point in the mode line. | |
1331 | ||
1332 | @item base_line_pos | |
1333 | The position in the buffer for which the line number is known, or | |
1334 | @code{nil} meaning none is known. | |
1335 | ||
1336 | @item region_showing | |
1337 | If the region (or part of it) is highlighted in this window, this field | |
1338 | holds the mark position that made one end of that region. Otherwise, | |
1339 | this field is @code{nil}. | |
95260b26 GM |
1340 | |
1341 | @item column_number_displayed | |
1342 | The column number currently displayed in this window's mode line, or @code{nil} | |
1343 | if column numbers are not being displayed. | |
1344 | ||
1345 | @item current_matrix | |
1346 | A glyph matrix describing the current display of this window. | |
1347 | ||
1348 | @item desired_matrix | |
1349 | A glyph matrix describing the desired display of this window. | |
a44af9f2 RS |
1350 | @end table |
1351 | ||
969fe9b5 | 1352 | @node Process Internals |
a44af9f2 RS |
1353 | @appendixsubsec Process Internals |
1354 | @cindex internals, of process | |
1355 | @cindex process internals | |
1356 | ||
1357 | The fields of a process are: | |
1358 | ||
1359 | @table @code | |
1360 | @item name | |
1361 | A string, the name of the process. | |
1362 | ||
1363 | @item command | |
1364 | A list containing the command arguments that were used to start this | |
1365 | process. | |
1366 | ||
1367 | @item filter | |
1368 | A function used to accept output from the process instead of a buffer, | |
1369 | or @code{nil}. | |
1370 | ||
1371 | @item sentinel | |
1372 | A function called whenever the process receives a signal, or @code{nil}. | |
1373 | ||
1374 | @item buffer | |
1375 | The associated buffer of the process. | |
1376 | ||
1377 | @item pid | |
1378 | An integer, the Unix process @sc{id}. | |
1379 | ||
1380 | @item childp | |
1381 | A flag, non-@code{nil} if this is really a child process. | |
1382 | It is @code{nil} for a network connection. | |
1383 | ||
a44af9f2 | 1384 | @item mark |
574efc83 RS |
1385 | A marker indicating the position of the end of the last output from this |
1386 | process inserted into the buffer. This is often but not always the end | |
1387 | of the buffer. | |
a44af9f2 RS |
1388 | |
1389 | @item kill_without_query | |
a890e1b0 RS |
1390 | If this is non-@code{nil}, killing Emacs while this process is still |
1391 | running does not ask for confirmation about killing the process. | |
1392 | ||
1393 | @item raw_status_low | |
1394 | @itemx raw_status_high | |
1395 | These two fields record 16 bits each of the process status returned by | |
1396 | the @code{wait} system call. | |
1397 | ||
1398 | @item status | |
1399 | The process status, as @code{process-status} should return it. | |
1400 | ||
1401 | @item tick | |
1402 | @itemx update_tick | |
1403 | If these two fields are not equal, a change in the status of the process | |
1404 | needs to be reported, either by running the sentinel or by inserting a | |
1405 | message in the process buffer. | |
1406 | ||
1407 | @item pty_flag | |
1408 | Non-@code{nil} if communication with the subprocess uses a @sc{pty}; | |
1409 | @code{nil} if it uses a pipe. | |
1410 | ||
1411 | @item infd | |
1412 | The file descriptor for input from the process. | |
1413 | ||
1414 | @item outfd | |
1415 | The file descriptor for output to the process. | |
1416 | ||
1417 | @item subtty | |
1418 | The file descriptor for the terminal that the subprocess is using. (On | |
1419 | some systems, there is no need to record this, so the value is | |
1420 | @code{nil}.) | |
bfe721d1 KH |
1421 | |
1422 | @item tty_name | |
1423 | The name of the terminal that the subprocess is using, | |
1424 | or @code{nil} if it is using pipes. | |
95260b26 GM |
1425 | |
1426 | @item decode_coding_system | |
1427 | Coding-system for decoding the input from this process. | |
1428 | ||
1429 | @item decoding_buf | |
1430 | A working buffer for decoding. | |
1431 | ||
1432 | @item decoding_carryover | |
1433 | Size of carryover in decoding. | |
1434 | ||
1435 | @item encode_coding_system | |
1436 | Coding-system for encoding the output to this process. | |
1437 | ||
1438 | @item encoding_buf | |
a39c2e0d | 1439 | A working buffer for encoding. |
95260b26 GM |
1440 | |
1441 | @item encoding_carryover | |
1442 | Size of carryover in encoding. | |
1443 | ||
1444 | @item inherit_coding_system_flag | |
1445 | Flag to set @code{coding-system} of the process buffer from the | |
1446 | coding system used to decode process output. | |
a44af9f2 | 1447 | @end table |