Commit | Line | Data |
---|---|---|
b8d4c8d0 GM |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
acaf905b | 3 | @c Copyright (C) 1990-1995, 1998-2012 Free Software Foundation, Inc. |
b8d4c8d0 | 4 | @c See the file elisp.texi for copying conditions. |
6336d8c3 | 5 | @setfilename ../../info/text |
b8d4c8d0 GM |
6 | @node Text, Non-ASCII Characters, Markers, Top |
7 | @chapter Text | |
8 | @cindex text | |
9 | ||
10 | This chapter describes the functions that deal with the text in a | |
11 | buffer. Most examine, insert, or delete text in the current buffer, | |
12 | often operating at point or on text adjacent to point. Many are | |
13 | interactive. All the functions that change the text provide for undoing | |
14 | the changes (@pxref{Undo}). | |
15 | ||
16 | Many text-related functions operate on a region of text defined by two | |
17 | buffer positions passed in arguments named @var{start} and @var{end}. | |
18 | These arguments should be either markers (@pxref{Markers}) or numeric | |
19 | character positions (@pxref{Positions}). The order of these arguments | |
20 | does not matter; it is all right for @var{start} to be the end of the | |
21 | region and @var{end} the beginning. For example, @code{(delete-region 1 | |
22 | 10)} and @code{(delete-region 10 1)} are equivalent. An | |
23 | @code{args-out-of-range} error is signaled if either @var{start} or | |
24 | @var{end} is outside the accessible portion of the buffer. In an | |
25 | interactive call, point and the mark are used for these arguments. | |
26 | ||
27 | @cindex buffer contents | |
28 | Throughout this chapter, ``text'' refers to the characters in the | |
29 | buffer, together with their properties (when relevant). Keep in mind | |
30 | that point is always between two characters, and the cursor appears on | |
31 | the character after point. | |
32 | ||
33 | @menu | |
34 | * Near Point:: Examining text in the vicinity of point. | |
35 | * Buffer Contents:: Examining text in a general fashion. | |
36 | * Comparing Text:: Comparing substrings of buffers. | |
37 | * Insertion:: Adding new text to a buffer. | |
38 | * Commands for Insertion:: User-level commands to insert text. | |
39 | * Deletion:: Removing text from a buffer. | |
40 | * User-Level Deletion:: User-level commands to delete text. | |
41 | * The Kill Ring:: Where removed text sometimes is saved for later use. | |
42 | * Undo:: Undoing changes to the text of a buffer. | |
43 | * Maintaining Undo:: How to enable and disable undo information. | |
d24880de | 44 | How to control how much information is kept. |
b8d4c8d0 GM |
45 | * Filling:: Functions for explicit filling. |
46 | * Margins:: How to specify margins for filling commands. | |
47 | * Adaptive Fill:: Adaptive Fill mode chooses a fill prefix from context. | |
48 | * Auto Filling:: How auto-fill mode is implemented to break lines. | |
49 | * Sorting:: Functions for sorting parts of the buffer. | |
50 | * Columns:: Computing horizontal positions, and using them. | |
51 | * Indentation:: Functions to insert or adjust indentation. | |
52 | * Case Changes:: Case conversion of parts of the buffer. | |
53 | * Text Properties:: Assigning Lisp property lists to text characters. | |
54 | * Substitution:: Replacing a given character wherever it appears. | |
55 | * Transposition:: Swapping two portions of a buffer. | |
56 | * Registers:: How registers are implemented. Accessing the text or | |
57 | position stored in a register. | |
58 | * Base 64:: Conversion to or from base 64 encoding. | |
59 | * MD5 Checksum:: Compute the MD5 "message digest"/"checksum". | |
381408e2 | 60 | * Parsing HTML:: Parsing HTML and XML. |
b8d4c8d0 GM |
61 | * Atomic Changes:: Installing several buffer changes "atomically". |
62 | * Change Hooks:: Supplying functions to be run when text is changed. | |
63 | @end menu | |
64 | ||
65 | @node Near Point | |
66 | @section Examining Text Near Point | |
67 | @cindex text near point | |
68 | ||
69 | Many functions are provided to look at the characters around point. | |
70 | Several simple functions are described here. See also @code{looking-at} | |
71 | in @ref{Regexp Search}. | |
72 | ||
73 | In the following four functions, ``beginning'' or ``end'' of buffer | |
74 | refers to the beginning or end of the accessible portion. | |
75 | ||
76 | @defun char-after &optional position | |
77 | This function returns the character in the current buffer at (i.e., | |
78 | immediately after) position @var{position}. If @var{position} is out of | |
79 | range for this purpose, either before the beginning of the buffer, or at | |
80 | or beyond the end, then the value is @code{nil}. The default for | |
81 | @var{position} is point. | |
82 | ||
83 | In the following example, assume that the first character in the | |
84 | buffer is @samp{@@}: | |
85 | ||
86 | @example | |
87 | @group | |
3e99b825 | 88 | (string (char-after 1)) |
b8d4c8d0 GM |
89 | @result{} "@@" |
90 | @end group | |
91 | @end example | |
92 | @end defun | |
93 | ||
94 | @defun char-before &optional position | |
95 | This function returns the character in the current buffer immediately | |
96 | before position @var{position}. If @var{position} is out of range for | |
97 | this purpose, either at or before the beginning of the buffer, or beyond | |
98 | the end, then the value is @code{nil}. The default for | |
99 | @var{position} is point. | |
100 | @end defun | |
101 | ||
102 | @defun following-char | |
103 | This function returns the character following point in the current | |
104 | buffer. This is similar to @code{(char-after (point))}. However, if | |
105 | point is at the end of the buffer, then @code{following-char} returns 0. | |
106 | ||
107 | Remember that point is always between characters, and the cursor | |
108 | normally appears over the character following point. Therefore, the | |
109 | character returned by @code{following-char} is the character the | |
110 | cursor is over. | |
111 | ||
112 | In this example, point is between the @samp{a} and the @samp{c}. | |
113 | ||
114 | @example | |
115 | @group | |
116 | ---------- Buffer: foo ---------- | |
117 | Gentlemen may cry ``Pea@point{}ce! Peace!,'' | |
118 | but there is no peace. | |
119 | ---------- Buffer: foo ---------- | |
120 | @end group | |
121 | ||
122 | @group | |
3e99b825 | 123 | (string (preceding-char)) |
b8d4c8d0 | 124 | @result{} "a" |
3e99b825 | 125 | (string (following-char)) |
b8d4c8d0 GM |
126 | @result{} "c" |
127 | @end group | |
128 | @end example | |
129 | @end defun | |
130 | ||
131 | @defun preceding-char | |
132 | This function returns the character preceding point in the current | |
133 | buffer. See above, under @code{following-char}, for an example. If | |
134 | point is at the beginning of the buffer, @code{preceding-char} returns | |
135 | 0. | |
136 | @end defun | |
137 | ||
138 | @defun bobp | |
139 | This function returns @code{t} if point is at the beginning of the | |
140 | buffer. If narrowing is in effect, this means the beginning of the | |
141 | accessible portion of the text. See also @code{point-min} in | |
142 | @ref{Point}. | |
143 | @end defun | |
144 | ||
145 | @defun eobp | |
146 | This function returns @code{t} if point is at the end of the buffer. | |
147 | If narrowing is in effect, this means the end of accessible portion of | |
148 | the text. See also @code{point-max} in @xref{Point}. | |
149 | @end defun | |
150 | ||
151 | @defun bolp | |
152 | This function returns @code{t} if point is at the beginning of a line. | |
153 | @xref{Text Lines}. The beginning of the buffer (or of its accessible | |
154 | portion) always counts as the beginning of a line. | |
155 | @end defun | |
156 | ||
157 | @defun eolp | |
158 | This function returns @code{t} if point is at the end of a line. The | |
159 | end of the buffer (or of its accessible portion) is always considered | |
160 | the end of a line. | |
161 | @end defun | |
162 | ||
163 | @node Buffer Contents | |
164 | @section Examining Buffer Contents | |
165 | ||
166 | This section describes functions that allow a Lisp program to | |
167 | convert any portion of the text in the buffer into a string. | |
168 | ||
169 | @defun buffer-substring start end | |
170 | This function returns a string containing a copy of the text of the | |
171 | region defined by positions @var{start} and @var{end} in the current | |
172 | buffer. If the arguments are not positions in the accessible portion of | |
173 | the buffer, @code{buffer-substring} signals an @code{args-out-of-range} | |
174 | error. | |
175 | ||
176 | It is not necessary for @var{start} to be less than @var{end}; the | |
177 | arguments can be given in either order. But most often the smaller | |
178 | argument is written first. | |
179 | ||
180 | Here's an example which assumes Font-Lock mode is not enabled: | |
181 | ||
182 | @example | |
183 | @group | |
184 | ---------- Buffer: foo ---------- | |
185 | This is the contents of buffer foo | |
186 | ||
187 | ---------- Buffer: foo ---------- | |
188 | @end group | |
189 | ||
190 | @group | |
191 | (buffer-substring 1 10) | |
192 | @result{} "This is t" | |
193 | @end group | |
194 | @group | |
195 | (buffer-substring (point-max) 10) | |
196 | @result{} "he contents of buffer foo\n" | |
197 | @end group | |
198 | @end example | |
199 | ||
200 | If the text being copied has any text properties, these are copied into | |
201 | the string along with the characters they belong to. @xref{Text | |
202 | Properties}. However, overlays (@pxref{Overlays}) in the buffer and | |
203 | their properties are ignored, not copied. | |
204 | ||
205 | For example, if Font-Lock mode is enabled, you might get results like | |
206 | these: | |
207 | ||
208 | @example | |
209 | @group | |
210 | (buffer-substring 1 10) | |
211 | @result{} #("This is t" 0 1 (fontified t) 1 9 (fontified t)) | |
212 | @end group | |
213 | @end example | |
214 | @end defun | |
215 | ||
216 | @defun buffer-substring-no-properties start end | |
217 | This is like @code{buffer-substring}, except that it does not copy text | |
218 | properties, just the characters themselves. @xref{Text Properties}. | |
219 | @end defun | |
220 | ||
221 | @defun filter-buffer-substring start end &optional delete noprops | |
222 | This function passes the buffer text between @var{start} and @var{end} | |
223 | through the filter functions specified by the variable | |
224 | @code{buffer-substring-filters}, and returns the value from the last | |
225 | filter function. If @code{buffer-substring-filters} is @code{nil}, | |
226 | the value is the unaltered text from the buffer, what | |
227 | @code{buffer-substring} would return. | |
228 | ||
229 | If @var{delete} is non-@code{nil}, this function deletes the text | |
230 | between @var{start} and @var{end} after copying it, like | |
231 | @code{delete-and-extract-region}. | |
232 | ||
233 | If @var{noprops} is non-@code{nil}, the final string returned does not | |
234 | include text properties, while the string passed through the filters | |
235 | still includes text properties from the buffer text. | |
236 | ||
237 | Lisp code should use this function instead of @code{buffer-substring}, | |
238 | @code{buffer-substring-no-properties}, | |
239 | or @code{delete-and-extract-region} when copying into user-accessible | |
240 | data structures such as the kill-ring, X clipboard, and registers. | |
241 | Major and minor modes can add functions to | |
242 | @code{buffer-substring-filters} to alter such text as it is copied out | |
243 | of the buffer. | |
244 | @end defun | |
245 | ||
246 | @defvar buffer-substring-filters | |
247 | This variable should be a list of functions that accept a single | |
248 | argument, a string, and return a string. | |
249 | @code{filter-buffer-substring} passes the buffer substring to the | |
250 | first function in this list, and the return value of each function is | |
251 | passed to the next function. The return value of the last function is | |
252 | used as the return value of @code{filter-buffer-substring}. | |
253 | ||
254 | As a special convention, point is set to the start of the buffer text | |
255 | being operated on (i.e., the @var{start} argument for | |
256 | @code{filter-buffer-substring}) before these functions are called. | |
257 | ||
258 | If this variable is @code{nil}, no filtering is performed. | |
259 | @end defvar | |
260 | ||
261 | @defun buffer-string | |
262 | This function returns the contents of the entire accessible portion of | |
263 | the current buffer as a string. It is equivalent to | |
264 | ||
265 | @example | |
266 | (buffer-substring (point-min) (point-max)) | |
267 | @end example | |
268 | ||
269 | @example | |
270 | @group | |
271 | ---------- Buffer: foo ---------- | |
272 | This is the contents of buffer foo | |
273 | ||
274 | ---------- Buffer: foo ---------- | |
275 | ||
276 | (buffer-string) | |
277 | @result{} "This is the contents of buffer foo\n" | |
278 | @end group | |
279 | @end example | |
280 | @end defun | |
281 | ||
282 | @defun current-word &optional strict really-word | |
283 | This function returns the symbol (or word) at or near point, as a string. | |
284 | The return value includes no text properties. | |
285 | ||
286 | If the optional argument @var{really-word} is non-@code{nil}, it finds a | |
287 | word; otherwise, it finds a symbol (which includes both word | |
288 | characters and symbol constituent characters). | |
289 | ||
290 | If the optional argument @var{strict} is non-@code{nil}, then point | |
291 | must be in or next to the symbol or word---if no symbol or word is | |
292 | there, the function returns @code{nil}. Otherwise, a nearby symbol or | |
293 | word on the same line is acceptable. | |
294 | @end defun | |
295 | ||
296 | @defun thing-at-point thing | |
297 | Return the @var{thing} around or next to point, as a string. | |
298 | ||
299 | The argument @var{thing} is a symbol which specifies a kind of syntactic | |
300 | entity. Possibilities include @code{symbol}, @code{list}, @code{sexp}, | |
301 | @code{defun}, @code{filename}, @code{url}, @code{word}, @code{sentence}, | |
302 | @code{whitespace}, @code{line}, @code{page}, and others. | |
303 | ||
304 | @example | |
305 | ---------- Buffer: foo ---------- | |
306 | Gentlemen may cry ``Pea@point{}ce! Peace!,'' | |
307 | but there is no peace. | |
308 | ---------- Buffer: foo ---------- | |
309 | ||
310 | (thing-at-point 'word) | |
311 | @result{} "Peace" | |
312 | (thing-at-point 'line) | |
313 | @result{} "Gentlemen may cry ``Peace! Peace!,''\n" | |
314 | (thing-at-point 'whitespace) | |
315 | @result{} nil | |
316 | @end example | |
317 | @end defun | |
318 | ||
319 | @node Comparing Text | |
320 | @section Comparing Text | |
321 | @cindex comparing buffer text | |
322 | ||
323 | This function lets you compare portions of the text in a buffer, without | |
324 | copying them into strings first. | |
325 | ||
326 | @defun compare-buffer-substrings buffer1 start1 end1 buffer2 start2 end2 | |
327 | This function lets you compare two substrings of the same buffer or two | |
328 | different buffers. The first three arguments specify one substring, | |
329 | giving a buffer (or a buffer name) and two positions within the | |
330 | buffer. The last three arguments specify the other substring in the | |
331 | same way. You can use @code{nil} for @var{buffer1}, @var{buffer2}, or | |
332 | both to stand for the current buffer. | |
333 | ||
334 | The value is negative if the first substring is less, positive if the | |
335 | first is greater, and zero if they are equal. The absolute value of | |
336 | the result is one plus the index of the first differing characters | |
337 | within the substrings. | |
338 | ||
339 | This function ignores case when comparing characters | |
340 | if @code{case-fold-search} is non-@code{nil}. It always ignores | |
341 | text properties. | |
342 | ||
343 | Suppose the current buffer contains the text @samp{foobarbar | |
344 | haha!rara!}; then in this example the two substrings are @samp{rbar } | |
345 | and @samp{rara!}. The value is 2 because the first substring is greater | |
346 | at the second character. | |
347 | ||
348 | @example | |
349 | (compare-buffer-substrings nil 6 11 nil 16 21) | |
350 | @result{} 2 | |
351 | @end example | |
352 | @end defun | |
353 | ||
354 | @node Insertion | |
355 | @section Inserting Text | |
356 | @cindex insertion of text | |
357 | @cindex text insertion | |
358 | ||
359 | @cindex insertion before point | |
360 | @cindex before point, insertion | |
361 | @dfn{Insertion} means adding new text to a buffer. The inserted text | |
362 | goes at point---between the character before point and the character | |
363 | after point. Some insertion functions leave point before the inserted | |
364 | text, while other functions leave it after. We call the former | |
365 | insertion @dfn{after point} and the latter insertion @dfn{before point}. | |
366 | ||
568f7b79 LMI |
367 | Insertion moves markers located at positions after the insertion |
368 | point, so that they stay with the surrounding text (@pxref{Markers}). | |
369 | When a marker points at the place of insertion, insertion may or may | |
370 | not relocate the marker, depending on the marker's insertion type | |
371 | (@pxref{Marker Insertion Types}). Certain special functions such as | |
372 | @code{insert-before-markers} relocate all such markers to point after | |
373 | the inserted text, regardless of the markers' insertion type. | |
b8d4c8d0 GM |
374 | |
375 | Insertion functions signal an error if the current buffer is | |
376 | read-only or if they insert within read-only text. | |
377 | ||
378 | These functions copy text characters from strings and buffers along | |
379 | with their properties. The inserted characters have exactly the same | |
380 | properties as the characters they were copied from. By contrast, | |
381 | characters specified as separate arguments, not part of a string or | |
382 | buffer, inherit their text properties from the neighboring text. | |
383 | ||
384 | The insertion functions convert text from unibyte to multibyte in | |
385 | order to insert in a multibyte buffer, and vice versa---if the text | |
386 | comes from a string or from a buffer. However, they do not convert | |
387 | unibyte character codes 128 through 255 to multibyte characters, not | |
388 | even if the current buffer is a multibyte buffer. @xref{Converting | |
389 | Representations}. | |
390 | ||
391 | @defun insert &rest args | |
392 | This function inserts the strings and/or characters @var{args} into the | |
393 | current buffer, at point, moving point forward. In other words, it | |
394 | inserts the text before point. An error is signaled unless all | |
395 | @var{args} are either strings or characters. The value is @code{nil}. | |
396 | @end defun | |
397 | ||
398 | @defun insert-before-markers &rest args | |
399 | This function inserts the strings and/or characters @var{args} into the | |
400 | current buffer, at point, moving point forward. An error is signaled | |
401 | unless all @var{args} are either strings or characters. The value is | |
402 | @code{nil}. | |
403 | ||
404 | This function is unlike the other insertion functions in that it | |
405 | relocates markers initially pointing at the insertion point, to point | |
406 | after the inserted text. If an overlay begins at the insertion point, | |
407 | the inserted text falls outside the overlay; if a nonempty overlay | |
408 | ends at the insertion point, the inserted text falls inside that | |
409 | overlay. | |
410 | @end defun | |
411 | ||
412 | @defun insert-char character count &optional inherit | |
413 | This function inserts @var{count} instances of @var{character} into the | |
414 | current buffer before point. The argument @var{count} should be an | |
415 | integer, and @var{character} must be a character. The value is @code{nil}. | |
416 | ||
417 | This function does not convert unibyte character codes 128 through 255 | |
418 | to multibyte characters, not even if the current buffer is a multibyte | |
419 | buffer. @xref{Converting Representations}. | |
420 | ||
421 | If @var{inherit} is non-@code{nil}, then the inserted characters inherit | |
422 | sticky text properties from the two characters before and after the | |
423 | insertion point. @xref{Sticky Properties}. | |
424 | @end defun | |
425 | ||
426 | @defun insert-buffer-substring from-buffer-or-name &optional start end | |
427 | This function inserts a portion of buffer @var{from-buffer-or-name} | |
428 | (which must already exist) into the current buffer before point. The | |
429 | text inserted is the region between @var{start} and @var{end}. (These | |
430 | arguments default to the beginning and end of the accessible portion of | |
431 | that buffer.) This function returns @code{nil}. | |
432 | ||
433 | In this example, the form is executed with buffer @samp{bar} as the | |
434 | current buffer. We assume that buffer @samp{bar} is initially empty. | |
435 | ||
436 | @example | |
437 | @group | |
438 | ---------- Buffer: foo ---------- | |
439 | We hold these truths to be self-evident, that all | |
440 | ---------- Buffer: foo ---------- | |
441 | @end group | |
442 | ||
443 | @group | |
444 | (insert-buffer-substring "foo" 1 20) | |
445 | @result{} nil | |
446 | ||
447 | ---------- Buffer: bar ---------- | |
448 | We hold these truth@point{} | |
449 | ---------- Buffer: bar ---------- | |
450 | @end group | |
451 | @end example | |
452 | @end defun | |
453 | ||
454 | @defun insert-buffer-substring-no-properties from-buffer-or-name &optional start end | |
455 | This is like @code{insert-buffer-substring} except that it does not | |
456 | copy any text properties. | |
457 | @end defun | |
458 | ||
459 | @xref{Sticky Properties}, for other insertion functions that inherit | |
460 | text properties from the nearby text in addition to inserting it. | |
461 | Whitespace inserted by indentation functions also inherits text | |
462 | properties. | |
463 | ||
464 | @node Commands for Insertion | |
465 | @section User-Level Insertion Commands | |
466 | ||
467 | This section describes higher-level commands for inserting text, | |
468 | commands intended primarily for the user but useful also in Lisp | |
469 | programs. | |
470 | ||
471 | @deffn Command insert-buffer from-buffer-or-name | |
472 | This command inserts the entire accessible contents of | |
473 | @var{from-buffer-or-name} (which must exist) into the current buffer | |
474 | after point. It leaves the mark after the inserted text. The value | |
475 | is @code{nil}. | |
476 | @end deffn | |
477 | ||
478 | @deffn Command self-insert-command count | |
479 | @cindex character insertion | |
480 | @cindex self-insertion | |
481 | This command inserts the last character typed; it does so @var{count} | |
482 | times, before point, and returns @code{nil}. Most printing characters | |
483 | are bound to this command. In routine use, @code{self-insert-command} | |
484 | is the most frequently called function in Emacs, but programs rarely use | |
485 | it except to install it on a keymap. | |
486 | ||
487 | In an interactive call, @var{count} is the numeric prefix argument. | |
488 | ||
ab992d66 EZ |
489 | Self-insertion translates the input character through |
490 | @code{translation-table-for-input}. @xref{Translation of Characters}. | |
491 | ||
b8d4c8d0 GM |
492 | This command calls @code{auto-fill-function} whenever that is |
493 | non-@code{nil} and the character inserted is in the table | |
494 | @code{auto-fill-chars} (@pxref{Auto Filling}). | |
495 | ||
496 | @c Cross refs reworded to prevent overfull hbox. --rjc 15mar92 | |
497 | This command performs abbrev expansion if Abbrev mode is enabled and | |
498 | the inserted character does not have word-constituent | |
499 | syntax. (@xref{Abbrevs}, and @ref{Syntax Class Table}.) It is also | |
500 | responsible for calling @code{blink-paren-function} when the inserted | |
501 | character has close parenthesis syntax (@pxref{Blinking}). | |
502 | ||
503 | Do not try substituting your own definition of | |
504 | @code{self-insert-command} for the standard one. The editor command | |
505 | loop handles this function specially. | |
506 | @end deffn | |
507 | ||
508 | @deffn Command newline &optional number-of-newlines | |
509 | This command inserts newlines into the current buffer before point. | |
510 | If @var{number-of-newlines} is supplied, that many newline characters | |
511 | are inserted. | |
512 | ||
513 | @cindex newline and Auto Fill mode | |
514 | This function calls @code{auto-fill-function} if the current column | |
515 | number is greater than the value of @code{fill-column} and | |
516 | @var{number-of-newlines} is @code{nil}. Typically what | |
517 | @code{auto-fill-function} does is insert a newline; thus, the overall | |
518 | result in this case is to insert two newlines at different places: one | |
519 | at point, and another earlier in the line. @code{newline} does not | |
520 | auto-fill if @var{number-of-newlines} is non-@code{nil}. | |
521 | ||
522 | This command indents to the left margin if that is not zero. | |
523 | @xref{Margins}. | |
524 | ||
525 | The value returned is @code{nil}. In an interactive call, @var{count} | |
526 | is the numeric prefix argument. | |
527 | @end deffn | |
528 | ||
529 | @defvar overwrite-mode | |
530 | This variable controls whether overwrite mode is in effect. The value | |
531 | should be @code{overwrite-mode-textual}, @code{overwrite-mode-binary}, | |
532 | or @code{nil}. @code{overwrite-mode-textual} specifies textual | |
533 | overwrite mode (treats newlines and tabs specially), and | |
534 | @code{overwrite-mode-binary} specifies binary overwrite mode (treats | |
535 | newlines and tabs like any other characters). | |
536 | @end defvar | |
537 | ||
538 | @node Deletion | |
539 | @section Deleting Text | |
540 | @cindex text deletion | |
541 | ||
542 | @cindex deleting text vs killing | |
543 | Deletion means removing part of the text in a buffer, without saving | |
544 | it in the kill ring (@pxref{The Kill Ring}). Deleted text can't be | |
545 | yanked, but can be reinserted using the undo mechanism (@pxref{Undo}). | |
546 | Some deletion functions do save text in the kill ring in some special | |
547 | cases. | |
548 | ||
549 | All of the deletion functions operate on the current buffer. | |
550 | ||
551 | @deffn Command erase-buffer | |
552 | This function deletes the entire text of the current buffer | |
553 | (@emph{not} just the accessible portion), leaving it | |
554 | empty. If the buffer is read-only, it signals a @code{buffer-read-only} | |
555 | error; if some of the text in it is read-only, it signals a | |
556 | @code{text-read-only} error. Otherwise, it deletes the text without | |
557 | asking for any confirmation. It returns @code{nil}. | |
558 | ||
559 | Normally, deleting a large amount of text from a buffer inhibits further | |
560 | auto-saving of that buffer ``because it has shrunk.'' However, | |
561 | @code{erase-buffer} does not do this, the idea being that the future | |
562 | text is not really related to the former text, and its size should not | |
563 | be compared with that of the former text. | |
564 | @end deffn | |
565 | ||
566 | @deffn Command delete-region start end | |
567 | This command deletes the text between positions @var{start} and | |
568 | @var{end} in the current buffer, and returns @code{nil}. If point was | |
569 | inside the deleted region, its value afterward is @var{start}. | |
570 | Otherwise, point relocates with the surrounding text, as markers do. | |
571 | @end deffn | |
572 | ||
573 | @defun delete-and-extract-region start end | |
574 | This function deletes the text between positions @var{start} and | |
575 | @var{end} in the current buffer, and returns a string containing the | |
576 | text just deleted. | |
577 | ||
578 | If point was inside the deleted region, its value afterward is | |
579 | @var{start}. Otherwise, point relocates with the surrounding text, as | |
580 | markers do. | |
581 | @end defun | |
582 | ||
583 | @deffn Command delete-char count &optional killp | |
584 | This command deletes @var{count} characters directly after point, or | |
585 | before point if @var{count} is negative. If @var{killp} is | |
586 | non-@code{nil}, then it saves the deleted characters in the kill ring. | |
587 | ||
588 | In an interactive call, @var{count} is the numeric prefix argument, and | |
589 | @var{killp} is the unprocessed prefix argument. Therefore, if a prefix | |
590 | argument is supplied, the text is saved in the kill ring. If no prefix | |
591 | argument is supplied, then one character is deleted, but not saved in | |
592 | the kill ring. | |
593 | ||
594 | The value returned is always @code{nil}. | |
595 | @end deffn | |
596 | ||
597 | @deffn Command delete-backward-char count &optional killp | |
598 | @cindex deleting previous char | |
599 | This command deletes @var{count} characters directly before point, or | |
600 | after point if @var{count} is negative. If @var{killp} is | |
601 | non-@code{nil}, then it saves the deleted characters in the kill ring. | |
602 | ||
603 | In an interactive call, @var{count} is the numeric prefix argument, and | |
604 | @var{killp} is the unprocessed prefix argument. Therefore, if a prefix | |
605 | argument is supplied, the text is saved in the kill ring. If no prefix | |
606 | argument is supplied, then one character is deleted, but not saved in | |
607 | the kill ring. | |
608 | ||
609 | The value returned is always @code{nil}. | |
610 | @end deffn | |
611 | ||
612 | @deffn Command backward-delete-char-untabify count &optional killp | |
613 | @cindex tab deletion | |
614 | This command deletes @var{count} characters backward, changing tabs | |
615 | into spaces. When the next character to be deleted is a tab, it is | |
616 | first replaced with the proper number of spaces to preserve alignment | |
617 | and then one of those spaces is deleted instead of the tab. If | |
618 | @var{killp} is non-@code{nil}, then the command saves the deleted | |
619 | characters in the kill ring. | |
620 | ||
621 | Conversion of tabs to spaces happens only if @var{count} is positive. | |
622 | If it is negative, exactly @minus{}@var{count} characters after point | |
623 | are deleted. | |
624 | ||
625 | In an interactive call, @var{count} is the numeric prefix argument, and | |
626 | @var{killp} is the unprocessed prefix argument. Therefore, if a prefix | |
627 | argument is supplied, the text is saved in the kill ring. If no prefix | |
628 | argument is supplied, then one character is deleted, but not saved in | |
629 | the kill ring. | |
630 | ||
631 | The value returned is always @code{nil}. | |
632 | @end deffn | |
633 | ||
634 | @defopt backward-delete-char-untabify-method | |
635 | This option specifies how @code{backward-delete-char-untabify} should | |
636 | deal with whitespace. Possible values include @code{untabify}, the | |
637 | default, meaning convert a tab to many spaces and delete one; | |
638 | @code{hungry}, meaning delete all tabs and spaces before point with | |
639 | one command; @code{all} meaning delete all tabs, spaces and newlines | |
640 | before point, and @code{nil}, meaning do nothing special for | |
641 | whitespace characters. | |
642 | @end defopt | |
643 | ||
644 | @node User-Level Deletion | |
645 | @section User-Level Deletion Commands | |
646 | ||
647 | This section describes higher-level commands for deleting text, | |
648 | commands intended primarily for the user but useful also in Lisp | |
649 | programs. | |
650 | ||
651 | @deffn Command delete-horizontal-space &optional backward-only | |
652 | @cindex deleting whitespace | |
653 | This function deletes all spaces and tabs around point. It returns | |
654 | @code{nil}. | |
655 | ||
656 | If @var{backward-only} is non-@code{nil}, the function deletes | |
657 | spaces and tabs before point, but not after point. | |
658 | ||
659 | In the following examples, we call @code{delete-horizontal-space} four | |
660 | times, once on each line, with point between the second and third | |
661 | characters on the line each time. | |
662 | ||
663 | @example | |
664 | @group | |
665 | ---------- Buffer: foo ---------- | |
666 | I @point{}thought | |
667 | I @point{} thought | |
668 | We@point{} thought | |
669 | Yo@point{}u thought | |
670 | ---------- Buffer: foo ---------- | |
671 | @end group | |
672 | ||
673 | @group | |
674 | (delete-horizontal-space) ; @r{Four times.} | |
675 | @result{} nil | |
676 | ||
677 | ---------- Buffer: foo ---------- | |
678 | Ithought | |
679 | Ithought | |
680 | Wethought | |
681 | You thought | |
682 | ---------- Buffer: foo ---------- | |
683 | @end group | |
684 | @end example | |
685 | @end deffn | |
686 | ||
687 | @deffn Command delete-indentation &optional join-following-p | |
688 | This function joins the line point is on to the previous line, deleting | |
689 | any whitespace at the join and in some cases replacing it with one | |
690 | space. If @var{join-following-p} is non-@code{nil}, | |
691 | @code{delete-indentation} joins this line to the following line | |
692 | instead. The function returns @code{nil}. | |
693 | ||
694 | If there is a fill prefix, and the second of the lines being joined | |
695 | starts with the prefix, then @code{delete-indentation} deletes the | |
696 | fill prefix before joining the lines. @xref{Margins}. | |
697 | ||
698 | In the example below, point is located on the line starting | |
699 | @samp{events}, and it makes no difference if there are trailing spaces | |
700 | in the preceding line. | |
701 | ||
702 | @smallexample | |
703 | @group | |
704 | ---------- Buffer: foo ---------- | |
705 | When in the course of human | |
706 | @point{} events, it becomes necessary | |
707 | ---------- Buffer: foo ---------- | |
708 | @end group | |
709 | ||
710 | (delete-indentation) | |
711 | @result{} nil | |
712 | ||
713 | @group | |
714 | ---------- Buffer: foo ---------- | |
715 | When in the course of human@point{} events, it becomes necessary | |
716 | ---------- Buffer: foo ---------- | |
717 | @end group | |
718 | @end smallexample | |
719 | ||
720 | After the lines are joined, the function @code{fixup-whitespace} is | |
721 | responsible for deciding whether to leave a space at the junction. | |
722 | @end deffn | |
723 | ||
724 | @deffn Command fixup-whitespace | |
725 | This function replaces all the horizontal whitespace surrounding point | |
726 | with either one space or no space, according to the context. It | |
727 | returns @code{nil}. | |
728 | ||
729 | At the beginning or end of a line, the appropriate amount of space is | |
730 | none. Before a character with close parenthesis syntax, or after a | |
731 | character with open parenthesis or expression-prefix syntax, no space is | |
732 | also appropriate. Otherwise, one space is appropriate. @xref{Syntax | |
733 | Class Table}. | |
734 | ||
735 | In the example below, @code{fixup-whitespace} is called the first time | |
736 | with point before the word @samp{spaces} in the first line. For the | |
737 | second invocation, point is directly after the @samp{(}. | |
738 | ||
739 | @smallexample | |
740 | @group | |
741 | ---------- Buffer: foo ---------- | |
742 | This has too many @point{}spaces | |
743 | This has too many spaces at the start of (@point{} this list) | |
744 | ---------- Buffer: foo ---------- | |
745 | @end group | |
746 | ||
747 | @group | |
748 | (fixup-whitespace) | |
749 | @result{} nil | |
750 | (fixup-whitespace) | |
751 | @result{} nil | |
752 | @end group | |
753 | ||
754 | @group | |
755 | ---------- Buffer: foo ---------- | |
756 | This has too many spaces | |
757 | This has too many spaces at the start of (this list) | |
758 | ---------- Buffer: foo ---------- | |
759 | @end group | |
760 | @end smallexample | |
761 | @end deffn | |
762 | ||
763 | @deffn Command just-one-space &optional n | |
764 | @comment !!SourceFile simple.el | |
765 | This command replaces any spaces and tabs around point with a single | |
766 | space, or @var{n} spaces if @var{n} is specified. It returns | |
767 | @code{nil}. | |
768 | @end deffn | |
769 | ||
770 | @deffn Command delete-blank-lines | |
771 | This function deletes blank lines surrounding point. If point is on a | |
772 | blank line with one or more blank lines before or after it, then all but | |
773 | one of them are deleted. If point is on an isolated blank line, then it | |
774 | is deleted. If point is on a nonblank line, the command deletes all | |
775 | blank lines immediately following it. | |
776 | ||
777 | A blank line is defined as a line containing only tabs and spaces. | |
778 | ||
779 | @code{delete-blank-lines} returns @code{nil}. | |
780 | @end deffn | |
781 | ||
782 | @node The Kill Ring | |
783 | @section The Kill Ring | |
784 | @cindex kill ring | |
785 | ||
786 | @dfn{Kill functions} delete text like the deletion functions, but save | |
787 | it so that the user can reinsert it by @dfn{yanking}. Most of these | |
788 | functions have @samp{kill-} in their name. By contrast, the functions | |
789 | whose names start with @samp{delete-} normally do not save text for | |
790 | yanking (though they can still be undone); these are ``deletion'' | |
791 | functions. | |
792 | ||
793 | Most of the kill commands are primarily for interactive use, and are | |
794 | not described here. What we do describe are the functions provided for | |
795 | use in writing such commands. You can use these functions to write | |
796 | commands for killing text. When you need to delete text for internal | |
797 | purposes within a Lisp function, you should normally use deletion | |
798 | functions, so as not to disturb the kill ring contents. | |
799 | @xref{Deletion}. | |
800 | ||
801 | Killed text is saved for later yanking in the @dfn{kill ring}. This | |
802 | is a list that holds a number of recent kills, not just the last text | |
803 | kill. We call this a ``ring'' because yanking treats it as having | |
804 | elements in a cyclic order. The list is kept in the variable | |
805 | @code{kill-ring}, and can be operated on with the usual functions for | |
806 | lists; there are also specialized functions, described in this section, | |
807 | that treat it as a ring. | |
808 | ||
809 | Some people think this use of the word ``kill'' is unfortunate, since | |
810 | it refers to operations that specifically @emph{do not} destroy the | |
811 | entities ``killed.'' This is in sharp contrast to ordinary life, in | |
812 | which death is permanent and ``killed'' entities do not come back to | |
813 | life. Therefore, other metaphors have been proposed. For example, the | |
814 | term ``cut ring'' makes sense to people who, in pre-computer days, used | |
815 | scissors and paste to cut up and rearrange manuscripts. However, it | |
816 | would be difficult to change the terminology now. | |
817 | ||
818 | @menu | |
819 | * Kill Ring Concepts:: What text looks like in the kill ring. | |
820 | * Kill Functions:: Functions that kill text. | |
821 | * Yanking:: How yanking is done. | |
822 | * Yank Commands:: Commands that access the kill ring. | |
d24880de | 823 | * Low-Level Kill Ring:: Functions and variables for kill ring access. |
b8d4c8d0 GM |
824 | * Internals of Kill Ring:: Variables that hold kill ring data. |
825 | @end menu | |
826 | ||
827 | @node Kill Ring Concepts | |
828 | @comment node-name, next, previous, up | |
829 | @subsection Kill Ring Concepts | |
830 | ||
831 | The kill ring records killed text as strings in a list, most recent | |
832 | first. A short kill ring, for example, might look like this: | |
833 | ||
834 | @example | |
835 | ("some text" "a different piece of text" "even older text") | |
836 | @end example | |
837 | ||
838 | @noindent | |
839 | When the list reaches @code{kill-ring-max} entries in length, adding a | |
840 | new entry automatically deletes the last entry. | |
841 | ||
842 | When kill commands are interwoven with other commands, each kill | |
843 | command makes a new entry in the kill ring. Multiple kill commands in | |
844 | succession build up a single kill ring entry, which would be yanked as a | |
845 | unit; the second and subsequent consecutive kill commands add text to | |
846 | the entry made by the first one. | |
847 | ||
848 | For yanking, one entry in the kill ring is designated the ``front'' of | |
849 | the ring. Some yank commands ``rotate'' the ring by designating a | |
850 | different element as the ``front.'' But this virtual rotation doesn't | |
851 | change the list itself---the most recent entry always comes first in the | |
852 | list. | |
853 | ||
854 | @node Kill Functions | |
855 | @comment node-name, next, previous, up | |
856 | @subsection Functions for Killing | |
857 | ||
858 | @code{kill-region} is the usual subroutine for killing text. Any | |
859 | command that calls this function is a ``kill command'' (and should | |
860 | probably have @samp{kill} in its name). @code{kill-region} puts the | |
861 | newly killed text in a new element at the beginning of the kill ring or | |
862 | adds it to the most recent element. It determines automatically (using | |
863 | @code{last-command}) whether the previous command was a kill command, | |
864 | and if so appends the killed text to the most recent entry. | |
865 | ||
ec8a6295 | 866 | @deffn Command kill-region start end |
b8d4c8d0 GM |
867 | This function kills the text in the region defined by @var{start} and |
868 | @var{end}. The text is deleted but saved in the kill ring, along with | |
869 | its text properties. The value is always @code{nil}. | |
870 | ||
871 | In an interactive call, @var{start} and @var{end} are point and | |
872 | the mark. | |
873 | ||
b8d4c8d0 GM |
874 | If the buffer or text is read-only, @code{kill-region} modifies the kill |
875 | ring just the same, then signals an error without modifying the buffer. | |
876 | This is convenient because it lets the user use a series of kill | |
877 | commands to copy text from a read-only buffer into the kill ring. | |
b8d4c8d0 GM |
878 | @end deffn |
879 | ||
880 | @defopt kill-read-only-ok | |
881 | If this option is non-@code{nil}, @code{kill-region} does not signal an | |
882 | error if the buffer or text is read-only. Instead, it simply returns, | |
883 | updating the kill ring but not changing the buffer. | |
884 | @end defopt | |
885 | ||
886 | @deffn Command copy-region-as-kill start end | |
887 | This command saves the region defined by @var{start} and @var{end} on | |
888 | the kill ring (including text properties), but does not delete the text | |
889 | from the buffer. It returns @code{nil}. | |
890 | ||
891 | The command does not set @code{this-command} to @code{kill-region}, so a | |
892 | subsequent kill command does not append to the same kill ring entry. | |
893 | ||
cde08ac9 GM |
894 | @c FIXME Why is it better? Why isn't copy-region-as-kill obsolete then? |
895 | @c Why is it used in many places in Emacs? | |
896 | In Lisp programs, it is better to use @code{kill-new} or | |
897 | @code{kill-append} instead of this command. @xref{Low-Level Kill Ring}. | |
b8d4c8d0 GM |
898 | @end deffn |
899 | ||
900 | @node Yanking | |
901 | @subsection Yanking | |
902 | ||
903 | Yanking means inserting text from the kill ring, but it does | |
904 | not insert the text blindly. Yank commands and some other commands | |
905 | use @code{insert-for-yank} to perform special processing on the | |
906 | text that they copy into the buffer. | |
907 | ||
908 | @defun insert-for-yank string | |
909 | This function normally works like @code{insert} except that it doesn't | |
50b063c3 CY |
910 | insert the text properties (@pxref{Text Properties}) in the list |
911 | variable @code{yank-excluded-properties}. However, if any part of | |
912 | @var{string} has a non-@code{nil} @code{yank-handler} text property, | |
913 | that property can do various special processing on that part of the | |
914 | text being inserted. | |
b8d4c8d0 GM |
915 | @end defun |
916 | ||
917 | @defun insert-buffer-substring-as-yank buf &optional start end | |
918 | This function resembles @code{insert-buffer-substring} except that it | |
919 | doesn't insert the text properties in the | |
920 | @code{yank-excluded-properties} list. | |
921 | @end defun | |
922 | ||
923 | You can put a @code{yank-handler} text property on all or part of | |
924 | the text to control how it will be inserted if it is yanked. The | |
925 | @code{insert-for-yank} function looks for that property. The property | |
926 | value must be a list of one to four elements, with the following | |
927 | format (where elements after the first may be omitted): | |
928 | ||
929 | @example | |
930 | (@var{function} @var{param} @var{noexclude} @var{undo}) | |
931 | @end example | |
932 | ||
933 | Here is what the elements do: | |
934 | ||
935 | @table @var | |
936 | @item function | |
937 | When @var{function} is present and non-@code{nil}, it is called instead of | |
938 | @code{insert} to insert the string. @var{function} takes one | |
939 | argument---the string to insert. | |
940 | ||
941 | @item param | |
942 | If @var{param} is present and non-@code{nil}, it replaces @var{string} | |
943 | (or the part of @var{string} being processed) as the object passed to | |
944 | @var{function} (or @code{insert}); for example, if @var{function} is | |
945 | @code{yank-rectangle}, @var{param} should be a list of strings to | |
946 | insert as a rectangle. | |
947 | ||
948 | @item noexclude | |
949 | If @var{noexclude} is present and non-@code{nil}, the normal removal of the | |
950 | yank-excluded-properties is not performed; instead @var{function} is | |
951 | responsible for removing those properties. This may be necessary | |
952 | if @var{function} adjusts point before or after inserting the object. | |
953 | ||
954 | @item undo | |
955 | If @var{undo} is present and non-@code{nil}, it is a function that will be | |
956 | called by @code{yank-pop} to undo the insertion of the current object. | |
957 | It is called with two arguments, the start and end of the current | |
958 | region. @var{function} can set @code{yank-undo-function} to override | |
959 | the @var{undo} value. | |
960 | @end table | |
961 | ||
50b063c3 CY |
962 | @cindex yanking and text properties |
963 | @defopt yank-excluded-properties | |
964 | Yanking discards certain text properties from the yanked text, as | |
965 | described above. The value of this variable is the list of properties | |
966 | to discard. Its default value contains properties that might lead to | |
967 | annoying results, such as causing the text to respond to the mouse or | |
968 | specifying key bindings. | |
969 | @end defopt | |
970 | ||
b8d4c8d0 GM |
971 | @node Yank Commands |
972 | @comment node-name, next, previous, up | |
973 | @subsection Functions for Yanking | |
974 | ||
975 | This section describes higher-level commands for yanking, which are | |
976 | intended primarily for the user but useful also in Lisp programs. | |
977 | Both @code{yank} and @code{yank-pop} honor the | |
978 | @code{yank-excluded-properties} variable and @code{yank-handler} text | |
979 | property (@pxref{Yanking}). | |
980 | ||
981 | @deffn Command yank &optional arg | |
982 | @cindex inserting killed text | |
2bad3299 CY |
983 | This command inserts before point the text at the front of the kill |
984 | ring. It sets the mark at the beginning of that text, using | |
985 | @code{push-mark} (@pxref{The Mark}), and puts point at the end. | |
b8d4c8d0 GM |
986 | |
987 | If @var{arg} is a non-@code{nil} list (which occurs interactively when | |
988 | the user types @kbd{C-u} with no digits), then @code{yank} inserts the | |
989 | text as described above, but puts point before the yanked text and | |
2bad3299 | 990 | sets the mark after it. |
b8d4c8d0 GM |
991 | |
992 | If @var{arg} is a number, then @code{yank} inserts the @var{arg}th | |
993 | most recently killed text---the @var{arg}th element of the kill ring | |
994 | list, counted cyclically from the front, which is considered the | |
995 | first element for this purpose. | |
996 | ||
997 | @code{yank} does not alter the contents of the kill ring, unless it | |
998 | used text provided by another program, in which case it pushes that text | |
999 | onto the kill ring. However if @var{arg} is an integer different from | |
1000 | one, it rotates the kill ring to place the yanked string at the front. | |
1001 | ||
1002 | @code{yank} returns @code{nil}. | |
1003 | @end deffn | |
1004 | ||
1005 | @deffn Command yank-pop &optional arg | |
1006 | This command replaces the just-yanked entry from the kill ring with a | |
1007 | different entry from the kill ring. | |
1008 | ||
1009 | This is allowed only immediately after a @code{yank} or another | |
1010 | @code{yank-pop}. At such a time, the region contains text that was just | |
1011 | inserted by yanking. @code{yank-pop} deletes that text and inserts in | |
1012 | its place a different piece of killed text. It does not add the deleted | |
1013 | text to the kill ring, since it is already in the kill ring somewhere. | |
1014 | It does however rotate the kill ring to place the newly yanked string at | |
1015 | the front. | |
1016 | ||
1017 | If @var{arg} is @code{nil}, then the replacement text is the previous | |
1018 | element of the kill ring. If @var{arg} is numeric, the replacement is | |
1019 | the @var{arg}th previous kill. If @var{arg} is negative, a more recent | |
1020 | kill is the replacement. | |
1021 | ||
1022 | The sequence of kills in the kill ring wraps around, so that after the | |
1023 | oldest one comes the newest one, and before the newest one goes the | |
1024 | oldest. | |
1025 | ||
1026 | The return value is always @code{nil}. | |
1027 | @end deffn | |
1028 | ||
1029 | @defvar yank-undo-function | |
1030 | If this variable is non-@code{nil}, the function @code{yank-pop} uses | |
1031 | its value instead of @code{delete-region} to delete the text | |
1032 | inserted by the previous @code{yank} or | |
1033 | @code{yank-pop} command. The value must be a function of two | |
1034 | arguments, the start and end of the current region. | |
1035 | ||
1036 | The function @code{insert-for-yank} automatically sets this variable | |
1037 | according to the @var{undo} element of the @code{yank-handler} | |
1038 | text property, if there is one. | |
1039 | @end defvar | |
1040 | ||
1041 | @node Low-Level Kill Ring | |
1042 | @subsection Low-Level Kill Ring | |
1043 | ||
1044 | These functions and variables provide access to the kill ring at a | |
cde08ac9 GM |
1045 | lower level, but are still convenient for use in Lisp programs, |
1046 | because they take care of interaction with window system selections | |
b8d4c8d0 GM |
1047 | (@pxref{Window System Selections}). |
1048 | ||
1049 | @defun current-kill n &optional do-not-move | |
1050 | The function @code{current-kill} rotates the yanking pointer, which | |
1051 | designates the ``front'' of the kill ring, by @var{n} places (from newer | |
1052 | kills to older ones), and returns the text at that place in the ring. | |
1053 | ||
1054 | If the optional second argument @var{do-not-move} is non-@code{nil}, | |
1055 | then @code{current-kill} doesn't alter the yanking pointer; it just | |
1056 | returns the @var{n}th kill, counting from the current yanking pointer. | |
1057 | ||
1058 | If @var{n} is zero, indicating a request for the latest kill, | |
1059 | @code{current-kill} calls the value of | |
1060 | @code{interprogram-paste-function} (documented below) before | |
1061 | consulting the kill ring. If that value is a function and calling it | |
8e8c1a72 EZ |
1062 | returns a string or a list of several string, @code{current-kill} |
1063 | pushes the strings onto the kill ring and returns the first string. | |
a053dae0 EZ |
1064 | It also sets the yanking pointer to point to the kill-ring entry of |
1065 | the first string returned by @code{interprogram-paste-function}, | |
8e8c1a72 EZ |
1066 | regardless of the value of @var{do-not-move}. Otherwise, |
1067 | @code{current-kill} does not treat a zero value for @var{n} specially: | |
1068 | it returns the entry pointed at by the yanking pointer and does not | |
1069 | move the yanking pointer. | |
b8d4c8d0 GM |
1070 | @end defun |
1071 | ||
ec8a6295 | 1072 | @defun kill-new string &optional replace |
b8d4c8d0 GM |
1073 | This function pushes the text @var{string} onto the kill ring and |
1074 | makes the yanking pointer point to it. It discards the oldest entry | |
1075 | if appropriate. It also invokes the value of | |
1076 | @code{interprogram-cut-function} (see below). | |
1077 | ||
1078 | If @var{replace} is non-@code{nil}, then @code{kill-new} replaces the | |
1079 | first element of the kill ring with @var{string}, rather than pushing | |
1080 | @var{string} onto the kill ring. | |
b8d4c8d0 GM |
1081 | @end defun |
1082 | ||
ec8a6295 | 1083 | @defun kill-append string before-p |
b8d4c8d0 GM |
1084 | This function appends the text @var{string} to the first entry in the |
1085 | kill ring and makes the yanking pointer point to the combined entry. | |
1086 | Normally @var{string} goes at the end of the entry, but if | |
1087 | @var{before-p} is non-@code{nil}, it goes at the beginning. This | |
1088 | function also invokes the value of @code{interprogram-cut-function} | |
ec8a6295 | 1089 | (see below). |
b8d4c8d0 GM |
1090 | @end defun |
1091 | ||
1092 | @defvar interprogram-paste-function | |
1093 | This variable provides a way of transferring killed text from other | |
1094 | programs, when you are using a window system. Its value should be | |
1095 | @code{nil} or a function of no arguments. | |
1096 | ||
1097 | If the value is a function, @code{current-kill} calls it to get the | |
1098 | ``most recent kill.'' If the function returns a non-@code{nil} value, | |
1099 | then that value is used as the ``most recent kill.'' If it returns | |
1100 | @code{nil}, then the front of the kill ring is used. | |
1101 | ||
8e8c1a72 EZ |
1102 | To facilitate support for window systems that support multiple |
1103 | selections, this function may also return a list of strings. In that | |
1104 | case, the first string is used as the ``most recent kill'', and all | |
1105 | the other strings are pushed onto the kill ring, for easy access by | |
1106 | @code{yank-pop}. | |
1107 | ||
1108 | The normal use of this function is to get the window system's primary | |
b8d4c8d0 | 1109 | selection as the most recent kill, even if the selection belongs to |
8e8c1a72 EZ |
1110 | another application. @xref{Window System Selections}. However, if |
1111 | the selection was provided by the current Emacs session, this function | |
1112 | should return @code{nil}. (If it is hard to tell whether Emacs or | |
1113 | some other program provided the selection, it should be good enough to | |
1114 | use @code{string=} to compare it with the last text Emacs provided.) | |
b8d4c8d0 GM |
1115 | @end defvar |
1116 | ||
1117 | @defvar interprogram-cut-function | |
1118 | This variable provides a way of communicating killed text to other | |
1119 | programs, when you are using a window system. Its value should be | |
45240125 | 1120 | @code{nil} or a function of one required argument. |
b8d4c8d0 GM |
1121 | |
1122 | If the value is a function, @code{kill-new} and @code{kill-append} call | |
45240125 | 1123 | it with the new first element of the kill ring as the argument. |
b8d4c8d0 | 1124 | |
8e8c1a72 | 1125 | The normal use of this function is to set the window system's primary |
45240125 | 1126 | selection from the newly killed text. |
b8d4c8d0 GM |
1127 | @xref{Window System Selections}. |
1128 | @end defvar | |
1129 | ||
1130 | @node Internals of Kill Ring | |
1131 | @comment node-name, next, previous, up | |
1132 | @subsection Internals of the Kill Ring | |
1133 | ||
1134 | The variable @code{kill-ring} holds the kill ring contents, in the | |
1135 | form of a list of strings. The most recent kill is always at the front | |
1136 | of the list. | |
1137 | ||
1138 | The @code{kill-ring-yank-pointer} variable points to a link in the | |
1139 | kill ring list, whose @sc{car} is the text to yank next. We say it | |
1140 | identifies the ``front'' of the ring. Moving | |
1141 | @code{kill-ring-yank-pointer} to a different link is called | |
1142 | @dfn{rotating the kill ring}. We call the kill ring a ``ring'' because | |
1143 | the functions that move the yank pointer wrap around from the end of the | |
1144 | list to the beginning, or vice-versa. Rotation of the kill ring is | |
1145 | virtual; it does not change the value of @code{kill-ring}. | |
1146 | ||
1147 | Both @code{kill-ring} and @code{kill-ring-yank-pointer} are Lisp | |
1148 | variables whose values are normally lists. The word ``pointer'' in the | |
1149 | name of the @code{kill-ring-yank-pointer} indicates that the variable's | |
1150 | purpose is to identify one element of the list for use by the next yank | |
1151 | command. | |
1152 | ||
1153 | The value of @code{kill-ring-yank-pointer} is always @code{eq} to one | |
1154 | of the links in the kill ring list. The element it identifies is the | |
1155 | @sc{car} of that link. Kill commands, which change the kill ring, also | |
1156 | set this variable to the value of @code{kill-ring}. The effect is to | |
1157 | rotate the ring so that the newly killed text is at the front. | |
1158 | ||
1159 | Here is a diagram that shows the variable @code{kill-ring-yank-pointer} | |
1160 | pointing to the second entry in the kill ring @code{("some text" "a | |
1161 | different piece of text" "yet older text")}. | |
1162 | ||
1163 | @example | |
1164 | @group | |
1165 | kill-ring ---- kill-ring-yank-pointer | |
1166 | | | | |
1167 | | v | |
1168 | | --- --- --- --- --- --- | |
1169 | --> | | |------> | | |--> | | |--> nil | |
1170 | --- --- --- --- --- --- | |
1171 | | | | | |
1172 | | | | | |
1173 | | | -->"yet older text" | |
1174 | | | | |
1175 | | --> "a different piece of text" | |
1176 | | | |
1177 | --> "some text" | |
1178 | @end group | |
1179 | @end example | |
1180 | ||
1181 | @noindent | |
1182 | This state of affairs might occur after @kbd{C-y} (@code{yank}) | |
1183 | immediately followed by @kbd{M-y} (@code{yank-pop}). | |
1184 | ||
1185 | @defvar kill-ring | |
1186 | This variable holds the list of killed text sequences, most recently | |
1187 | killed first. | |
1188 | @end defvar | |
1189 | ||
1190 | @defvar kill-ring-yank-pointer | |
1191 | This variable's value indicates which element of the kill ring is at the | |
1192 | ``front'' of the ring for yanking. More precisely, the value is a tail | |
1193 | of the value of @code{kill-ring}, and its @sc{car} is the kill string | |
1194 | that @kbd{C-y} should yank. | |
1195 | @end defvar | |
1196 | ||
1197 | @defopt kill-ring-max | |
1198 | The value of this variable is the maximum length to which the kill | |
1199 | ring can grow, before elements are thrown away at the end. The default | |
1200 | value for @code{kill-ring-max} is 60. | |
1201 | @end defopt | |
1202 | ||
1203 | @node Undo | |
1204 | @comment node-name, next, previous, up | |
1205 | @section Undo | |
1206 | @cindex redo | |
1207 | ||
1208 | Most buffers have an @dfn{undo list}, which records all changes made | |
1209 | to the buffer's text so that they can be undone. (The buffers that | |
1210 | don't have one are usually special-purpose buffers for which Emacs | |
1211 | assumes that undoing is not useful. In particular, any buffer whose | |
1212 | name begins with a space has its undo recording off by default; | |
1213 | see @ref{Buffer Names}.) All the primitives that modify the | |
1214 | text in the buffer automatically add elements to the front of the undo | |
1215 | list, which is in the variable @code{buffer-undo-list}. | |
1216 | ||
1217 | @defvar buffer-undo-list | |
1218 | This buffer-local variable's value is the undo list of the current | |
1219 | buffer. A value of @code{t} disables the recording of undo information. | |
1220 | @end defvar | |
1221 | ||
1222 | Here are the kinds of elements an undo list can have: | |
1223 | ||
1224 | @table @code | |
1225 | @item @var{position} | |
1226 | This kind of element records a previous value of point; undoing this | |
1227 | element moves point to @var{position}. Ordinary cursor motion does not | |
1228 | make any sort of undo record, but deletion operations use these entries | |
1229 | to record where point was before the command. | |
1230 | ||
1231 | @item (@var{beg} . @var{end}) | |
1232 | This kind of element indicates how to delete text that was inserted. | |
1233 | Upon insertion, the text occupied the range @var{beg}--@var{end} in the | |
1234 | buffer. | |
1235 | ||
1236 | @item (@var{text} . @var{position}) | |
1237 | This kind of element indicates how to reinsert text that was deleted. | |
1238 | The deleted text itself is the string @var{text}. The place to | |
1239 | reinsert it is @code{(abs @var{position})}. If @var{position} is | |
1240 | positive, point was at the beginning of the deleted text, otherwise it | |
1241 | was at the end. | |
1242 | ||
1243 | @item (t @var{high} . @var{low}) | |
1244 | This kind of element indicates that an unmodified buffer became | |
1245 | modified. The elements @var{high} and @var{low} are two integers, each | |
1246 | recording 16 bits of the visited file's modification time as of when it | |
1247 | was previously visited or saved. @code{primitive-undo} uses those | |
1248 | values to determine whether to mark the buffer as unmodified once again; | |
1249 | it does so only if the file's modification time matches those numbers. | |
1250 | ||
1251 | @item (nil @var{property} @var{value} @var{beg} . @var{end}) | |
1252 | This kind of element records a change in a text property. | |
1253 | Here's how you might undo the change: | |
1254 | ||
1255 | @example | |
1256 | (put-text-property @var{beg} @var{end} @var{property} @var{value}) | |
1257 | @end example | |
1258 | ||
1259 | @item (@var{marker} . @var{adjustment}) | |
1260 | This kind of element records the fact that the marker @var{marker} was | |
1261 | relocated due to deletion of surrounding text, and that it moved | |
1262 | @var{adjustment} character positions. Undoing this element moves | |
1263 | @var{marker} @minus{} @var{adjustment} characters. | |
1264 | ||
1265 | @item (apply @var{funname} . @var{args}) | |
1266 | This is an extensible undo item, which is undone by calling | |
1267 | @var{funname} with arguments @var{args}. | |
1268 | ||
1269 | @item (apply @var{delta} @var{beg} @var{end} @var{funname} . @var{args}) | |
1270 | This is an extensible undo item, which records a change limited to the | |
1271 | range @var{beg} to @var{end}, which increased the size of the buffer | |
1272 | by @var{delta}. It is undone by calling @var{funname} with arguments | |
1273 | @var{args}. | |
1274 | ||
1275 | This kind of element enables undo limited to a region to determine | |
1276 | whether the element pertains to that region. | |
1277 | ||
1278 | @item nil | |
1279 | This element is a boundary. The elements between two boundaries are | |
1280 | called a @dfn{change group}; normally, each change group corresponds to | |
1281 | one keyboard command, and undo commands normally undo an entire group as | |
1282 | a unit. | |
1283 | @end table | |
1284 | ||
1285 | @defun undo-boundary | |
1286 | This function places a boundary element in the undo list. The undo | |
1287 | command stops at such a boundary, and successive undo commands undo | |
1288 | to earlier and earlier boundaries. This function returns @code{nil}. | |
1289 | ||
51422d6d CY |
1290 | The editor command loop automatically calls @code{undo-boundary} just |
1291 | before executing each key sequence, so that each undo normally undoes | |
1292 | the effects of one command. As an exception, the command | |
1293 | @code{self-insert-command}, which produces self-inserting input | |
1294 | characters (@pxref{Commands for Insertion}), may remove the boundary | |
1295 | inserted by the command loop: a boundary is accepted for the first | |
1296 | such character, the next 19 consecutive self-inserting input | |
1297 | characters do not have boundaries, and then the 20th does; and so on | |
1298 | as long as the self-inserting characters continue. Hence, sequences | |
1299 | of consecutive character insertions can be undone as a group. | |
b8d4c8d0 GM |
1300 | |
1301 | All buffer modifications add a boundary whenever the previous undoable | |
1302 | change was made in some other buffer. This is to ensure that | |
1303 | each command makes a boundary in each buffer where it makes changes. | |
1304 | ||
1305 | Calling this function explicitly is useful for splitting the effects of | |
1306 | a command into more than one unit. For example, @code{query-replace} | |
1307 | calls @code{undo-boundary} after each replacement, so that the user can | |
1308 | undo individual replacements one by one. | |
1309 | @end defun | |
1310 | ||
1311 | @defvar undo-in-progress | |
1312 | This variable is normally @code{nil}, but the undo commands bind it to | |
1313 | @code{t}. This is so that various kinds of change hooks can tell when | |
1314 | they're being called for the sake of undoing. | |
1315 | @end defvar | |
1316 | ||
1317 | @defun primitive-undo count list | |
1318 | This is the basic function for undoing elements of an undo list. | |
1319 | It undoes the first @var{count} elements of @var{list}, returning | |
1320 | the rest of @var{list}. | |
1321 | ||
1322 | @code{primitive-undo} adds elements to the buffer's undo list when it | |
1323 | changes the buffer. Undo commands avoid confusion by saving the undo | |
1324 | list value at the beginning of a sequence of undo operations. Then the | |
1325 | undo operations use and update the saved value. The new elements added | |
1326 | by undoing are not part of this saved value, so they don't interfere with | |
1327 | continuing to undo. | |
1328 | ||
1329 | This function does not bind @code{undo-in-progress}. | |
1330 | @end defun | |
1331 | ||
1332 | @node Maintaining Undo | |
1333 | @section Maintaining Undo Lists | |
1334 | ||
1335 | This section describes how to enable and disable undo information for | |
1336 | a given buffer. It also explains how the undo list is truncated | |
1337 | automatically so it doesn't get too big. | |
1338 | ||
1339 | Recording of undo information in a newly created buffer is normally | |
1340 | enabled to start with; but if the buffer name starts with a space, the | |
1341 | undo recording is initially disabled. You can explicitly enable or | |
1342 | disable undo recording with the following two functions, or by setting | |
1343 | @code{buffer-undo-list} yourself. | |
1344 | ||
1345 | @deffn Command buffer-enable-undo &optional buffer-or-name | |
1346 | This command enables recording undo information for buffer | |
1347 | @var{buffer-or-name}, so that subsequent changes can be undone. If no | |
1348 | argument is supplied, then the current buffer is used. This function | |
1349 | does nothing if undo recording is already enabled in the buffer. It | |
1350 | returns @code{nil}. | |
1351 | ||
1352 | In an interactive call, @var{buffer-or-name} is the current buffer. | |
1353 | You cannot specify any other buffer. | |
1354 | @end deffn | |
1355 | ||
1356 | @deffn Command buffer-disable-undo &optional buffer-or-name | |
1357 | @cindex disabling undo | |
1358 | This function discards the undo list of @var{buffer-or-name}, and disables | |
1359 | further recording of undo information. As a result, it is no longer | |
1360 | possible to undo either previous changes or any subsequent changes. If | |
1361 | the undo list of @var{buffer-or-name} is already disabled, this function | |
1362 | has no effect. | |
1363 | ||
1364 | This function returns @code{nil}. | |
1365 | @end deffn | |
1366 | ||
1367 | As editing continues, undo lists get longer and longer. To prevent | |
1368 | them from using up all available memory space, garbage collection trims | |
1369 | them back to size limits you can set. (For this purpose, the ``size'' | |
1370 | of an undo list measures the cons cells that make up the list, plus the | |
1371 | strings of deleted text.) Three variables control the range of acceptable | |
1372 | sizes: @code{undo-limit}, @code{undo-strong-limit} and | |
1373 | @code{undo-outer-limit}. In these variables, size is counted as the | |
1374 | number of bytes occupied, which includes both saved text and other | |
1375 | data. | |
1376 | ||
1377 | @defopt undo-limit | |
1378 | This is the soft limit for the acceptable size of an undo list. The | |
1379 | change group at which this size is exceeded is the last one kept. | |
1380 | @end defopt | |
1381 | ||
1382 | @defopt undo-strong-limit | |
1383 | This is the upper limit for the acceptable size of an undo list. The | |
1384 | change group at which this size is exceeded is discarded itself (along | |
1385 | with all older change groups). There is one exception: the very latest | |
1386 | change group is only discarded if it exceeds @code{undo-outer-limit}. | |
1387 | @end defopt | |
1388 | ||
1389 | @defopt undo-outer-limit | |
1390 | If at garbage collection time the undo info for the current command | |
1391 | exceeds this limit, Emacs discards the info and displays a warning. | |
1392 | This is a last ditch limit to prevent memory overflow. | |
1393 | @end defopt | |
1394 | ||
1395 | @defopt undo-ask-before-discard | |
1396 | If this variable is non-@code{nil}, when the undo info exceeds | |
1397 | @code{undo-outer-limit}, Emacs asks in the echo area whether to | |
1398 | discard the info. The default value is @code{nil}, which means to | |
1399 | discard it automatically. | |
1400 | ||
1401 | This option is mainly intended for debugging. Garbage collection is | |
1402 | inhibited while the question is asked, which means that Emacs might | |
1403 | leak memory if the user waits too long before answering the question. | |
1404 | @end defopt | |
1405 | ||
1406 | @node Filling | |
1407 | @comment node-name, next, previous, up | |
1408 | @section Filling | |
1409 | @cindex filling text | |
1410 | ||
1411 | @dfn{Filling} means adjusting the lengths of lines (by moving the line | |
1412 | breaks) so that they are nearly (but no greater than) a specified | |
1413 | maximum width. Additionally, lines can be @dfn{justified}, which means | |
1414 | inserting spaces to make the left and/or right margins line up | |
1415 | precisely. The width is controlled by the variable @code{fill-column}. | |
1416 | For ease of reading, lines should be no longer than 70 or so columns. | |
1417 | ||
1418 | You can use Auto Fill mode (@pxref{Auto Filling}) to fill text | |
1419 | automatically as you insert it, but changes to existing text may leave | |
1420 | it improperly filled. Then you must fill the text explicitly. | |
1421 | ||
1422 | Most of the commands in this section return values that are not | |
1423 | meaningful. All the functions that do filling take note of the current | |
1424 | left margin, current right margin, and current justification style | |
1425 | (@pxref{Margins}). If the current justification style is | |
1426 | @code{none}, the filling functions don't actually do anything. | |
1427 | ||
1428 | Several of the filling functions have an argument @var{justify}. | |
1429 | If it is non-@code{nil}, that requests some kind of justification. It | |
1430 | can be @code{left}, @code{right}, @code{full}, or @code{center}, to | |
1431 | request a specific style of justification. If it is @code{t}, that | |
1432 | means to use the current justification style for this part of the text | |
1433 | (see @code{current-justification}, below). Any other value is treated | |
1434 | as @code{full}. | |
1435 | ||
1436 | When you call the filling functions interactively, using a prefix | |
1437 | argument implies the value @code{full} for @var{justify}. | |
1438 | ||
65ced25f | 1439 | @deffn Command fill-paragraph &optional justify region |
b8d4c8d0 GM |
1440 | This command fills the paragraph at or after point. If |
1441 | @var{justify} is non-@code{nil}, each line is justified as well. | |
1442 | It uses the ordinary paragraph motion commands to find paragraph | |
1443 | boundaries. @xref{Paragraphs,,, emacs, The GNU Emacs Manual}. | |
2bad3299 CY |
1444 | |
1445 | When @var{region} is non-@code{nil}, then if Transient Mark mode is | |
1446 | enabled and the mark is active, this command calls @code{fill-region} | |
1447 | to fill all the paragraphs in the region, instead of filling only the | |
1448 | current paragraph. When this command is called interactively, | |
1449 | @var{region} is @code{t}. | |
b8d4c8d0 GM |
1450 | @end deffn |
1451 | ||
1452 | @deffn Command fill-region start end &optional justify nosqueeze to-eop | |
1453 | This command fills each of the paragraphs in the region from @var{start} | |
1454 | to @var{end}. It justifies as well if @var{justify} is | |
1455 | non-@code{nil}. | |
1456 | ||
1457 | If @var{nosqueeze} is non-@code{nil}, that means to leave whitespace | |
1458 | other than line breaks untouched. If @var{to-eop} is non-@code{nil}, | |
1459 | that means to keep filling to the end of the paragraph---or the next hard | |
1460 | newline, if @code{use-hard-newlines} is enabled (see below). | |
1461 | ||
1462 | The variable @code{paragraph-separate} controls how to distinguish | |
1463 | paragraphs. @xref{Standard Regexps}. | |
1464 | @end deffn | |
1465 | ||
1466 | @deffn Command fill-individual-paragraphs start end &optional justify citation-regexp | |
1467 | This command fills each paragraph in the region according to its | |
1468 | individual fill prefix. Thus, if the lines of a paragraph were indented | |
1469 | with spaces, the filled paragraph will remain indented in the same | |
1470 | fashion. | |
1471 | ||
1472 | The first two arguments, @var{start} and @var{end}, are the beginning | |
1473 | and end of the region to be filled. The third and fourth arguments, | |
1474 | @var{justify} and @var{citation-regexp}, are optional. If | |
1475 | @var{justify} is non-@code{nil}, the paragraphs are justified as | |
1476 | well as filled. If @var{citation-regexp} is non-@code{nil}, it means the | |
1477 | function is operating on a mail message and therefore should not fill | |
1478 | the header lines. If @var{citation-regexp} is a string, it is used as | |
1479 | a regular expression; if it matches the beginning of a line, that line | |
1480 | is treated as a citation marker. | |
1481 | ||
1482 | Ordinarily, @code{fill-individual-paragraphs} regards each change in | |
1483 | indentation as starting a new paragraph. If | |
1484 | @code{fill-individual-varying-indent} is non-@code{nil}, then only | |
1485 | separator lines separate paragraphs. That mode can handle indented | |
1486 | paragraphs with additional indentation on the first line. | |
1487 | @end deffn | |
1488 | ||
1489 | @defopt fill-individual-varying-indent | |
1490 | This variable alters the action of @code{fill-individual-paragraphs} as | |
1491 | described above. | |
1492 | @end defopt | |
1493 | ||
1494 | @deffn Command fill-region-as-paragraph start end &optional justify nosqueeze squeeze-after | |
1495 | This command considers a region of text as a single paragraph and fills | |
1496 | it. If the region was made up of many paragraphs, the blank lines | |
1497 | between paragraphs are removed. This function justifies as well as | |
1498 | filling when @var{justify} is non-@code{nil}. | |
1499 | ||
1500 | If @var{nosqueeze} is non-@code{nil}, that means to leave whitespace | |
1501 | other than line breaks untouched. If @var{squeeze-after} is | |
1502 | non-@code{nil}, it specifies a position in the region, and means don't | |
1503 | canonicalize spaces before that position. | |
1504 | ||
1505 | In Adaptive Fill mode, this command calls @code{fill-context-prefix} to | |
1506 | choose a fill prefix by default. @xref{Adaptive Fill}. | |
1507 | @end deffn | |
1508 | ||
1509 | @deffn Command justify-current-line &optional how eop nosqueeze | |
1510 | This command inserts spaces between the words of the current line so | |
1511 | that the line ends exactly at @code{fill-column}. It returns | |
1512 | @code{nil}. | |
1513 | ||
1514 | The argument @var{how}, if non-@code{nil} specifies explicitly the style | |
1515 | of justification. It can be @code{left}, @code{right}, @code{full}, | |
1516 | @code{center}, or @code{none}. If it is @code{t}, that means to do | |
1517 | follow specified justification style (see @code{current-justification}, | |
1518 | below). @code{nil} means to do full justification. | |
1519 | ||
1520 | If @var{eop} is non-@code{nil}, that means do only left-justification | |
1521 | if @code{current-justification} specifies full justification. This is | |
1522 | used for the last line of a paragraph; even if the paragraph as a | |
1523 | whole is fully justified, the last line should not be. | |
1524 | ||
1525 | If @var{nosqueeze} is non-@code{nil}, that means do not change interior | |
1526 | whitespace. | |
1527 | @end deffn | |
1528 | ||
1529 | @defopt default-justification | |
1530 | This variable's value specifies the style of justification to use for | |
1531 | text that doesn't specify a style with a text property. The possible | |
1532 | values are @code{left}, @code{right}, @code{full}, @code{center}, or | |
1533 | @code{none}. The default value is @code{left}. | |
1534 | @end defopt | |
1535 | ||
1536 | @defun current-justification | |
1537 | This function returns the proper justification style to use for filling | |
1538 | the text around point. | |
1539 | ||
1540 | This returns the value of the @code{justification} text property at | |
1541 | point, or the variable @var{default-justification} if there is no such | |
1542 | text property. However, it returns @code{nil} rather than @code{none} | |
1543 | to mean ``don't justify''. | |
1544 | @end defun | |
1545 | ||
1546 | @defopt sentence-end-double-space | |
1547 | @anchor{Definition of sentence-end-double-space} | |
1548 | If this variable is non-@code{nil}, a period followed by just one space | |
1549 | does not count as the end of a sentence, and the filling functions | |
1550 | avoid breaking the line at such a place. | |
1551 | @end defopt | |
1552 | ||
1553 | @defopt sentence-end-without-period | |
1554 | If this variable is non-@code{nil}, a sentence can end without a | |
1555 | period. This is used for languages like Thai, where sentences end | |
1556 | with a double space but without a period. | |
1557 | @end defopt | |
1558 | ||
1559 | @defopt sentence-end-without-space | |
1560 | If this variable is non-@code{nil}, it should be a string of | |
1561 | characters that can end a sentence without following spaces. | |
1562 | @end defopt | |
1563 | ||
1564 | @defvar fill-paragraph-function | |
2bad3299 CY |
1565 | This variable provides a way to override the filling of paragraphs. |
1566 | If its value is non-@code{nil}, @code{fill-paragraph} calls this | |
1567 | function to do the work. If the function returns a non-@code{nil} | |
b8d4c8d0 GM |
1568 | value, @code{fill-paragraph} assumes the job is done, and immediately |
1569 | returns that value. | |
1570 | ||
1571 | The usual use of this feature is to fill comments in programming | |
1572 | language modes. If the function needs to fill a paragraph in the usual | |
1573 | way, it can do so as follows: | |
1574 | ||
1575 | @example | |
1576 | (let ((fill-paragraph-function nil)) | |
1577 | (fill-paragraph arg)) | |
1578 | @end example | |
1579 | @end defvar | |
1580 | ||
2bad3299 CY |
1581 | @defvar fill-forward-paragraph-function |
1582 | This variable provides a way to override how the filling functions, | |
1583 | such as @code{fill-region} and @code{fill-paragraph}, move forward to | |
1584 | the next paragraph. Its value should be a function, which is called | |
1585 | with a single argument @var{n}, the number of paragraphs to move, and | |
1586 | should return the difference between @var{n} and the number of | |
1587 | paragraphs actually moved. The default value of this variable is | |
1588 | @code{forward-paragraph}. @xref{Paragraphs,,, emacs, The GNU Emacs | |
1589 | Manual}. | |
1590 | @end defvar | |
1591 | ||
b8d4c8d0 GM |
1592 | @defvar use-hard-newlines |
1593 | If this variable is non-@code{nil}, the filling functions do not delete | |
1594 | newlines that have the @code{hard} text property. These ``hard | |
1595 | newlines'' act as paragraph separators. | |
1596 | @end defvar | |
1597 | ||
1598 | @node Margins | |
1599 | @section Margins for Filling | |
1600 | ||
1601 | @defopt fill-prefix | |
1602 | This buffer-local variable, if non-@code{nil}, specifies a string of | |
1603 | text that appears at the beginning of normal text lines and should be | |
1604 | disregarded when filling them. Any line that fails to start with the | |
1605 | fill prefix is considered the start of a paragraph; so is any line | |
1606 | that starts with the fill prefix followed by additional whitespace. | |
1607 | Lines that start with the fill prefix but no additional whitespace are | |
1608 | ordinary text lines that can be filled together. The resulting filled | |
1609 | lines also start with the fill prefix. | |
1610 | ||
1611 | The fill prefix follows the left margin whitespace, if any. | |
1612 | @end defopt | |
1613 | ||
1614 | @defopt fill-column | |
1615 | This buffer-local variable specifies the maximum width of filled lines. | |
1616 | Its value should be an integer, which is a number of columns. All the | |
1617 | filling, justification, and centering commands are affected by this | |
1618 | variable, including Auto Fill mode (@pxref{Auto Filling}). | |
1619 | ||
1620 | As a practical matter, if you are writing text for other people to | |
1621 | read, you should set @code{fill-column} to no more than 70. Otherwise | |
1622 | the line will be too long for people to read comfortably, and this can | |
1623 | make the text seem clumsy. | |
b8d4c8d0 | 1624 | |
4e3b4528 SM |
1625 | The default value for @code{fill-column} is 70. |
1626 | @end defopt | |
b8d4c8d0 GM |
1627 | |
1628 | @deffn Command set-left-margin from to margin | |
1629 | This sets the @code{left-margin} property on the text from @var{from} to | |
1630 | @var{to} to the value @var{margin}. If Auto Fill mode is enabled, this | |
1631 | command also refills the region to fit the new margin. | |
1632 | @end deffn | |
1633 | ||
1634 | @deffn Command set-right-margin from to margin | |
1635 | This sets the @code{right-margin} property on the text from @var{from} | |
1636 | to @var{to} to the value @var{margin}. If Auto Fill mode is enabled, | |
1637 | this command also refills the region to fit the new margin. | |
1638 | @end deffn | |
1639 | ||
1640 | @defun current-left-margin | |
1641 | This function returns the proper left margin value to use for filling | |
1642 | the text around point. The value is the sum of the @code{left-margin} | |
1643 | property of the character at the start of the current line (or zero if | |
1644 | none), and the value of the variable @code{left-margin}. | |
1645 | @end defun | |
1646 | ||
1647 | @defun current-fill-column | |
1648 | This function returns the proper fill column value to use for filling | |
1649 | the text around point. The value is the value of the @code{fill-column} | |
1650 | variable, minus the value of the @code{right-margin} property of the | |
1651 | character after point. | |
1652 | @end defun | |
1653 | ||
1654 | @deffn Command move-to-left-margin &optional n force | |
1655 | This function moves point to the left margin of the current line. The | |
1656 | column moved to is determined by calling the function | |
1657 | @code{current-left-margin}. If the argument @var{n} is non-@code{nil}, | |
1658 | @code{move-to-left-margin} moves forward @var{n}@minus{}1 lines first. | |
1659 | ||
1660 | If @var{force} is non-@code{nil}, that says to fix the line's | |
1661 | indentation if that doesn't match the left margin value. | |
1662 | @end deffn | |
1663 | ||
1664 | @defun delete-to-left-margin &optional from to | |
1665 | This function removes left margin indentation from the text between | |
1666 | @var{from} and @var{to}. The amount of indentation to delete is | |
1667 | determined by calling @code{current-left-margin}. In no case does this | |
1668 | function delete non-whitespace. If @var{from} and @var{to} are omitted, | |
1669 | they default to the whole buffer. | |
1670 | @end defun | |
1671 | ||
1672 | @defun indent-to-left-margin | |
1673 | This function adjusts the indentation at the beginning of the current | |
1674 | line to the value specified by the variable @code{left-margin}. (That | |
1675 | may involve either inserting or deleting whitespace.) This function | |
1676 | is value of @code{indent-line-function} in Paragraph-Indent Text mode. | |
1677 | @end defun | |
1678 | ||
01f17ae2 | 1679 | @defopt left-margin |
b8d4c8d0 GM |
1680 | This variable specifies the base left margin column. In Fundamental |
1681 | mode, @kbd{C-j} indents to this column. This variable automatically | |
1682 | becomes buffer-local when set in any fashion. | |
01f17ae2 | 1683 | @end defopt |
b8d4c8d0 | 1684 | |
01f17ae2 | 1685 | @defopt fill-nobreak-predicate |
b8d4c8d0 GM |
1686 | This variable gives major modes a way to specify not to break a line |
1687 | at certain places. Its value should be a list of functions. Whenever | |
1688 | filling considers breaking the line at a certain place in the buffer, | |
1689 | it calls each of these functions with no arguments and with point | |
1690 | located at that place. If any of the functions returns | |
1691 | non-@code{nil}, then the line won't be broken there. | |
01f17ae2 | 1692 | @end defopt |
b8d4c8d0 GM |
1693 | |
1694 | @node Adaptive Fill | |
1695 | @section Adaptive Fill Mode | |
1696 | @c @cindex Adaptive Fill mode "adaptive-fill-mode" is adjacent. | |
1697 | ||
1698 | When @dfn{Adaptive Fill Mode} is enabled, Emacs determines the fill | |
1699 | prefix automatically from the text in each paragraph being filled | |
1700 | rather than using a predetermined value. During filling, this fill | |
1701 | prefix gets inserted at the start of the second and subsequent lines | |
1702 | of the paragraph as described in @ref{Filling}, and in @ref{Auto | |
1703 | Filling}. | |
1704 | ||
1705 | @defopt adaptive-fill-mode | |
1706 | Adaptive Fill mode is enabled when this variable is non-@code{nil}. | |
1707 | It is @code{t} by default. | |
1708 | @end defopt | |
1709 | ||
1710 | @defun fill-context-prefix from to | |
1711 | This function implements the heart of Adaptive Fill mode; it chooses a | |
1712 | fill prefix based on the text between @var{from} and @var{to}, | |
1713 | typically the start and end of a paragraph. It does this by looking | |
1714 | at the first two lines of the paragraph, based on the variables | |
1715 | described below. | |
1716 | @c The optional argument first-line-regexp is not documented | |
1717 | @c because it exists for internal purposes and might be eliminated | |
1718 | @c in the future. | |
1719 | ||
1720 | Usually, this function returns the fill prefix, a string. However, | |
1721 | before doing this, the function makes a final check (not specially | |
1722 | mentioned in the following) that a line starting with this prefix | |
1723 | wouldn't look like the start of a paragraph. Should this happen, the | |
1724 | function signals the anomaly by returning @code{nil} instead. | |
1725 | ||
1726 | In detail, @code{fill-context-prefix} does this: | |
1727 | ||
1728 | @enumerate | |
1729 | @item | |
1730 | It takes a candidate for the fill prefix from the first line---it | |
1731 | tries first the function in @code{adaptive-fill-function} (if any), | |
1732 | then the regular expression @code{adaptive-fill-regexp} (see below). | |
1733 | The first non-@code{nil} result of these, or the empty string if | |
1734 | they're both @code{nil}, becomes the first line's candidate. | |
1735 | @item | |
1736 | If the paragraph has as yet only one line, the function tests the | |
1737 | validity of the prefix candidate just found. The function then | |
1738 | returns the candidate if it's valid, or a string of spaces otherwise. | |
1739 | (see the description of @code{adaptive-fill-first-line-regexp} below). | |
1740 | @item | |
1741 | When the paragraph already has two lines, the function next looks for | |
1742 | a prefix candidate on the second line, in just the same way it did for | |
1743 | the first line. If it doesn't find one, it returns @code{nil}. | |
1744 | @item | |
1745 | The function now compares the two candidate prefixes heuristically: if | |
1746 | the non-whitespace characters in the line 2 candidate occur in the | |
1747 | same order in the line 1 candidate, the function returns the line 2 | |
1748 | candidate. Otherwise, it returns the largest initial substring which | |
1749 | is common to both candidates (which might be the empty string). | |
1750 | @end enumerate | |
1751 | @end defun | |
1752 | ||
1753 | @defopt adaptive-fill-regexp | |
1754 | Adaptive Fill mode matches this regular expression against the text | |
1755 | starting after the left margin whitespace (if any) on a line; the | |
1756 | characters it matches are that line's candidate for the fill prefix. | |
1757 | ||
1758 | The default value matches whitespace with certain punctuation | |
1759 | characters intermingled. | |
1760 | @end defopt | |
1761 | ||
1762 | @defopt adaptive-fill-first-line-regexp | |
1763 | Used only in one-line paragraphs, this regular expression acts as an | |
1764 | additional check of the validity of the one available candidate fill | |
1765 | prefix: the candidate must match this regular expression, or match | |
1766 | @code{comment-start-skip}. If it doesn't, @code{fill-context-prefix} | |
1767 | replaces the candidate with a string of spaces ``of the same width'' | |
1768 | as it. | |
1769 | ||
1770 | The default value of this variable is @w{@code{"\\`[ \t]*\\'"}}, which | |
1771 | matches only a string of whitespace. The effect of this default is to | |
1772 | force the fill prefixes found in one-line paragraphs always to be pure | |
1773 | whitespace. | |
1774 | @end defopt | |
1775 | ||
1776 | @defopt adaptive-fill-function | |
1777 | You can specify more complex ways of choosing a fill prefix | |
1778 | automatically by setting this variable to a function. The function is | |
1779 | called with point after the left margin (if any) of a line, and it | |
1780 | must preserve point. It should return either ``that line's'' fill | |
1781 | prefix or @code{nil}, meaning it has failed to determine a prefix. | |
1782 | @end defopt | |
1783 | ||
1784 | @node Auto Filling | |
1785 | @comment node-name, next, previous, up | |
1786 | @section Auto Filling | |
1787 | @cindex filling, automatic | |
1788 | @cindex Auto Fill mode | |
1789 | ||
1790 | Auto Fill mode is a minor mode that fills lines automatically as text | |
1791 | is inserted. This section describes the hook used by Auto Fill mode. | |
1792 | For a description of functions that you can call explicitly to fill and | |
1793 | justify existing text, see @ref{Filling}. | |
1794 | ||
1795 | Auto Fill mode also enables the functions that change the margins and | |
1796 | justification style to refill portions of the text. @xref{Margins}. | |
1797 | ||
1798 | @defvar auto-fill-function | |
1799 | The value of this buffer-local variable should be a function (of no | |
1800 | arguments) to be called after self-inserting a character from the table | |
1801 | @code{auto-fill-chars}. It may be @code{nil}, in which case nothing | |
1802 | special is done in that case. | |
1803 | ||
1804 | The value of @code{auto-fill-function} is @code{do-auto-fill} when | |
1805 | Auto-Fill mode is enabled. That is a function whose sole purpose is to | |
1806 | implement the usual strategy for breaking a line. | |
1807 | ||
1808 | @quotation | |
1809 | In older Emacs versions, this variable was named @code{auto-fill-hook}, | |
1810 | but since it is not called with the standard convention for hooks, it | |
1811 | was renamed to @code{auto-fill-function} in version 19. | |
1812 | @end quotation | |
1813 | @end defvar | |
1814 | ||
1815 | @defvar normal-auto-fill-function | |
1816 | This variable specifies the function to use for | |
1817 | @code{auto-fill-function}, if and when Auto Fill is turned on. Major | |
1818 | modes can set buffer-local values for this variable to alter how Auto | |
1819 | Fill works. | |
1820 | @end defvar | |
1821 | ||
1822 | @defvar auto-fill-chars | |
1823 | A char table of characters which invoke @code{auto-fill-function} when | |
1824 | self-inserted---space and newline in most language environments. They | |
1825 | have an entry @code{t} in the table. | |
1826 | @end defvar | |
1827 | ||
1828 | @node Sorting | |
1829 | @section Sorting Text | |
1830 | @cindex sorting text | |
1831 | ||
1832 | The sorting functions described in this section all rearrange text in | |
1833 | a buffer. This is in contrast to the function @code{sort}, which | |
1834 | rearranges the order of the elements of a list (@pxref{Rearrangement}). | |
1835 | The values returned by these functions are not meaningful. | |
1836 | ||
1837 | @defun sort-subr reverse nextrecfun endrecfun &optional startkeyfun endkeyfun predicate | |
1838 | This function is the general text-sorting routine that subdivides a | |
1839 | buffer into records and then sorts them. Most of the commands in this | |
1840 | section use this function. | |
1841 | ||
1842 | To understand how @code{sort-subr} works, consider the whole accessible | |
1843 | portion of the buffer as being divided into disjoint pieces called | |
1844 | @dfn{sort records}. The records may or may not be contiguous, but they | |
1845 | must not overlap. A portion of each sort record (perhaps all of it) is | |
1846 | designated as the sort key. Sorting rearranges the records in order by | |
1847 | their sort keys. | |
1848 | ||
1849 | Usually, the records are rearranged in order of ascending sort key. | |
1850 | If the first argument to the @code{sort-subr} function, @var{reverse}, | |
1851 | is non-@code{nil}, the sort records are rearranged in order of | |
1852 | descending sort key. | |
1853 | ||
1854 | The next four arguments to @code{sort-subr} are functions that are | |
1855 | called to move point across a sort record. They are called many times | |
1856 | from within @code{sort-subr}. | |
1857 | ||
1858 | @enumerate | |
1859 | @item | |
1860 | @var{nextrecfun} is called with point at the end of a record. This | |
1861 | function moves point to the start of the next record. The first record | |
1862 | is assumed to start at the position of point when @code{sort-subr} is | |
1863 | called. Therefore, you should usually move point to the beginning of | |
1864 | the buffer before calling @code{sort-subr}. | |
1865 | ||
1866 | This function can indicate there are no more sort records by leaving | |
1867 | point at the end of the buffer. | |
1868 | ||
1869 | @item | |
1870 | @var{endrecfun} is called with point within a record. It moves point to | |
1871 | the end of the record. | |
1872 | ||
1873 | @item | |
1874 | @var{startkeyfun} is called to move point from the start of a record to | |
1875 | the start of the sort key. This argument is optional; if it is omitted, | |
1876 | the whole record is the sort key. If supplied, the function should | |
1877 | either return a non-@code{nil} value to be used as the sort key, or | |
1878 | return @code{nil} to indicate that the sort key is in the buffer | |
1879 | starting at point. In the latter case, @var{endkeyfun} is called to | |
1880 | find the end of the sort key. | |
1881 | ||
1882 | @item | |
1883 | @var{endkeyfun} is called to move point from the start of the sort key | |
1884 | to the end of the sort key. This argument is optional. If | |
1885 | @var{startkeyfun} returns @code{nil} and this argument is omitted (or | |
1886 | @code{nil}), then the sort key extends to the end of the record. There | |
1887 | is no need for @var{endkeyfun} if @var{startkeyfun} returns a | |
1888 | non-@code{nil} value. | |
1889 | @end enumerate | |
1890 | ||
1891 | The argument @var{predicate} is the function to use to compare keys. | |
1892 | If keys are numbers, it defaults to @code{<}; otherwise it defaults to | |
1893 | @code{string<}. | |
1894 | ||
1895 | As an example of @code{sort-subr}, here is the complete function | |
1896 | definition for @code{sort-lines}: | |
1897 | ||
1898 | @example | |
1899 | @group | |
1900 | ;; @r{Note that the first two lines of doc string} | |
1901 | ;; @r{are effectively one line when viewed by a user.} | |
1902 | (defun sort-lines (reverse beg end) | |
1903 | "Sort lines in region alphabetically;\ | |
1904 | argument means descending order. | |
1905 | Called from a program, there are three arguments: | |
1906 | @end group | |
1907 | @group | |
1908 | REVERSE (non-nil means reverse order),\ | |
1909 | BEG and END (region to sort). | |
1910 | The variable `sort-fold-case' determines\ | |
1911 | whether alphabetic case affects | |
1912 | the sort order." | |
1913 | @end group | |
1914 | @group | |
1915 | (interactive "P\nr") | |
1916 | (save-excursion | |
1917 | (save-restriction | |
1918 | (narrow-to-region beg end) | |
1919 | (goto-char (point-min)) | |
1920 | (let ((inhibit-field-text-motion t)) | |
1921 | (sort-subr reverse 'forward-line 'end-of-line))))) | |
1922 | @end group | |
1923 | @end example | |
1924 | ||
1925 | Here @code{forward-line} moves point to the start of the next record, | |
1926 | and @code{end-of-line} moves point to the end of record. We do not pass | |
1927 | the arguments @var{startkeyfun} and @var{endkeyfun}, because the entire | |
1928 | record is used as the sort key. | |
1929 | ||
1930 | The @code{sort-paragraphs} function is very much the same, except that | |
1931 | its @code{sort-subr} call looks like this: | |
1932 | ||
1933 | @example | |
1934 | @group | |
1935 | (sort-subr reverse | |
1936 | (function | |
1937 | (lambda () | |
1938 | (while (and (not (eobp)) | |
1939 | (looking-at paragraph-separate)) | |
1940 | (forward-line 1)))) | |
1941 | 'forward-paragraph) | |
1942 | @end group | |
1943 | @end example | |
1944 | ||
1945 | Markers pointing into any sort records are left with no useful | |
1946 | position after @code{sort-subr} returns. | |
1947 | @end defun | |
1948 | ||
1949 | @defopt sort-fold-case | |
1950 | If this variable is non-@code{nil}, @code{sort-subr} and the other | |
1951 | buffer sorting functions ignore case when comparing strings. | |
1952 | @end defopt | |
1953 | ||
1954 | @deffn Command sort-regexp-fields reverse record-regexp key-regexp start end | |
1955 | This command sorts the region between @var{start} and @var{end} | |
1956 | alphabetically as specified by @var{record-regexp} and @var{key-regexp}. | |
1957 | If @var{reverse} is a negative integer, then sorting is in reverse | |
1958 | order. | |
1959 | ||
1960 | Alphabetical sorting means that two sort keys are compared by | |
1961 | comparing the first characters of each, the second characters of each, | |
1962 | and so on. If a mismatch is found, it means that the sort keys are | |
1963 | unequal; the sort key whose character is less at the point of first | |
1964 | mismatch is the lesser sort key. The individual characters are compared | |
1965 | according to their numerical character codes in the Emacs character set. | |
1966 | ||
1967 | The value of the @var{record-regexp} argument specifies how to divide | |
1968 | the buffer into sort records. At the end of each record, a search is | |
1969 | done for this regular expression, and the text that matches it is taken | |
1970 | as the next record. For example, the regular expression @samp{^.+$}, | |
1971 | which matches lines with at least one character besides a newline, would | |
1972 | make each such line into a sort record. @xref{Regular Expressions}, for | |
1973 | a description of the syntax and meaning of regular expressions. | |
1974 | ||
1975 | The value of the @var{key-regexp} argument specifies what part of each | |
1976 | record is the sort key. The @var{key-regexp} could match the whole | |
1977 | record, or only a part. In the latter case, the rest of the record has | |
1978 | no effect on the sorted order of records, but it is carried along when | |
1979 | the record moves to its new position. | |
1980 | ||
1981 | The @var{key-regexp} argument can refer to the text matched by a | |
1982 | subexpression of @var{record-regexp}, or it can be a regular expression | |
1983 | on its own. | |
1984 | ||
1985 | If @var{key-regexp} is: | |
1986 | ||
1987 | @table @asis | |
1988 | @item @samp{\@var{digit}} | |
1989 | then the text matched by the @var{digit}th @samp{\(...\)} parenthesis | |
1990 | grouping in @var{record-regexp} is the sort key. | |
1991 | ||
1992 | @item @samp{\&} | |
1993 | then the whole record is the sort key. | |
1994 | ||
1995 | @item a regular expression | |
1996 | then @code{sort-regexp-fields} searches for a match for the regular | |
1997 | expression within the record. If such a match is found, it is the sort | |
1998 | key. If there is no match for @var{key-regexp} within a record then | |
1999 | that record is ignored, which means its position in the buffer is not | |
2000 | changed. (The other records may move around it.) | |
2001 | @end table | |
2002 | ||
2003 | For example, if you plan to sort all the lines in the region by the | |
2004 | first word on each line starting with the letter @samp{f}, you should | |
2005 | set @var{record-regexp} to @samp{^.*$} and set @var{key-regexp} to | |
2006 | @samp{\<f\w*\>}. The resulting expression looks like this: | |
2007 | ||
2008 | @example | |
2009 | @group | |
2010 | (sort-regexp-fields nil "^.*$" "\\<f\\w*\\>" | |
2011 | (region-beginning) | |
2012 | (region-end)) | |
2013 | @end group | |
2014 | @end example | |
2015 | ||
2016 | If you call @code{sort-regexp-fields} interactively, it prompts for | |
2017 | @var{record-regexp} and @var{key-regexp} in the minibuffer. | |
2018 | @end deffn | |
2019 | ||
2020 | @deffn Command sort-lines reverse start end | |
2021 | This command alphabetically sorts lines in the region between | |
2022 | @var{start} and @var{end}. If @var{reverse} is non-@code{nil}, the sort | |
2023 | is in reverse order. | |
2024 | @end deffn | |
2025 | ||
2026 | @deffn Command sort-paragraphs reverse start end | |
2027 | This command alphabetically sorts paragraphs in the region between | |
2028 | @var{start} and @var{end}. If @var{reverse} is non-@code{nil}, the sort | |
2029 | is in reverse order. | |
2030 | @end deffn | |
2031 | ||
2032 | @deffn Command sort-pages reverse start end | |
2033 | This command alphabetically sorts pages in the region between | |
2034 | @var{start} and @var{end}. If @var{reverse} is non-@code{nil}, the sort | |
2035 | is in reverse order. | |
2036 | @end deffn | |
2037 | ||
2038 | @deffn Command sort-fields field start end | |
2039 | This command sorts lines in the region between @var{start} and | |
2040 | @var{end}, comparing them alphabetically by the @var{field}th field | |
2041 | of each line. Fields are separated by whitespace and numbered starting | |
2042 | from 1. If @var{field} is negative, sorting is by the | |
2043 | @w{@minus{}@var{field}th} field from the end of the line. This command | |
2044 | is useful for sorting tables. | |
2045 | @end deffn | |
2046 | ||
2047 | @deffn Command sort-numeric-fields field start end | |
2048 | This command sorts lines in the region between @var{start} and | |
2049 | @var{end}, comparing them numerically by the @var{field}th field of | |
2050 | each line. Fields are separated by whitespace and numbered starting | |
2051 | from 1. The specified field must contain a number in each line of the | |
2052 | region. Numbers starting with 0 are treated as octal, and numbers | |
2053 | starting with @samp{0x} are treated as hexadecimal. | |
2054 | ||
2055 | If @var{field} is negative, sorting is by the | |
2056 | @w{@minus{}@var{field}th} field from the end of the line. This | |
2057 | command is useful for sorting tables. | |
2058 | @end deffn | |
2059 | ||
2060 | @defopt sort-numeric-base | |
2061 | This variable specifies the default radix for | |
2062 | @code{sort-numeric-fields} to parse numbers. | |
2063 | @end defopt | |
2064 | ||
2065 | @deffn Command sort-columns reverse &optional beg end | |
2066 | This command sorts the lines in the region between @var{beg} and | |
2067 | @var{end}, comparing them alphabetically by a certain range of | |
2068 | columns. The column positions of @var{beg} and @var{end} bound the | |
2069 | range of columns to sort on. | |
2070 | ||
2071 | If @var{reverse} is non-@code{nil}, the sort is in reverse order. | |
2072 | ||
2073 | One unusual thing about this command is that the entire line | |
2074 | containing position @var{beg}, and the entire line containing position | |
2075 | @var{end}, are included in the region sorted. | |
2076 | ||
2077 | Note that @code{sort-columns} rejects text that contains tabs, because | |
2078 | tabs could be split across the specified columns. Use @kbd{M-x | |
2079 | untabify} to convert tabs to spaces before sorting. | |
2080 | ||
2081 | When possible, this command actually works by calling the @code{sort} | |
2082 | utility program. | |
2083 | @end deffn | |
2084 | ||
2085 | @node Columns | |
2086 | @comment node-name, next, previous, up | |
2087 | @section Counting Columns | |
2088 | @cindex columns | |
2089 | @cindex counting columns | |
2090 | @cindex horizontal position | |
2091 | ||
2092 | The column functions convert between a character position (counting | |
2093 | characters from the beginning of the buffer) and a column position | |
2094 | (counting screen characters from the beginning of a line). | |
2095 | ||
2096 | These functions count each character according to the number of | |
2097 | columns it occupies on the screen. This means control characters count | |
2098 | as occupying 2 or 4 columns, depending upon the value of | |
2099 | @code{ctl-arrow}, and tabs count as occupying a number of columns that | |
2100 | depends on the value of @code{tab-width} and on the column where the tab | |
2101 | begins. @xref{Usual Display}. | |
2102 | ||
2103 | Column number computations ignore the width of the window and the | |
2104 | amount of horizontal scrolling. Consequently, a column value can be | |
2105 | arbitrarily high. The first (or leftmost) column is numbered 0. They | |
2106 | also ignore overlays and text properties, aside from invisibility. | |
2107 | ||
2108 | @defun current-column | |
2109 | This function returns the horizontal position of point, measured in | |
2110 | columns, counting from 0 at the left margin. The column position is the | |
2111 | sum of the widths of all the displayed representations of the characters | |
2112 | between the start of the current line and point. | |
2113 | ||
2114 | For an example of using @code{current-column}, see the description of | |
2115 | @code{count-lines} in @ref{Text Lines}. | |
2116 | @end defun | |
2117 | ||
106e6894 | 2118 | @deffn Command move-to-column column &optional force |
b8d4c8d0 GM |
2119 | This function moves point to @var{column} in the current line. The |
2120 | calculation of @var{column} takes into account the widths of the | |
2121 | displayed representations of the characters between the start of the | |
2122 | line and point. | |
2123 | ||
106e6894 CY |
2124 | When called interactively, @var{column} is the value of prefix numeric |
2125 | argument. If @var{column} is not an integer, an error is signaled. | |
2126 | ||
2127 | If column @var{column} is beyond the end of the line, point moves to | |
2128 | the end of the line. If @var{column} is negative, point moves to the | |
b8d4c8d0 GM |
2129 | beginning of the line. |
2130 | ||
2131 | If it is impossible to move to column @var{column} because that is in | |
2132 | the middle of a multicolumn character such as a tab, point moves to the | |
2133 | end of that character. However, if @var{force} is non-@code{nil}, and | |
2134 | @var{column} is in the middle of a tab, then @code{move-to-column} | |
2135 | converts the tab into spaces so that it can move precisely to column | |
2136 | @var{column}. Other multicolumn characters can cause anomalies despite | |
2137 | @var{force}, since there is no way to split them. | |
2138 | ||
2139 | The argument @var{force} also has an effect if the line isn't long | |
2140 | enough to reach column @var{column}; if it is @code{t}, that means to | |
2141 | add whitespace at the end of the line to reach that column. | |
2142 | ||
b8d4c8d0 | 2143 | The return value is the column number actually moved to. |
106e6894 | 2144 | @end deffn |
b8d4c8d0 GM |
2145 | |
2146 | @node Indentation | |
2147 | @section Indentation | |
2148 | @cindex indentation | |
2149 | ||
2150 | The indentation functions are used to examine, move to, and change | |
2151 | whitespace that is at the beginning of a line. Some of the functions | |
2152 | can also change whitespace elsewhere on a line. Columns and indentation | |
2153 | count from zero at the left margin. | |
2154 | ||
2155 | @menu | |
2156 | * Primitive Indent:: Functions used to count and insert indentation. | |
2157 | * Mode-Specific Indent:: Customize indentation for different modes. | |
2158 | * Region Indent:: Indent all the lines in a region. | |
2159 | * Relative Indent:: Indent the current line based on previous lines. | |
2160 | * Indent Tabs:: Adjustable, typewriter-like tab stops. | |
2161 | * Motion by Indent:: Move to first non-blank character. | |
2162 | @end menu | |
2163 | ||
2164 | @node Primitive Indent | |
2165 | @subsection Indentation Primitives | |
2166 | ||
2167 | This section describes the primitive functions used to count and | |
2168 | insert indentation. The functions in the following sections use these | |
2169 | primitives. @xref{Width}, for related functions. | |
2170 | ||
2171 | @defun current-indentation | |
2172 | @comment !!Type Primitive Function | |
2173 | @comment !!SourceFile indent.c | |
2174 | This function returns the indentation of the current line, which is | |
2175 | the horizontal position of the first nonblank character. If the | |
2176 | contents are entirely blank, then this is the horizontal position of the | |
2177 | end of the line. | |
2178 | @end defun | |
2179 | ||
2180 | @deffn Command indent-to column &optional minimum | |
2181 | @comment !!Type Primitive Function | |
2182 | @comment !!SourceFile indent.c | |
2183 | This function indents from point with tabs and spaces until @var{column} | |
2184 | is reached. If @var{minimum} is specified and non-@code{nil}, then at | |
2185 | least that many spaces are inserted even if this requires going beyond | |
2186 | @var{column}. Otherwise the function does nothing if point is already | |
2187 | beyond @var{column}. The value is the column at which the inserted | |
2188 | indentation ends. | |
2189 | ||
2190 | The inserted whitespace characters inherit text properties from the | |
2191 | surrounding text (usually, from the preceding text only). @xref{Sticky | |
2192 | Properties}. | |
2193 | @end deffn | |
2194 | ||
2195 | @defopt indent-tabs-mode | |
2196 | @comment !!SourceFile indent.c | |
2197 | If this variable is non-@code{nil}, indentation functions can insert | |
2198 | tabs as well as spaces. Otherwise, they insert only spaces. Setting | |
2199 | this variable automatically makes it buffer-local in the current buffer. | |
2200 | @end defopt | |
2201 | ||
2202 | @node Mode-Specific Indent | |
2203 | @subsection Indentation Controlled by Major Mode | |
2204 | ||
2205 | An important function of each major mode is to customize the @key{TAB} | |
2206 | key to indent properly for the language being edited. This section | |
2207 | describes the mechanism of the @key{TAB} key and how to control it. | |
2208 | The functions in this section return unpredictable values. | |
2209 | ||
2210 | @defvar indent-line-function | |
2211 | This variable's value is the function to be used by @key{TAB} (and | |
2212 | various commands) to indent the current line. The command | |
769741e3 | 2213 | @code{indent-according-to-mode} does little more than call this function. |
b8d4c8d0 GM |
2214 | |
2215 | In Lisp mode, the value is the symbol @code{lisp-indent-line}; in C | |
2216 | mode, @code{c-indent-line}; in Fortran mode, @code{fortran-indent-line}. | |
5dcb4c4e | 2217 | The default value is @code{indent-relative}. @xref{Auto-Indentation}. |
b8d4c8d0 GM |
2218 | @end defvar |
2219 | ||
2220 | @deffn Command indent-according-to-mode | |
2221 | This command calls the function in @code{indent-line-function} to | |
2222 | indent the current line in a way appropriate for the current major mode. | |
2223 | @end deffn | |
2224 | ||
106e6894 CY |
2225 | @deffn Command indent-for-tab-command &optional rigid |
2226 | This command calls the function in @code{indent-line-function} to | |
2227 | indent the current line; however, if that function is | |
2228 | @code{indent-to-left-margin}, @code{insert-tab} is called instead. | |
2229 | (That is a trivial command that inserts a tab character.) If | |
2230 | @var{rigid} is non-@code{nil}, this function also rigidly indents the | |
2231 | entire balanced expression that starts at the beginning of the current | |
2232 | line, to reflect change in indentation of the current line. | |
b8d4c8d0 GM |
2233 | @end deffn |
2234 | ||
2235 | @deffn Command newline-and-indent | |
b8d4c8d0 GM |
2236 | This function inserts a newline, then indents the new line (the one |
2237 | following the newline just inserted) according to the major mode. | |
2238 | ||
2239 | It does indentation by calling the current @code{indent-line-function}. | |
2240 | In programming language modes, this is the same thing @key{TAB} does, | |
2241 | but in some text modes, where @key{TAB} inserts a tab, | |
2242 | @code{newline-and-indent} indents to the column specified by | |
2243 | @code{left-margin}. | |
2244 | @end deffn | |
2245 | ||
2246 | @deffn Command reindent-then-newline-and-indent | |
2247 | @comment !!SourceFile simple.el | |
2248 | This command reindents the current line, inserts a newline at point, | |
2249 | and then indents the new line (the one following the newline just | |
2250 | inserted). | |
2251 | ||
2252 | This command does indentation on both lines according to the current | |
2253 | major mode, by calling the current value of @code{indent-line-function}. | |
2254 | In programming language modes, this is the same thing @key{TAB} does, | |
2255 | but in some text modes, where @key{TAB} inserts a tab, | |
2256 | @code{reindent-then-newline-and-indent} indents to the column specified | |
2257 | by @code{left-margin}. | |
2258 | @end deffn | |
2259 | ||
2260 | @node Region Indent | |
2261 | @subsection Indenting an Entire Region | |
2262 | ||
2263 | This section describes commands that indent all the lines in the | |
2264 | region. They return unpredictable values. | |
2265 | ||
106e6894 | 2266 | @deffn Command indent-region start end &optional to-column |
b8d4c8d0 GM |
2267 | This command indents each nonblank line starting between @var{start} |
2268 | (inclusive) and @var{end} (exclusive). If @var{to-column} is | |
2269 | @code{nil}, @code{indent-region} indents each nonblank line by calling | |
2270 | the current mode's indentation function, the value of | |
2271 | @code{indent-line-function}. | |
2272 | ||
2273 | If @var{to-column} is non-@code{nil}, it should be an integer | |
2274 | specifying the number of columns of indentation; then this function | |
2275 | gives each line exactly that much indentation, by either adding or | |
2276 | deleting whitespace. | |
2277 | ||
2278 | If there is a fill prefix, @code{indent-region} indents each line | |
2279 | by making it start with the fill prefix. | |
2280 | @end deffn | |
2281 | ||
2282 | @defvar indent-region-function | |
2283 | The value of this variable is a function that can be used by | |
2284 | @code{indent-region} as a short cut. It should take two arguments, the | |
2285 | start and end of the region. You should design the function so | |
2286 | that it will produce the same results as indenting the lines of the | |
2287 | region one by one, but presumably faster. | |
2288 | ||
2289 | If the value is @code{nil}, there is no short cut, and | |
2290 | @code{indent-region} actually works line by line. | |
2291 | ||
2292 | A short-cut function is useful in modes such as C mode and Lisp mode, | |
2293 | where the @code{indent-line-function} must scan from the beginning of | |
2294 | the function definition: applying it to each line would be quadratic in | |
2295 | time. The short cut can update the scan information as it moves through | |
2296 | the lines indenting them; this takes linear time. In a mode where | |
2297 | indenting a line individually is fast, there is no need for a short cut. | |
2298 | ||
2299 | @code{indent-region} with a non-@code{nil} argument @var{to-column} has | |
2300 | a different meaning and does not use this variable. | |
2301 | @end defvar | |
2302 | ||
2303 | @deffn Command indent-rigidly start end count | |
b8d4c8d0 GM |
2304 | This command indents all lines starting between @var{start} |
2305 | (inclusive) and @var{end} (exclusive) sideways by @var{count} columns. | |
2306 | This ``preserves the shape'' of the affected region, moving it as a | |
2307 | rigid unit. Consequently, this command is useful not only for indenting | |
2308 | regions of unindented text, but also for indenting regions of formatted | |
2309 | code. | |
2310 | ||
2311 | For example, if @var{count} is 3, this command adds 3 columns of | |
2312 | indentation to each of the lines beginning in the region specified. | |
2313 | ||
2314 | In Mail mode, @kbd{C-c C-y} (@code{mail-yank-original}) uses | |
2315 | @code{indent-rigidly} to indent the text copied from the message being | |
2316 | replied to. | |
2317 | @end deffn | |
2318 | ||
106e6894 | 2319 | @deffn Command indent-code-rigidly start end columns &optional nochange-regexp |
b8d4c8d0 GM |
2320 | This is like @code{indent-rigidly}, except that it doesn't alter lines |
2321 | that start within strings or comments. | |
2322 | ||
2323 | In addition, it doesn't alter a line if @var{nochange-regexp} matches at | |
2324 | the beginning of the line (if @var{nochange-regexp} is non-@code{nil}). | |
106e6894 | 2325 | @end deffn |
b8d4c8d0 GM |
2326 | |
2327 | @node Relative Indent | |
2328 | @subsection Indentation Relative to Previous Lines | |
2329 | ||
2330 | This section describes two commands that indent the current line | |
2331 | based on the contents of previous lines. | |
2332 | ||
2333 | @deffn Command indent-relative &optional unindented-ok | |
2334 | This command inserts whitespace at point, extending to the same | |
2335 | column as the next @dfn{indent point} of the previous nonblank line. An | |
2336 | indent point is a non-whitespace character following whitespace. The | |
2337 | next indent point is the first one at a column greater than the current | |
2338 | column of point. For example, if point is underneath and to the left of | |
2339 | the first non-blank character of a line of text, it moves to that column | |
2340 | by inserting whitespace. | |
2341 | ||
2342 | If the previous nonblank line has no next indent point (i.e., none at a | |
2343 | great enough column position), @code{indent-relative} either does | |
2344 | nothing (if @var{unindented-ok} is non-@code{nil}) or calls | |
2345 | @code{tab-to-tab-stop}. Thus, if point is underneath and to the right | |
2346 | of the last column of a short line of text, this command ordinarily | |
2347 | moves point to the next tab stop by inserting whitespace. | |
2348 | ||
2349 | The return value of @code{indent-relative} is unpredictable. | |
2350 | ||
2351 | In the following example, point is at the beginning of the second | |
2352 | line: | |
2353 | ||
2354 | @example | |
2355 | @group | |
2356 | This line is indented twelve spaces. | |
2357 | @point{}The quick brown fox jumped. | |
2358 | @end group | |
2359 | @end example | |
2360 | ||
2361 | @noindent | |
2362 | Evaluation of the expression @code{(indent-relative nil)} produces the | |
2363 | following: | |
2364 | ||
2365 | @example | |
2366 | @group | |
2367 | This line is indented twelve spaces. | |
2368 | @point{}The quick brown fox jumped. | |
2369 | @end group | |
2370 | @end example | |
2371 | ||
2372 | In this next example, point is between the @samp{m} and @samp{p} of | |
2373 | @samp{jumped}: | |
2374 | ||
2375 | @example | |
2376 | @group | |
2377 | This line is indented twelve spaces. | |
2378 | The quick brown fox jum@point{}ped. | |
2379 | @end group | |
2380 | @end example | |
2381 | ||
2382 | @noindent | |
2383 | Evaluation of the expression @code{(indent-relative nil)} produces the | |
2384 | following: | |
2385 | ||
2386 | @example | |
2387 | @group | |
2388 | This line is indented twelve spaces. | |
2389 | The quick brown fox jum @point{}ped. | |
2390 | @end group | |
2391 | @end example | |
2392 | @end deffn | |
2393 | ||
2394 | @deffn Command indent-relative-maybe | |
2395 | @comment !!SourceFile indent.el | |
2396 | This command indents the current line like the previous nonblank line, | |
2397 | by calling @code{indent-relative} with @code{t} as the | |
2398 | @var{unindented-ok} argument. The return value is unpredictable. | |
2399 | ||
2400 | If the previous nonblank line has no indent points beyond the current | |
2401 | column, this command does nothing. | |
2402 | @end deffn | |
2403 | ||
2404 | @node Indent Tabs | |
2405 | @comment node-name, next, previous, up | |
2406 | @subsection Adjustable ``Tab Stops'' | |
2407 | @cindex tabs stops for indentation | |
2408 | ||
2409 | This section explains the mechanism for user-specified ``tab stops'' | |
2410 | and the mechanisms that use and set them. The name ``tab stops'' is | |
2411 | used because the feature is similar to that of the tab stops on a | |
2412 | typewriter. The feature works by inserting an appropriate number of | |
2413 | spaces and tab characters to reach the next tab stop column; it does not | |
2414 | affect the display of tab characters in the buffer (@pxref{Usual | |
2415 | Display}). Note that the @key{TAB} character as input uses this tab | |
2416 | stop feature only in a few major modes, such as Text mode. | |
2417 | @xref{Tab Stops,,, emacs, The GNU Emacs Manual}. | |
2418 | ||
2419 | @deffn Command tab-to-tab-stop | |
2420 | This command inserts spaces or tabs before point, up to the next tab | |
2421 | stop column defined by @code{tab-stop-list}. It searches the list for | |
2422 | an element greater than the current column number, and uses that element | |
2423 | as the column to indent to. It does nothing if no such element is | |
2424 | found. | |
2425 | @end deffn | |
2426 | ||
2427 | @defopt tab-stop-list | |
2428 | This variable is the list of tab stop columns used by | |
2429 | @code{tab-to-tab-stops}. The elements should be integers in increasing | |
2430 | order. The tab stop columns need not be evenly spaced. | |
2431 | ||
2432 | Use @kbd{M-x edit-tab-stops} to edit the location of tab stops | |
2433 | interactively. | |
2434 | @end defopt | |
2435 | ||
2436 | @node Motion by Indent | |
2437 | @subsection Indentation-Based Motion Commands | |
2438 | ||
2439 | These commands, primarily for interactive use, act based on the | |
2440 | indentation in the text. | |
2441 | ||
2442 | @deffn Command back-to-indentation | |
2443 | @comment !!SourceFile simple.el | |
2444 | This command moves point to the first non-whitespace character in the | |
2445 | current line (which is the line in which point is located). It returns | |
2446 | @code{nil}. | |
2447 | @end deffn | |
2448 | ||
2449 | @deffn Command backward-to-indentation &optional arg | |
2450 | @comment !!SourceFile simple.el | |
2451 | This command moves point backward @var{arg} lines and then to the | |
2452 | first nonblank character on that line. It returns @code{nil}. | |
2453 | If @var{arg} is omitted or @code{nil}, it defaults to 1. | |
2454 | @end deffn | |
2455 | ||
2456 | @deffn Command forward-to-indentation &optional arg | |
2457 | @comment !!SourceFile simple.el | |
2458 | This command moves point forward @var{arg} lines and then to the first | |
2459 | nonblank character on that line. It returns @code{nil}. | |
2460 | If @var{arg} is omitted or @code{nil}, it defaults to 1. | |
2461 | @end deffn | |
2462 | ||
2463 | @node Case Changes | |
2464 | @comment node-name, next, previous, up | |
2465 | @section Case Changes | |
2466 | @cindex case conversion in buffers | |
2467 | ||
2468 | The case change commands described here work on text in the current | |
2469 | buffer. @xref{Case Conversion}, for case conversion functions that work | |
2470 | on strings and characters. @xref{Case Tables}, for how to customize | |
2471 | which characters are upper or lower case and how to convert them. | |
2472 | ||
2473 | @deffn Command capitalize-region start end | |
2474 | This function capitalizes all words in the region defined by | |
2475 | @var{start} and @var{end}. To capitalize means to convert each word's | |
2476 | first character to upper case and convert the rest of each word to lower | |
2477 | case. The function returns @code{nil}. | |
2478 | ||
2479 | If one end of the region is in the middle of a word, the part of the | |
2480 | word within the region is treated as an entire word. | |
2481 | ||
2482 | When @code{capitalize-region} is called interactively, @var{start} and | |
2483 | @var{end} are point and the mark, with the smallest first. | |
2484 | ||
2485 | @example | |
2486 | @group | |
2487 | ---------- Buffer: foo ---------- | |
2488 | This is the contents of the 5th foo. | |
2489 | ---------- Buffer: foo ---------- | |
2490 | @end group | |
2491 | ||
2492 | @group | |
2493 | (capitalize-region 1 44) | |
2494 | @result{} nil | |
2495 | ||
2496 | ---------- Buffer: foo ---------- | |
2497 | This Is The Contents Of The 5th Foo. | |
2498 | ---------- Buffer: foo ---------- | |
2499 | @end group | |
2500 | @end example | |
2501 | @end deffn | |
2502 | ||
2503 | @deffn Command downcase-region start end | |
2504 | This function converts all of the letters in the region defined by | |
2505 | @var{start} and @var{end} to lower case. The function returns | |
2506 | @code{nil}. | |
2507 | ||
2508 | When @code{downcase-region} is called interactively, @var{start} and | |
2509 | @var{end} are point and the mark, with the smallest first. | |
2510 | @end deffn | |
2511 | ||
2512 | @deffn Command upcase-region start end | |
2513 | This function converts all of the letters in the region defined by | |
2514 | @var{start} and @var{end} to upper case. The function returns | |
2515 | @code{nil}. | |
2516 | ||
2517 | When @code{upcase-region} is called interactively, @var{start} and | |
2518 | @var{end} are point and the mark, with the smallest first. | |
2519 | @end deffn | |
2520 | ||
2521 | @deffn Command capitalize-word count | |
2522 | This function capitalizes @var{count} words after point, moving point | |
2523 | over as it does. To capitalize means to convert each word's first | |
2524 | character to upper case and convert the rest of each word to lower case. | |
2525 | If @var{count} is negative, the function capitalizes the | |
2526 | @minus{}@var{count} previous words but does not move point. The value | |
2527 | is @code{nil}. | |
2528 | ||
2529 | If point is in the middle of a word, the part of the word before point | |
2530 | is ignored when moving forward. The rest is treated as an entire word. | |
2531 | ||
2532 | When @code{capitalize-word} is called interactively, @var{count} is | |
2533 | set to the numeric prefix argument. | |
2534 | @end deffn | |
2535 | ||
2536 | @deffn Command downcase-word count | |
2537 | This function converts the @var{count} words after point to all lower | |
2538 | case, moving point over as it does. If @var{count} is negative, it | |
2539 | converts the @minus{}@var{count} previous words but does not move point. | |
2540 | The value is @code{nil}. | |
2541 | ||
2542 | When @code{downcase-word} is called interactively, @var{count} is set | |
2543 | to the numeric prefix argument. | |
2544 | @end deffn | |
2545 | ||
2546 | @deffn Command upcase-word count | |
2547 | This function converts the @var{count} words after point to all upper | |
2548 | case, moving point over as it does. If @var{count} is negative, it | |
2549 | converts the @minus{}@var{count} previous words but does not move point. | |
2550 | The value is @code{nil}. | |
2551 | ||
2552 | When @code{upcase-word} is called interactively, @var{count} is set to | |
2553 | the numeric prefix argument. | |
2554 | @end deffn | |
2555 | ||
2556 | @node Text Properties | |
2557 | @section Text Properties | |
2558 | @cindex text properties | |
2559 | @cindex attributes of text | |
2560 | @cindex properties of text | |
2561 | ||
2562 | Each character position in a buffer or a string can have a @dfn{text | |
2563 | property list}, much like the property list of a symbol (@pxref{Property | |
2564 | Lists}). The properties belong to a particular character at a | |
2565 | particular place, such as, the letter @samp{T} at the beginning of this | |
2566 | sentence or the first @samp{o} in @samp{foo}---if the same character | |
2567 | occurs in two different places, the two occurrences in general have | |
2568 | different properties. | |
2569 | ||
2570 | Each property has a name and a value. Both of these can be any Lisp | |
2571 | object, but the name is normally a symbol. Typically each property | |
2572 | name symbol is used for a particular purpose; for instance, the text | |
2573 | property @code{face} specifies the faces for displaying the character | |
2574 | (@pxref{Special Properties}). The usual way to access the property | |
2575 | list is to specify a name and ask what value corresponds to it. | |
2576 | ||
2577 | If a character has a @code{category} property, we call it the | |
2578 | @dfn{property category} of the character. It should be a symbol. The | |
2579 | properties of the symbol serve as defaults for the properties of the | |
2580 | character. | |
2581 | ||
2582 | Copying text between strings and buffers preserves the properties | |
2583 | along with the characters; this includes such diverse functions as | |
2584 | @code{substring}, @code{insert}, and @code{buffer-substring}. | |
2585 | ||
2586 | @menu | |
2587 | * Examining Properties:: Looking at the properties of one character. | |
d24880de GM |
2588 | * Changing Properties:: Setting the properties of a range of text. |
2589 | * Property Search:: Searching for where a property changes value. | |
2590 | * Special Properties:: Particular properties with special meanings. | |
b8d4c8d0 GM |
2591 | * Format Properties:: Properties for representing formatting of text. |
2592 | * Sticky Properties:: How inserted text gets properties from | |
2593 | neighboring text. | |
2594 | * Lazy Properties:: Computing text properties in a lazy fashion | |
2595 | only when text is examined. | |
2596 | * Clickable Text:: Using text properties to make regions of text | |
2597 | do something when you click on them. | |
b8d4c8d0 GM |
2598 | * Fields:: The @code{field} property defines |
2599 | fields within the buffer. | |
d24880de GM |
2600 | * Not Intervals:: Why text properties do not use |
2601 | Lisp-visible text intervals. | |
b8d4c8d0 GM |
2602 | @end menu |
2603 | ||
2604 | @node Examining Properties | |
2605 | @subsection Examining Text Properties | |
2606 | ||
2607 | The simplest way to examine text properties is to ask for the value of | |
2608 | a particular property of a particular character. For that, use | |
2609 | @code{get-text-property}. Use @code{text-properties-at} to get the | |
2610 | entire property list of a character. @xref{Property Search}, for | |
2611 | functions to examine the properties of a number of characters at once. | |
2612 | ||
2613 | These functions handle both strings and buffers. Keep in mind that | |
2614 | positions in a string start from 0, whereas positions in a buffer start | |
2615 | from 1. | |
2616 | ||
2617 | @defun get-text-property pos prop &optional object | |
2618 | This function returns the value of the @var{prop} property of the | |
2619 | character after position @var{pos} in @var{object} (a buffer or | |
2620 | string). The argument @var{object} is optional and defaults to the | |
2621 | current buffer. | |
2622 | ||
2623 | If there is no @var{prop} property strictly speaking, but the character | |
2624 | has a property category that is a symbol, then @code{get-text-property} returns | |
2625 | the @var{prop} property of that symbol. | |
2626 | @end defun | |
2627 | ||
2628 | @defun get-char-property position prop &optional object | |
2629 | This function is like @code{get-text-property}, except that it checks | |
2630 | overlays first and then text properties. @xref{Overlays}. | |
2631 | ||
af23e1e8 RS |
2632 | The argument @var{object} may be a string, a buffer, or a window. If |
2633 | it is a window, then the buffer displayed in that window is used for | |
2634 | text properties and overlays, but only the overlays active for that | |
2635 | window are considered. If @var{object} is a buffer, then overlays in | |
2636 | that buffer are considered first, in order of decreasing priority, | |
2637 | followed by the text properties. If @var{object} is a string, only | |
2638 | text properties are considered, since strings never have overlays. | |
b8d4c8d0 GM |
2639 | @end defun |
2640 | ||
2641 | @defun get-char-property-and-overlay position prop &optional object | |
2642 | This is like @code{get-char-property}, but gives extra information | |
2643 | about the overlay that the property value comes from. | |
2644 | ||
2645 | Its value is a cons cell whose @sc{car} is the property value, the | |
2646 | same value @code{get-char-property} would return with the same | |
2647 | arguments. Its @sc{cdr} is the overlay in which the property was | |
2648 | found, or @code{nil}, if it was found as a text property or not found | |
2649 | at all. | |
2650 | ||
2651 | If @var{position} is at the end of @var{object}, both the @sc{car} and | |
2652 | the @sc{cdr} of the value are @code{nil}. | |
2653 | @end defun | |
2654 | ||
2655 | @defvar char-property-alias-alist | |
2656 | This variable holds an alist which maps property names to a list of | |
2657 | alternative property names. If a character does not specify a direct | |
2658 | value for a property, the alternative property names are consulted in | |
2659 | order; the first non-@code{nil} value is used. This variable takes | |
2660 | precedence over @code{default-text-properties}, and @code{category} | |
2661 | properties take precedence over this variable. | |
2662 | @end defvar | |
2663 | ||
2664 | @defun text-properties-at position &optional object | |
2665 | This function returns the entire property list of the character at | |
2666 | @var{position} in the string or buffer @var{object}. If @var{object} is | |
2667 | @code{nil}, it defaults to the current buffer. | |
2668 | @end defun | |
2669 | ||
2670 | @defvar default-text-properties | |
2671 | This variable holds a property list giving default values for text | |
2672 | properties. Whenever a character does not specify a value for a | |
2673 | property, neither directly, through a category symbol, or through | |
2674 | @code{char-property-alias-alist}, the value stored in this list is | |
2675 | used instead. Here is an example: | |
2676 | ||
2677 | @example | |
2678 | (setq default-text-properties '(foo 69) | |
2679 | char-property-alias-alist nil) | |
2680 | ;; @r{Make sure character 1 has no properties of its own.} | |
2681 | (set-text-properties 1 2 nil) | |
2682 | ;; @r{What we get, when we ask, is the default value.} | |
2683 | (get-text-property 1 'foo) | |
2684 | @result{} 69 | |
2685 | @end example | |
2686 | @end defvar | |
2687 | ||
2688 | @node Changing Properties | |
2689 | @subsection Changing Text Properties | |
2690 | ||
2691 | The primitives for changing properties apply to a specified range of | |
2692 | text in a buffer or string. The function @code{set-text-properties} | |
2693 | (see end of section) sets the entire property list of the text in that | |
2694 | range; more often, it is useful to add, change, or delete just certain | |
2695 | properties specified by name. | |
2696 | ||
2697 | Since text properties are considered part of the contents of the | |
2698 | buffer (or string), and can affect how a buffer looks on the screen, | |
2699 | any change in buffer text properties marks the buffer as modified. | |
2700 | Buffer text property changes are undoable also (@pxref{Undo}). | |
2701 | Positions in a string start from 0, whereas positions in a buffer | |
2702 | start from 1. | |
2703 | ||
2704 | @defun put-text-property start end prop value &optional object | |
2705 | This function sets the @var{prop} property to @var{value} for the text | |
2706 | between @var{start} and @var{end} in the string or buffer @var{object}. | |
2707 | If @var{object} is @code{nil}, it defaults to the current buffer. | |
2708 | @end defun | |
2709 | ||
2710 | @defun add-text-properties start end props &optional object | |
2711 | This function adds or overrides text properties for the text between | |
2712 | @var{start} and @var{end} in the string or buffer @var{object}. If | |
2713 | @var{object} is @code{nil}, it defaults to the current buffer. | |
2714 | ||
2715 | The argument @var{props} specifies which properties to add. It should | |
2716 | have the form of a property list (@pxref{Property Lists}): a list whose | |
2717 | elements include the property names followed alternately by the | |
2718 | corresponding values. | |
2719 | ||
2720 | The return value is @code{t} if the function actually changed some | |
2721 | property's value; @code{nil} otherwise (if @var{props} is @code{nil} or | |
2722 | its values agree with those in the text). | |
2723 | ||
2724 | For example, here is how to set the @code{comment} and @code{face} | |
2725 | properties of a range of text: | |
2726 | ||
2727 | @example | |
2728 | (add-text-properties @var{start} @var{end} | |
2729 | '(comment t face highlight)) | |
2730 | @end example | |
2731 | @end defun | |
2732 | ||
2733 | @defun remove-text-properties start end props &optional object | |
2734 | This function deletes specified text properties from the text between | |
2735 | @var{start} and @var{end} in the string or buffer @var{object}. If | |
2736 | @var{object} is @code{nil}, it defaults to the current buffer. | |
2737 | ||
2738 | The argument @var{props} specifies which properties to delete. It | |
2739 | should have the form of a property list (@pxref{Property Lists}): a list | |
2740 | whose elements are property names alternating with corresponding values. | |
2741 | But only the names matter---the values that accompany them are ignored. | |
2742 | For example, here's how to remove the @code{face} property. | |
2743 | ||
2744 | @example | |
2745 | (remove-text-properties @var{start} @var{end} '(face nil)) | |
2746 | @end example | |
2747 | ||
2748 | The return value is @code{t} if the function actually changed some | |
2749 | property's value; @code{nil} otherwise (if @var{props} is @code{nil} or | |
2750 | if no character in the specified text had any of those properties). | |
2751 | ||
2752 | To remove all text properties from certain text, use | |
2753 | @code{set-text-properties} and specify @code{nil} for the new property | |
2754 | list. | |
2755 | @end defun | |
2756 | ||
2757 | @defun remove-list-of-text-properties start end list-of-properties &optional object | |
2758 | Like @code{remove-text-properties} except that | |
2759 | @var{list-of-properties} is a list of property names only, not an | |
2760 | alternating list of property names and values. | |
2761 | @end defun | |
2762 | ||
2763 | @defun set-text-properties start end props &optional object | |
2764 | This function completely replaces the text property list for the text | |
2765 | between @var{start} and @var{end} in the string or buffer @var{object}. | |
2766 | If @var{object} is @code{nil}, it defaults to the current buffer. | |
2767 | ||
2768 | The argument @var{props} is the new property list. It should be a list | |
2769 | whose elements are property names alternating with corresponding values. | |
2770 | ||
2771 | After @code{set-text-properties} returns, all the characters in the | |
2772 | specified range have identical properties. | |
2773 | ||
2774 | If @var{props} is @code{nil}, the effect is to get rid of all properties | |
2775 | from the specified range of text. Here's an example: | |
2776 | ||
2777 | @example | |
2778 | (set-text-properties @var{start} @var{end} nil) | |
2779 | @end example | |
2780 | ||
2781 | Do not rely on the return value of this function. | |
2782 | @end defun | |
2783 | ||
2784 | The easiest way to make a string with text properties | |
2785 | is with @code{propertize}: | |
2786 | ||
2787 | @defun propertize string &rest properties | |
2788 | This function returns a copy of @var{string} which has the text | |
2789 | properties @var{properties}. These properties apply to all the | |
2790 | characters in the string that is returned. Here is an example that | |
2791 | constructs a string with a @code{face} property and a @code{mouse-face} | |
2792 | property: | |
2793 | ||
2794 | @smallexample | |
2795 | (propertize "foo" 'face 'italic | |
2796 | 'mouse-face 'bold-italic) | |
2797 | @result{} #("foo" 0 3 (mouse-face bold-italic face italic)) | |
2798 | @end smallexample | |
2799 | ||
2800 | To put different properties on various parts of a string, you can | |
2801 | construct each part with @code{propertize} and then combine them with | |
2802 | @code{concat}: | |
2803 | ||
2804 | @smallexample | |
2805 | (concat | |
2806 | (propertize "foo" 'face 'italic | |
2807 | 'mouse-face 'bold-italic) | |
2808 | " and " | |
2809 | (propertize "bar" 'face 'italic | |
2810 | 'mouse-face 'bold-italic)) | |
2811 | @result{} #("foo and bar" | |
2812 | 0 3 (face italic mouse-face bold-italic) | |
2813 | 3 8 nil | |
2814 | 8 11 (face italic mouse-face bold-italic)) | |
2815 | @end smallexample | |
2816 | @end defun | |
2817 | ||
049bcbcb CY |
2818 | @xref{Buffer Contents}, for the function |
2819 | @code{buffer-substring-no-properties}, which copies text from the | |
2820 | buffer but does not copy its properties. | |
b8d4c8d0 GM |
2821 | |
2822 | @node Property Search | |
2823 | @subsection Text Property Search Functions | |
2824 | ||
2825 | In typical use of text properties, most of the time several or many | |
2826 | consecutive characters have the same value for a property. Rather than | |
2827 | writing your programs to examine characters one by one, it is much | |
2828 | faster to process chunks of text that have the same property value. | |
2829 | ||
2830 | Here are functions you can use to do this. They use @code{eq} for | |
2831 | comparing property values. In all cases, @var{object} defaults to the | |
2832 | current buffer. | |
2833 | ||
2834 | For high performance, it's very important to use the @var{limit} | |
2835 | argument to these functions, especially the ones that search for a | |
2836 | single property---otherwise, they may spend a long time scanning to the | |
2837 | end of the buffer, if the property you are interested in does not change. | |
2838 | ||
2839 | These functions do not move point; instead, they return a position (or | |
2840 | @code{nil}). Remember that a position is always between two characters; | |
2841 | the position returned by these functions is between two characters with | |
2842 | different properties. | |
2843 | ||
2844 | @defun next-property-change pos &optional object limit | |
2845 | The function scans the text forward from position @var{pos} in the | |
2846 | string or buffer @var{object} till it finds a change in some text | |
2847 | property, then returns the position of the change. In other words, it | |
2848 | returns the position of the first character beyond @var{pos} whose | |
2849 | properties are not identical to those of the character just after | |
2850 | @var{pos}. | |
2851 | ||
2852 | If @var{limit} is non-@code{nil}, then the scan ends at position | |
2853 | @var{limit}. If there is no property change before that point, | |
2854 | @code{next-property-change} returns @var{limit}. | |
2855 | ||
2856 | The value is @code{nil} if the properties remain unchanged all the way | |
2857 | to the end of @var{object} and @var{limit} is @code{nil}. If the value | |
2858 | is non-@code{nil}, it is a position greater than or equal to @var{pos}. | |
2859 | The value equals @var{pos} only when @var{limit} equals @var{pos}. | |
2860 | ||
2861 | Here is an example of how to scan the buffer by chunks of text within | |
2862 | which all properties are constant: | |
2863 | ||
2864 | @smallexample | |
2865 | (while (not (eobp)) | |
2866 | (let ((plist (text-properties-at (point))) | |
2867 | (next-change | |
2868 | (or (next-property-change (point) (current-buffer)) | |
2869 | (point-max)))) | |
2870 | @r{Process text from point to @var{next-change}@dots{}} | |
2871 | (goto-char next-change))) | |
2872 | @end smallexample | |
2873 | @end defun | |
2874 | ||
2875 | @defun previous-property-change pos &optional object limit | |
2876 | This is like @code{next-property-change}, but scans back from @var{pos} | |
2877 | instead of forward. If the value is non-@code{nil}, it is a position | |
2878 | less than or equal to @var{pos}; it equals @var{pos} only if @var{limit} | |
2879 | equals @var{pos}. | |
2880 | @end defun | |
2881 | ||
2882 | @defun next-single-property-change pos prop &optional object limit | |
2883 | The function scans text for a change in the @var{prop} property, then | |
2884 | returns the position of the change. The scan goes forward from | |
2885 | position @var{pos} in the string or buffer @var{object}. In other | |
2886 | words, this function returns the position of the first character | |
2887 | beyond @var{pos} whose @var{prop} property differs from that of the | |
2888 | character just after @var{pos}. | |
2889 | ||
2890 | If @var{limit} is non-@code{nil}, then the scan ends at position | |
2891 | @var{limit}. If there is no property change before that point, | |
2892 | @code{next-single-property-change} returns @var{limit}. | |
2893 | ||
2894 | The value is @code{nil} if the property remains unchanged all the way to | |
2895 | the end of @var{object} and @var{limit} is @code{nil}. If the value is | |
2896 | non-@code{nil}, it is a position greater than or equal to @var{pos}; it | |
2897 | equals @var{pos} only if @var{limit} equals @var{pos}. | |
2898 | @end defun | |
2899 | ||
2900 | @defun previous-single-property-change pos prop &optional object limit | |
2901 | This is like @code{next-single-property-change}, but scans back from | |
2902 | @var{pos} instead of forward. If the value is non-@code{nil}, it is a | |
2903 | position less than or equal to @var{pos}; it equals @var{pos} only if | |
2904 | @var{limit} equals @var{pos}. | |
2905 | @end defun | |
2906 | ||
2907 | @defun next-char-property-change pos &optional limit | |
2908 | This is like @code{next-property-change} except that it considers | |
2909 | overlay properties as well as text properties, and if no change is | |
2910 | found before the end of the buffer, it returns the maximum buffer | |
2911 | position rather than @code{nil} (in this sense, it resembles the | |
2912 | corresponding overlay function @code{next-overlay-change}, rather than | |
2913 | @code{next-property-change}). There is no @var{object} operand | |
2914 | because this function operates only on the current buffer. It returns | |
2915 | the next address at which either kind of property changes. | |
2916 | @end defun | |
2917 | ||
2918 | @defun previous-char-property-change pos &optional limit | |
2919 | This is like @code{next-char-property-change}, but scans back from | |
2920 | @var{pos} instead of forward, and returns the minimum buffer | |
2921 | position if no change is found. | |
2922 | @end defun | |
2923 | ||
2924 | @defun next-single-char-property-change pos prop &optional object limit | |
2925 | This is like @code{next-single-property-change} except that it | |
2926 | considers overlay properties as well as text properties, and if no | |
2927 | change is found before the end of the @var{object}, it returns the | |
2928 | maximum valid position in @var{object} rather than @code{nil}. Unlike | |
2929 | @code{next-char-property-change}, this function @emph{does} have an | |
2930 | @var{object} operand; if @var{object} is not a buffer, only | |
2931 | text-properties are considered. | |
2932 | @end defun | |
2933 | ||
2934 | @defun previous-single-char-property-change pos prop &optional object limit | |
2935 | This is like @code{next-single-char-property-change}, but scans back | |
2936 | from @var{pos} instead of forward, and returns the minimum valid | |
2937 | position in @var{object} if no change is found. | |
2938 | @end defun | |
2939 | ||
2940 | @defun text-property-any start end prop value &optional object | |
2941 | This function returns non-@code{nil} if at least one character between | |
2942 | @var{start} and @var{end} has a property @var{prop} whose value is | |
2943 | @var{value}. More precisely, it returns the position of the first such | |
2944 | character. Otherwise, it returns @code{nil}. | |
2945 | ||
2946 | The optional fifth argument, @var{object}, specifies the string or | |
2947 | buffer to scan. Positions are relative to @var{object}. The default | |
2948 | for @var{object} is the current buffer. | |
2949 | @end defun | |
2950 | ||
2951 | @defun text-property-not-all start end prop value &optional object | |
2952 | This function returns non-@code{nil} if at least one character between | |
2953 | @var{start} and @var{end} does not have a property @var{prop} with value | |
2954 | @var{value}. More precisely, it returns the position of the first such | |
2955 | character. Otherwise, it returns @code{nil}. | |
2956 | ||
2957 | The optional fifth argument, @var{object}, specifies the string or | |
2958 | buffer to scan. Positions are relative to @var{object}. The default | |
2959 | for @var{object} is the current buffer. | |
2960 | @end defun | |
2961 | ||
2962 | @node Special Properties | |
2963 | @subsection Properties with Special Meanings | |
2964 | ||
2965 | Here is a table of text property names that have special built-in | |
2966 | meanings. The following sections list a few additional special property | |
2967 | names that control filling and property inheritance. All other names | |
2968 | have no standard meaning, and you can use them as you like. | |
2969 | ||
2970 | Note: the properties @code{composition}, @code{display}, | |
2971 | @code{invisible} and @code{intangible} can also cause point to move to | |
2972 | an acceptable place, after each Emacs command. @xref{Adjusting | |
2973 | Point}. | |
2974 | ||
2975 | @table @code | |
2976 | @cindex property category of text character | |
2977 | @kindex category @r{(text property)} | |
2978 | @item category | |
2979 | If a character has a @code{category} property, we call it the | |
2980 | @dfn{property category} of the character. It should be a symbol. The | |
2981 | properties of this symbol serve as defaults for the properties of the | |
2982 | character. | |
2983 | ||
2984 | @item face | |
2985 | @cindex face codes of text | |
2986 | @kindex face @r{(text property)} | |
2987 | You can use the property @code{face} to control the font and color of | |
2988 | text. @xref{Faces}, for more information. | |
2989 | ||
d94d85e9 | 2990 | @code{face} can be the following: |
b8d4c8d0 GM |
2991 | |
2992 | @itemize @bullet | |
2993 | @item | |
2994 | A face name (a symbol or string). | |
2995 | ||
2996 | @item | |
2997 | A property list of face attributes. This has the | |
2998 | form (@var{keyword} @var{value} @dots{}), where each @var{keyword} is a | |
2999 | face attribute name and @var{value} is a meaningful value for that | |
3000 | attribute. With this feature, you do not need to create a face each | |
3001 | time you want to specify a particular attribute for certain text. | |
3002 | @xref{Face Attributes}. | |
b8d4c8d0 GM |
3003 | @end itemize |
3004 | ||
d94d85e9 LMI |
3005 | @code{face} can also be a list, where each element uses one of the |
3006 | forms listed above. | |
db3625ba RS |
3007 | |
3008 | Font Lock mode (@pxref{Font Lock Mode}) works in most buffers by | |
3009 | dynamically updating the @code{face} property of characters based on | |
3010 | the context. | |
b8d4c8d0 GM |
3011 | |
3012 | @item font-lock-face | |
3013 | @kindex font-lock-face @r{(text property)} | |
eeafcea7 CY |
3014 | This property specifies a value for the @code{face} property that Font |
3015 | Lock mode should apply to the underlying text. It is one of the | |
3016 | fontification methods used by Font Lock mode, and is useful for | |
3017 | special modes that implement their own highlighting. | |
3018 | @xref{Precalculated Fontification}. When Font Lock mode is disabled, | |
db3625ba | 3019 | @code{font-lock-face} has no effect. |
b8d4c8d0 | 3020 | |
b8d4c8d0 GM |
3021 | @item mouse-face |
3022 | @kindex mouse-face @r{(text property)} | |
eeafcea7 CY |
3023 | This property is used instead of @code{face} when the mouse is on or |
3024 | near the character. For this purpose, ``near'' means that all text | |
3025 | between the character and where the mouse is have the same | |
b8d4c8d0 GM |
3026 | @code{mouse-face} property value. |
3027 | ||
ebb552ed CY |
3028 | Emacs ignores all face attributes from the @code{mouse-face} property |
3029 | that alter the text size (e.g. @code{:height}, @code{:weight}, and | |
3030 | @code{:slant}). Those attributes are always the same as for the | |
3031 | unhighlighted text. | |
3032 | ||
b8d4c8d0 GM |
3033 | @item fontified |
3034 | @kindex fontified @r{(text property)} | |
3035 | This property says whether the text is ready for display. If | |
3036 | @code{nil}, Emacs's redisplay routine calls the functions in | |
3037 | @code{fontification-functions} (@pxref{Auto Faces}) to prepare this | |
3038 | part of the buffer before it is displayed. It is used internally by | |
3039 | the ``just in time'' font locking code. | |
3040 | ||
3041 | @item display | |
3042 | This property activates various features that change the | |
3043 | way text is displayed. For example, it can make text appear taller | |
3044 | or shorter, higher or lower, wider or narrow, or replaced with an image. | |
3045 | @xref{Display Property}. | |
3046 | ||
3047 | @item help-echo | |
3048 | @kindex help-echo @r{(text property)} | |
3049 | @cindex tooltip | |
3050 | @anchor{Text help-echo} | |
3051 | If text has a string as its @code{help-echo} property, then when you | |
3052 | move the mouse onto that text, Emacs displays that string in the echo | |
3053 | area, or in the tooltip window (@pxref{Tooltips,,, emacs, The GNU Emacs | |
3054 | Manual}). | |
3055 | ||
3056 | If the value of the @code{help-echo} property is a function, that | |
3057 | function is called with three arguments, @var{window}, @var{object} and | |
3058 | @var{pos} and should return a help string or @code{nil} for | |
3059 | none. The first argument, @var{window} is the window in which | |
3060 | the help was found. The second, @var{object}, is the buffer, overlay or | |
3061 | string which had the @code{help-echo} property. The @var{pos} | |
3062 | argument is as follows: | |
3063 | ||
3064 | @itemize @bullet{} | |
3065 | @item | |
3066 | If @var{object} is a buffer, @var{pos} is the position in the buffer. | |
3067 | @item | |
3068 | If @var{object} is an overlay, that overlay has a @code{help-echo} | |
3069 | property, and @var{pos} is the position in the overlay's buffer. | |
3070 | @item | |
3071 | If @var{object} is a string (an overlay string or a string displayed | |
3072 | with the @code{display} property), @var{pos} is the position in that | |
3073 | string. | |
3074 | @end itemize | |
3075 | ||
3076 | If the value of the @code{help-echo} property is neither a function nor | |
3077 | a string, it is evaluated to obtain a help string. | |
3078 | ||
3079 | You can alter the way help text is displayed by setting the variable | |
3080 | @code{show-help-function} (@pxref{Help display}). | |
3081 | ||
3082 | This feature is used in the mode line and for other active text. | |
3083 | ||
3084 | @item keymap | |
3085 | @cindex keymap of character | |
3086 | @kindex keymap @r{(text property)} | |
3087 | The @code{keymap} property specifies an additional keymap for | |
3088 | commands. When this keymap applies, it is used for key lookup before | |
3089 | the minor mode keymaps and before the buffer's local map. | |
3090 | @xref{Active Keymaps}. If the property value is a symbol, the | |
3091 | symbol's function definition is used as the keymap. | |
3092 | ||
3093 | The property's value for the character before point applies if it is | |
3094 | non-@code{nil} and rear-sticky, and the property's value for the | |
3095 | character after point applies if it is non-@code{nil} and | |
3096 | front-sticky. (For mouse clicks, the position of the click is used | |
3097 | instead of the position of point.) | |
3098 | ||
3099 | @item local-map | |
3100 | @kindex local-map @r{(text property)} | |
3101 | This property works like @code{keymap} except that it specifies a | |
3102 | keymap to use @emph{instead of} the buffer's local map. For most | |
3103 | purposes (perhaps all purposes), it is better to use the @code{keymap} | |
3104 | property. | |
3105 | ||
3106 | @item syntax-table | |
3107 | The @code{syntax-table} property overrides what the syntax table says | |
3108 | about this particular character. @xref{Syntax Properties}. | |
3109 | ||
3110 | @item read-only | |
3111 | @cindex read-only character | |
3112 | @kindex read-only @r{(text property)} | |
3113 | If a character has the property @code{read-only}, then modifying that | |
3114 | character is not allowed. Any command that would do so gets an error, | |
3115 | @code{text-read-only}. If the property value is a string, that string | |
3116 | is used as the error message. | |
3117 | ||
3118 | Insertion next to a read-only character is an error if inserting | |
3119 | ordinary text there would inherit the @code{read-only} property due to | |
3120 | stickiness. Thus, you can control permission to insert next to | |
3121 | read-only text by controlling the stickiness. @xref{Sticky Properties}. | |
3122 | ||
3123 | Since changing properties counts as modifying the buffer, it is not | |
3124 | possible to remove a @code{read-only} property unless you know the | |
3125 | special trick: bind @code{inhibit-read-only} to a non-@code{nil} value | |
3126 | and then remove the property. @xref{Read Only Buffers}. | |
3127 | ||
3128 | @item invisible | |
3129 | @kindex invisible @r{(text property)} | |
3130 | A non-@code{nil} @code{invisible} property can make a character invisible | |
3131 | on the screen. @xref{Invisible Text}, for details. | |
3132 | ||
3133 | @item intangible | |
3134 | @kindex intangible @r{(text property)} | |
3135 | If a group of consecutive characters have equal and non-@code{nil} | |
3136 | @code{intangible} properties, then you cannot place point between them. | |
3137 | If you try to move point forward into the group, point actually moves to | |
3138 | the end of the group. If you try to move point backward into the group, | |
3139 | point actually moves to the start of the group. | |
3140 | ||
3141 | If consecutive characters have unequal non-@code{nil} | |
3142 | @code{intangible} properties, they belong to separate groups; each | |
3143 | group is separately treated as described above. | |
3144 | ||
3145 | When the variable @code{inhibit-point-motion-hooks} is non-@code{nil}, | |
3146 | the @code{intangible} property is ignored. | |
3147 | ||
a7cdbfce SM |
3148 | Beware: this property operates at a very low level, and affects a lot of code |
3149 | in unexpected ways. So use it with extreme caution. A common misuse is to put | |
3150 | an intangible property on invisible text, which is actually unnecessary since | |
3151 | the command loop will move point outside of the invisible text at the end of | |
3152 | each command anyway. @xref{Adjusting Point}. | |
3153 | ||
b8d4c8d0 GM |
3154 | @item field |
3155 | @kindex field @r{(text property)} | |
3156 | Consecutive characters with the same @code{field} property constitute a | |
3157 | @dfn{field}. Some motion functions including @code{forward-word} and | |
3158 | @code{beginning-of-line} stop moving at a field boundary. | |
3159 | @xref{Fields}. | |
3160 | ||
3161 | @item cursor | |
3162 | @kindex cursor @r{(text property)} | |
3163 | Normally, the cursor is displayed at the end of any overlay and text | |
b640eb52 | 3164 | property strings present at the current buffer position. You can |
b8d4c8d0 | 3165 | place the cursor on any desired character of these strings by giving |
b640eb52 EZ |
3166 | that character a non-@code{nil} @code{cursor} text property. In |
3167 | addition, if the value of the @code{cursor} property of an overlay | |
3168 | string is an integer number, it specifies the number of buffer's | |
3169 | character positions associated with the overlay string; this way, | |
3170 | Emacs will display the cursor on the character with that property | |
3171 | regardless of whether the current buffer position is actually covered | |
3172 | by the overlay. Specifically, if the value of the @code{cursor} | |
3173 | property of a character is the number @var{n}, the cursor will be | |
3174 | displayed on this character for any buffer position in the range | |
3175 | @code{[@var{ovpos}..@var{ovpos}+@var{n}]}, where @var{ovpos} is the | |
3176 | starting buffer position covered by the overlay (@pxref{Managing | |
3177 | Overlays}). | |
b8d4c8d0 GM |
3178 | |
3179 | @item pointer | |
3180 | @kindex pointer @r{(text property)} | |
3181 | This specifies a specific pointer shape when the mouse pointer is over | |
3182 | this text or image. @xref{Pointer Shape}, for possible pointer | |
3183 | shapes. | |
3184 | ||
3185 | @item line-spacing | |
3186 | @kindex line-spacing @r{(text property)} | |
3187 | A newline can have a @code{line-spacing} text or overlay property that | |
3188 | controls the height of the display line ending with that newline. The | |
3189 | property value overrides the default frame line spacing and the buffer | |
3190 | local @code{line-spacing} variable. @xref{Line Height}. | |
3191 | ||
3192 | @item line-height | |
3193 | @kindex line-height @r{(text property)} | |
3194 | A newline can have a @code{line-height} text or overlay property that | |
3195 | controls the total height of the display line ending in that newline. | |
3196 | @xref{Line Height}. | |
3197 | ||
c4f4682b MB |
3198 | @item wrap-prefix |
3199 | If text has a @code{wrap-prefix} property, the prefix it defines will | |
579ebf8f | 3200 | be added at display time to the beginning of every continuation line |
c4f4682b | 3201 | due to text wrapping (so if lines are truncated, the wrap-prefix is |
579ebf8f EZ |
3202 | never used). It may be a string or an image (@pxref{Other Display |
3203 | Specs}), or a stretch of whitespace such as specified by the | |
3204 | @code{:width} or @code{:align-to} display properties (@pxref{Specified | |
3205 | Space}). | |
c4f4682b MB |
3206 | |
3207 | A wrap-prefix may also be specified for an entire buffer using the | |
3208 | @code{wrap-prefix} buffer-local variable (however, a | |
3209 | @code{wrap-prefix} text-property takes precedence over the value of | |
3210 | the @code{wrap-prefix} variable). @xref{Truncation}. | |
3211 | ||
3212 | @item line-prefix | |
3213 | If text has a @code{line-prefix} property, the prefix it defines will | |
579ebf8f EZ |
3214 | be added at display time to the beginning of every non-continuation |
3215 | line. It may be a string or an image (@pxref{Other Display | |
3216 | Specs}), or a stretch of whitespace such as specified by the | |
3217 | @code{:width} or @code{:align-to} display properties (@pxref{Specified | |
3218 | Space}). | |
c4f4682b MB |
3219 | |
3220 | A line-prefix may also be specified for an entire buffer using the | |
3221 | @code{line-prefix} buffer-local variable (however, a | |
3222 | @code{line-prefix} text-property takes precedence over the value of | |
3223 | the @code{line-prefix} variable). @xref{Truncation}. | |
3224 | ||
b8d4c8d0 GM |
3225 | @item modification-hooks |
3226 | @cindex change hooks for a character | |
3227 | @cindex hooks for changing a character | |
3228 | @kindex modification-hooks @r{(text property)} | |
3229 | If a character has the property @code{modification-hooks}, then its | |
f816790b SM |
3230 | value should be a list of functions; modifying that character calls |
3231 | all of those functions before the actual modification. Each function | |
3232 | receives two arguments: the beginning and end of the part of the | |
3233 | buffer being modified. Note that if a particular modification hook | |
3234 | function appears on several characters being modified by a single | |
3235 | primitive, you can't predict how many times the function will | |
3236 | be called. | |
3237 | Furthermore, insertion will not modify any existing character, so this | |
3238 | hook will only be run when removing some characters, replacing them | |
3239 | with others, or changing their text-properties. | |
b8d4c8d0 GM |
3240 | |
3241 | If these functions modify the buffer, they should bind | |
3242 | @code{inhibit-modification-hooks} to @code{t} around doing so, to | |
3243 | avoid confusing the internal mechanism that calls these hooks. | |
3244 | ||
3245 | Overlays also support the @code{modification-hooks} property, but the | |
3246 | details are somewhat different (@pxref{Overlay Properties}). | |
3247 | ||
3248 | @item insert-in-front-hooks | |
3249 | @itemx insert-behind-hooks | |
3250 | @kindex insert-in-front-hooks @r{(text property)} | |
3251 | @kindex insert-behind-hooks @r{(text property)} | |
3252 | The operation of inserting text in a buffer also calls the functions | |
3253 | listed in the @code{insert-in-front-hooks} property of the following | |
3254 | character and in the @code{insert-behind-hooks} property of the | |
3255 | preceding character. These functions receive two arguments, the | |
3256 | beginning and end of the inserted text. The functions are called | |
3257 | @emph{after} the actual insertion takes place. | |
3258 | ||
3259 | See also @ref{Change Hooks}, for other hooks that are called | |
3260 | when you change text in a buffer. | |
3261 | ||
3262 | @item point-entered | |
3263 | @itemx point-left | |
3264 | @cindex hooks for motion of point | |
3265 | @kindex point-entered @r{(text property)} | |
3266 | @kindex point-left @r{(text property)} | |
3267 | The special properties @code{point-entered} and @code{point-left} | |
3268 | record hook functions that report motion of point. Each time point | |
3269 | moves, Emacs compares these two property values: | |
3270 | ||
3271 | @itemize @bullet | |
3272 | @item | |
3273 | the @code{point-left} property of the character after the old location, | |
3274 | and | |
3275 | @item | |
3276 | the @code{point-entered} property of the character after the new | |
3277 | location. | |
3278 | @end itemize | |
3279 | ||
3280 | @noindent | |
3281 | If these two values differ, each of them is called (if not @code{nil}) | |
3282 | with two arguments: the old value of point, and the new one. | |
3283 | ||
3284 | The same comparison is made for the characters before the old and new | |
3285 | locations. The result may be to execute two @code{point-left} functions | |
3286 | (which may be the same function) and/or two @code{point-entered} | |
3287 | functions (which may be the same function). In any case, all the | |
3288 | @code{point-left} functions are called first, followed by all the | |
3289 | @code{point-entered} functions. | |
3290 | ||
e3934a8a | 3291 | It is possible to use @code{char-after} to examine characters at various |
b8d4c8d0 GM |
3292 | buffer positions without moving point to those positions. Only an |
3293 | actual change in the value of point runs these hook functions. | |
3294 | ||
e3934a8a EZ |
3295 | The variable @code{inhibit-point-motion-hooks} can inhibit running the |
3296 | @code{point-left} and @code{point-entered} hooks, see @ref{Inhibit | |
3297 | point motion hooks}. | |
3298 | ||
3299 | @item composition | |
3300 | @kindex composition @r{(text property)} | |
3301 | This text property is used to display a sequence of characters as a | |
3302 | single glyph composed from components. But the value of the property | |
3303 | itself is completely internal to Emacs and should not be manipulated | |
3304 | directly by, for instance, @code{put-text-property}. | |
3305 | ||
3306 | @end table | |
3307 | ||
b8d4c8d0 | 3308 | @defvar inhibit-point-motion-hooks |
e3934a8a EZ |
3309 | @anchor{Inhibit point motion hooks} When this variable is |
3310 | non-@code{nil}, @code{point-left} and @code{point-entered} hooks are | |
3311 | not run, and the @code{intangible} property has no effect. Do not set | |
3312 | this variable globally; bind it with @code{let}. | |
b8d4c8d0 GM |
3313 | @end defvar |
3314 | ||
3315 | @defvar show-help-function | |
3316 | @anchor{Help display} If this variable is non-@code{nil}, it specifies a | |
3317 | function called to display help strings. These may be @code{help-echo} | |
3318 | properties, menu help strings (@pxref{Simple Menu Items}, | |
3319 | @pxref{Extended Menu Items}), or tool bar help strings (@pxref{Tool | |
3320 | Bar}). The specified function is called with one argument, the help | |
3321 | string to display. Tooltip mode (@pxref{Tooltips,,, emacs, The GNU Emacs | |
3322 | Manual}) provides an example. | |
3323 | @end defvar | |
3324 | ||
b8d4c8d0 GM |
3325 | @node Format Properties |
3326 | @subsection Formatted Text Properties | |
3327 | ||
3328 | These text properties affect the behavior of the fill commands. They | |
3329 | are used for representing formatted text. @xref{Filling}, and | |
3330 | @ref{Margins}. | |
3331 | ||
3332 | @table @code | |
3333 | @item hard | |
3334 | If a newline character has this property, it is a ``hard'' newline. | |
3335 | The fill commands do not alter hard newlines and do not move words | |
3336 | across them. However, this property takes effect only if the | |
3337 | @code{use-hard-newlines} minor mode is enabled. @xref{Hard and Soft | |
3338 | Newlines,, Hard and Soft Newlines, emacs, The GNU Emacs Manual}. | |
3339 | ||
3340 | @item right-margin | |
3341 | This property specifies an extra right margin for filling this part of the | |
3342 | text. | |
3343 | ||
3344 | @item left-margin | |
3345 | This property specifies an extra left margin for filling this part of the | |
3346 | text. | |
3347 | ||
3348 | @item justification | |
3349 | This property specifies the style of justification for filling this part | |
3350 | of the text. | |
3351 | @end table | |
3352 | ||
3353 | @node Sticky Properties | |
3354 | @subsection Stickiness of Text Properties | |
3355 | @cindex sticky text properties | |
3356 | @cindex inheritance of text properties | |
3357 | ||
3358 | Self-inserting characters normally take on the same properties as the | |
3359 | preceding character. This is called @dfn{inheritance} of properties. | |
3360 | ||
3361 | In a Lisp program, you can do insertion with inheritance or without, | |
3362 | depending on your choice of insertion primitive. The ordinary text | |
3363 | insertion functions such as @code{insert} do not inherit any properties. | |
3364 | They insert text with precisely the properties of the string being | |
3365 | inserted, and no others. This is correct for programs that copy text | |
3366 | from one context to another---for example, into or out of the kill ring. | |
3367 | To insert with inheritance, use the special primitives described in this | |
3368 | section. Self-inserting characters inherit properties because they work | |
3369 | using these primitives. | |
3370 | ||
3371 | When you do insertion with inheritance, @emph{which} properties are | |
3372 | inherited, and from where, depends on which properties are @dfn{sticky}. | |
3373 | Insertion after a character inherits those of its properties that are | |
3374 | @dfn{rear-sticky}. Insertion before a character inherits those of its | |
3375 | properties that are @dfn{front-sticky}. When both sides offer different | |
3376 | sticky values for the same property, the previous character's value | |
3377 | takes precedence. | |
3378 | ||
3379 | By default, a text property is rear-sticky but not front-sticky; thus, | |
3380 | the default is to inherit all the properties of the preceding character, | |
3381 | and nothing from the following character. | |
3382 | ||
3383 | You can control the stickiness of various text properties with two | |
3384 | specific text properties, @code{front-sticky} and @code{rear-nonsticky}, | |
3385 | and with the variable @code{text-property-default-nonsticky}. You can | |
3386 | use the variable to specify a different default for a given property. | |
3387 | You can use those two text properties to make any specific properties | |
3388 | sticky or nonsticky in any particular part of the text. | |
3389 | ||
3390 | If a character's @code{front-sticky} property is @code{t}, then all | |
3391 | its properties are front-sticky. If the @code{front-sticky} property is | |
3392 | a list, then the sticky properties of the character are those whose | |
3393 | names are in the list. For example, if a character has a | |
3394 | @code{front-sticky} property whose value is @code{(face read-only)}, | |
3395 | then insertion before the character can inherit its @code{face} property | |
3396 | and its @code{read-only} property, but no others. | |
3397 | ||
3398 | The @code{rear-nonsticky} property works the opposite way. Most | |
3399 | properties are rear-sticky by default, so the @code{rear-nonsticky} | |
3400 | property says which properties are @emph{not} rear-sticky. If a | |
3401 | character's @code{rear-nonsticky} property is @code{t}, then none of its | |
3402 | properties are rear-sticky. If the @code{rear-nonsticky} property is a | |
3403 | list, properties are rear-sticky @emph{unless} their names are in the | |
3404 | list. | |
3405 | ||
3406 | @defvar text-property-default-nonsticky | |
3407 | This variable holds an alist which defines the default rear-stickiness | |
3408 | of various text properties. Each element has the form | |
3409 | @code{(@var{property} . @var{nonstickiness})}, and it defines the | |
3410 | stickiness of a particular text property, @var{property}. | |
3411 | ||
3412 | If @var{nonstickiness} is non-@code{nil}, this means that the property | |
3413 | @var{property} is rear-nonsticky by default. Since all properties are | |
3414 | front-nonsticky by default, this makes @var{property} nonsticky in both | |
3415 | directions by default. | |
3416 | ||
3417 | The text properties @code{front-sticky} and @code{rear-nonsticky}, when | |
3418 | used, take precedence over the default @var{nonstickiness} specified in | |
3419 | @code{text-property-default-nonsticky}. | |
3420 | @end defvar | |
3421 | ||
3422 | Here are the functions that insert text with inheritance of properties: | |
3423 | ||
3424 | @defun insert-and-inherit &rest strings | |
3425 | Insert the strings @var{strings}, just like the function @code{insert}, | |
3426 | but inherit any sticky properties from the adjoining text. | |
3427 | @end defun | |
3428 | ||
3429 | @defun insert-before-markers-and-inherit &rest strings | |
3430 | Insert the strings @var{strings}, just like the function | |
3431 | @code{insert-before-markers}, but inherit any sticky properties from the | |
3432 | adjoining text. | |
3433 | @end defun | |
3434 | ||
3435 | @xref{Insertion}, for the ordinary insertion functions which do not | |
3436 | inherit. | |
3437 | ||
3438 | @node Lazy Properties | |
3439 | @subsection Lazy Computation of Text Properties | |
3440 | ||
3441 | Instead of computing text properties for all the text in the buffer, | |
3442 | you can arrange to compute the text properties for parts of the text | |
3443 | when and if something depends on them. | |
3444 | ||
3445 | The primitive that extracts text from the buffer along with its | |
3446 | properties is @code{buffer-substring}. Before examining the properties, | |
3447 | this function runs the abnormal hook @code{buffer-access-fontify-functions}. | |
3448 | ||
3449 | @defvar buffer-access-fontify-functions | |
3450 | This variable holds a list of functions for computing text properties. | |
3451 | Before @code{buffer-substring} copies the text and text properties for a | |
3452 | portion of the buffer, it calls all the functions in this list. Each of | |
3453 | the functions receives two arguments that specify the range of the | |
3454 | buffer being accessed. (The buffer itself is always the current | |
3455 | buffer.) | |
3456 | @end defvar | |
3457 | ||
3458 | The function @code{buffer-substring-no-properties} does not call these | |
3459 | functions, since it ignores text properties anyway. | |
3460 | ||
3461 | In order to prevent the hook functions from being called more than | |
3462 | once for the same part of the buffer, you can use the variable | |
3463 | @code{buffer-access-fontified-property}. | |
3464 | ||
3465 | @defvar buffer-access-fontified-property | |
3466 | If this variable's value is non-@code{nil}, it is a symbol which is used | |
3467 | as a text property name. A non-@code{nil} value for that text property | |
3468 | means, ``the other text properties for this character have already been | |
3469 | computed.'' | |
3470 | ||
3471 | If all the characters in the range specified for @code{buffer-substring} | |
3472 | have a non-@code{nil} value for this property, @code{buffer-substring} | |
3473 | does not call the @code{buffer-access-fontify-functions} functions. It | |
3474 | assumes these characters already have the right text properties, and | |
3475 | just copies the properties they already have. | |
3476 | ||
3477 | The normal way to use this feature is that the | |
3478 | @code{buffer-access-fontify-functions} functions add this property, as | |
3479 | well as others, to the characters they operate on. That way, they avoid | |
3480 | being called over and over for the same text. | |
3481 | @end defvar | |
3482 | ||
3483 | @node Clickable Text | |
3484 | @subsection Defining Clickable Text | |
3485 | @cindex clickable text | |
2bad3299 CY |
3486 | @cindex follow links |
3487 | @cindex mouse-1 | |
b8d4c8d0 GM |
3488 | |
3489 | @dfn{Clickable text} is text that can be clicked, with either the | |
2bad3299 CY |
3490 | mouse or via a keyboard command, to produce some result. Many major |
3491 | modes use clickable text to implement textual hyper-links, or | |
3492 | @dfn{links} for short. | |
3493 | ||
3494 | The easiest way to insert and manipulate links is to use the | |
3495 | @code{button} package. @xref{Buttons}. In this section, we will | |
3496 | explain how to manually set up clickable text in a buffer, using text | |
3497 | properties. For simplicity, we will refer to the clickable text as a | |
3498 | @dfn{link}. | |
3499 | ||
3500 | Implementing a link involves three separate steps: (1) indicating | |
3501 | clickability when the mouse moves over the link; (2) making @kbd{RET} | |
3502 | or @kbd{Mouse-2} on that link do something; and (3) setting up a | |
3503 | @code{follow-link} condition so that the link obeys | |
3504 | @code{mouse-1-click-follows-link}. | |
3505 | ||
3506 | To indicate clickability, add the @code{mouse-face} text property to | |
3507 | the text of the link; then Emacs will highlight the link when the | |
3508 | mouse moves over it. In addition, you should define a tooltip or echo | |
3509 | area message, using the @code{help-echo} text property. @xref{Special | |
3510 | Properties}. For instance, here is how Dired indicates that file | |
3511 | names are clickable: | |
b8d4c8d0 GM |
3512 | |
3513 | @smallexample | |
2bad3299 CY |
3514 | (if (dired-move-to-filename) |
3515 | (add-text-properties | |
3516 | (point) | |
3517 | (save-excursion | |
3518 | (dired-move-to-end-of-filename) | |
3519 | (point)) | |
3520 | '(mouse-face highlight | |
3521 | help-echo "mouse-2: visit this file in other window"))) | |
b8d4c8d0 GM |
3522 | @end smallexample |
3523 | ||
2bad3299 CY |
3524 | To make the link clickable, bind @key{RET} and @kbd{Mouse-2} to |
3525 | commands that perform the desired action. Each command should check | |
3526 | to see whether it was called on a link, and act accordingly. For | |
3527 | instance, Dired's major mode keymap binds @kbd{Mouse-2} to the | |
3528 | following command: | |
b8d4c8d0 GM |
3529 | |
3530 | @smallexample | |
3531 | (defun dired-mouse-find-file-other-window (event) | |
3532 | "In Dired, visit the file or directory name you click on." | |
3533 | (interactive "e") | |
c57008f6 SM |
3534 | (let ((window (posn-window (event-end event))) |
3535 | (pos (posn-point (event-end event))) | |
3536 | file) | |
3537 | (if (not (windowp window)) | |
3538 | (error "No file chosen")) | |
3539 | (with-current-buffer (window-buffer window) | |
b8d4c8d0 GM |
3540 | (goto-char pos) |
3541 | (setq file (dired-get-file-for-visit))) | |
3542 | (if (file-directory-p file) | |
3543 | (or (and (cdr dired-subdir-alist) | |
3544 | (dired-goto-subdir file)) | |
3545 | (progn | |
3546 | (select-window window) | |
3547 | (dired-other-window file))) | |
3548 | (select-window window) | |
3549 | (find-file-other-window (file-name-sans-versions file t))))) | |
3550 | @end smallexample | |
3551 | ||
3552 | @noindent | |
2bad3299 CY |
3553 | This command uses the functions @code{posn-window} and |
3554 | @code{posn-point} to determine where the click occurred, and | |
3555 | @code{dired-get-file-for-visit} to determine which file to visit. | |
b8d4c8d0 | 3556 | |
2bad3299 CY |
3557 | Instead of binding the mouse command in a major mode keymap, you can |
3558 | bind it within the link text, using the @code{keymap} text property | |
3559 | (@pxref{Special Properties}). For instance: | |
b8d4c8d0 GM |
3560 | |
3561 | @example | |
3562 | (let ((map (make-sparse-keymap))) | |
3563 | (define-key map [mouse-2] 'operate-this-button) | |
2bad3299 | 3564 | (put-text-property link-start link-end 'keymap map)) |
b8d4c8d0 GM |
3565 | @end example |
3566 | ||
3567 | @noindent | |
2bad3299 CY |
3568 | With this method, you can easily define different commands for |
3569 | different links. Furthermore, the global definition of @key{RET} and | |
3570 | @kbd{Mouse-2} remain available for the rest of the text in the buffer. | |
3571 | ||
3572 | @vindex mouse-1-click-follows-link | |
3573 | The basic Emacs command for clicking on links is @kbd{Mouse-2}. | |
3574 | However, for compatibility with other graphical applications, Emacs | |
3575 | also recognizes @kbd{Mouse-1} clicks on links, provided the user | |
3576 | clicks on the link quickly without moving the mouse. This behavior is | |
3577 | controlled by the user option @code{mouse-1-click-follows-link}. | |
3578 | @xref{Mouse References,,, emacs, The GNU Emacs Manual}. | |
3579 | ||
3580 | To set up the link so that it obeys | |
3581 | @code{mouse-1-click-follows-link}, you must either (1) apply a | |
3582 | @code{follow-link} text or overlay property to the link text, or (2) | |
3583 | bind the @code{follow-link} event to a keymap (which can be a major | |
3584 | mode keymap or a local keymap specified via the @code{keymap} text | |
3585 | property). The value of the @code{follow-link} property, or the | |
3586 | binding for the @code{follow-link} event, acts as a ``condition'' for | |
3587 | the link action. This condition tells Emacs two things: the | |
3588 | circumstances under which a @kbd{Mouse-1} click should be regarded as | |
3589 | occurring ``inside'' the link, and how to compute an ``action code'' | |
3590 | that says what to translate the @kbd{Mouse-1} click into. The link | |
3591 | action condition can be one of the following: | |
b8d4c8d0 GM |
3592 | |
3593 | @table @asis | |
3594 | @item @code{mouse-face} | |
2bad3299 CY |
3595 | If the condition is the symbol @code{mouse-face}, a position is inside |
3596 | a link if there is a non-@code{nil} @code{mouse-face} property at that | |
3597 | position. The action code is always @code{t}. | |
b8d4c8d0 GM |
3598 | |
3599 | For example, here is how Info mode handles @key{Mouse-1}: | |
3600 | ||
3601 | @smallexample | |
3602 | (define-key Info-mode-map [follow-link] 'mouse-face) | |
3603 | @end smallexample | |
3604 | ||
3605 | @item a function | |
2bad3299 CY |
3606 | If the condition is a function, @var{func}, then a position @var{pos} |
3607 | is inside a link if @code{(@var{func} @var{pos})} evaluates to | |
3608 | non-@code{nil}. The value returned by @var{func} serves as the action | |
3609 | code. | |
b8d4c8d0 | 3610 | |
2bad3299 | 3611 | For example, here is how pcvs enables @kbd{Mouse-1} to follow links on |
b8d4c8d0 GM |
3612 | file names only: |
3613 | ||
3614 | @smallexample | |
3615 | (define-key map [follow-link] | |
3616 | (lambda (pos) | |
3617 | (eq (get-char-property pos 'face) 'cvs-filename-face))) | |
3618 | @end smallexample | |
3619 | ||
3620 | @item anything else | |
3621 | If the condition value is anything else, then the position is inside a | |
2bad3299 CY |
3622 | link and the condition itself is the action code. Clearly, you should |
3623 | specify this kind of condition only when applying the condition via a | |
3624 | text or property overlay on the link text (so that it does not apply | |
3625 | to the entire buffer). | |
b8d4c8d0 GM |
3626 | @end table |
3627 | ||
3628 | @noindent | |
2bad3299 | 3629 | The action code tells @kbd{Mouse-1} how to follow the link: |
b8d4c8d0 GM |
3630 | |
3631 | @table @asis | |
3632 | @item a string or vector | |
2bad3299 | 3633 | If the action code is a string or vector, the @kbd{Mouse-1} event is |
b8d4c8d0 | 3634 | translated into the first element of the string or vector; i.e., the |
2bad3299 | 3635 | action of the @kbd{Mouse-1} click is the local or global binding of |
b8d4c8d0 | 3636 | that character or symbol. Thus, if the action code is @code{"foo"}, |
2bad3299 CY |
3637 | @kbd{Mouse-1} translates into @kbd{f}. If it is @code{[foo]}, |
3638 | @kbd{Mouse-1} translates into @key{foo}. | |
b8d4c8d0 GM |
3639 | |
3640 | @item anything else | |
2bad3299 CY |
3641 | For any other non-@code{nil} action code, the @kbd{Mouse-1} event is |
3642 | translated into a @kbd{Mouse-2} event at the same position. | |
b8d4c8d0 GM |
3643 | @end table |
3644 | ||
2bad3299 | 3645 | To define @kbd{Mouse-1} to activate a button defined with |
b8d4c8d0 | 3646 | @code{define-button-type}, give the button a @code{follow-link} |
2bad3299 CY |
3647 | property. The property value should be a link action condition, as |
3648 | described above. @xref{Buttons}. For example, here is how Help mode | |
3649 | handles @kbd{Mouse-1}: | |
b8d4c8d0 GM |
3650 | |
3651 | @smallexample | |
3652 | (define-button-type 'help-xref | |
3653 | 'follow-link t | |
3654 | 'action #'help-button-action) | |
3655 | @end smallexample | |
3656 | ||
2bad3299 CY |
3657 | To define @kbd{Mouse-1} on a widget defined with |
3658 | @code{define-widget}, give the widget a @code{:follow-link} property. | |
3659 | The property value should be a link action condition, as described | |
3660 | above. For example, here is how the @code{link} widget specifies that | |
b8d4c8d0 GM |
3661 | a @key{Mouse-1} click shall be translated to @key{RET}: |
3662 | ||
3663 | @smallexample | |
3664 | (define-widget 'link 'item | |
3665 | "An embedded link." | |
3666 | :button-prefix 'widget-link-prefix | |
3667 | :button-suffix 'widget-link-suffix | |
3668 | :follow-link "\C-m" | |
3669 | :help-echo "Follow the link." | |
3670 | :format "%[%t%]") | |
3671 | @end smallexample | |
3672 | ||
3673 | @defun mouse-on-link-p pos | |
3674 | This function returns non-@code{nil} if position @var{pos} in the | |
3675 | current buffer is on a link. @var{pos} can also be a mouse event | |
db3625ba | 3676 | location, as returned by @code{event-start} (@pxref{Accessing Mouse}). |
b8d4c8d0 GM |
3677 | @end defun |
3678 | ||
3679 | @node Fields | |
3680 | @subsection Defining and Using Fields | |
3681 | @cindex fields | |
3682 | ||
3683 | A field is a range of consecutive characters in the buffer that are | |
3684 | identified by having the same value (comparing with @code{eq}) of the | |
3685 | @code{field} property (either a text-property or an overlay property). | |
3686 | This section describes special functions that are available for | |
3687 | operating on fields. | |
3688 | ||
3689 | You specify a field with a buffer position, @var{pos}. We think of | |
3690 | each field as containing a range of buffer positions, so the position | |
3691 | you specify stands for the field containing that position. | |
3692 | ||
3693 | When the characters before and after @var{pos} are part of the same | |
3694 | field, there is no doubt which field contains @var{pos}: the one those | |
3695 | characters both belong to. When @var{pos} is at a boundary between | |
3696 | fields, which field it belongs to depends on the stickiness of the | |
3697 | @code{field} properties of the two surrounding characters (@pxref{Sticky | |
3698 | Properties}). The field whose property would be inherited by text | |
3699 | inserted at @var{pos} is the field that contains @var{pos}. | |
3700 | ||
3701 | There is an anomalous case where newly inserted text at @var{pos} | |
3702 | would not inherit the @code{field} property from either side. This | |
3703 | happens if the previous character's @code{field} property is not | |
3704 | rear-sticky, and the following character's @code{field} property is not | |
3705 | front-sticky. In this case, @var{pos} belongs to neither the preceding | |
3706 | field nor the following field; the field functions treat it as belonging | |
3707 | to an empty field whose beginning and end are both at @var{pos}. | |
3708 | ||
3709 | In all of these functions, if @var{pos} is omitted or @code{nil}, the | |
3710 | value of point is used by default. If narrowing is in effect, then | |
3711 | @var{pos} should fall within the accessible portion. @xref{Narrowing}. | |
3712 | ||
3713 | @defun field-beginning &optional pos escape-from-edge limit | |
3714 | This function returns the beginning of the field specified by @var{pos}. | |
3715 | ||
3716 | If @var{pos} is at the beginning of its field, and | |
3717 | @var{escape-from-edge} is non-@code{nil}, then the return value is | |
3718 | always the beginning of the preceding field that @emph{ends} at @var{pos}, | |
3719 | regardless of the stickiness of the @code{field} properties around | |
3720 | @var{pos}. | |
3721 | ||
3722 | If @var{limit} is non-@code{nil}, it is a buffer position; if the | |
3723 | beginning of the field is before @var{limit}, then @var{limit} will be | |
3724 | returned instead. | |
3725 | @end defun | |
3726 | ||
3727 | @defun field-end &optional pos escape-from-edge limit | |
3728 | This function returns the end of the field specified by @var{pos}. | |
3729 | ||
3730 | If @var{pos} is at the end of its field, and @var{escape-from-edge} is | |
3731 | non-@code{nil}, then the return value is always the end of the following | |
3732 | field that @emph{begins} at @var{pos}, regardless of the stickiness of | |
3733 | the @code{field} properties around @var{pos}. | |
3734 | ||
3735 | If @var{limit} is non-@code{nil}, it is a buffer position; if the end | |
3736 | of the field is after @var{limit}, then @var{limit} will be returned | |
3737 | instead. | |
3738 | @end defun | |
3739 | ||
3740 | @defun field-string &optional pos | |
3741 | This function returns the contents of the field specified by @var{pos}, | |
3742 | as a string. | |
3743 | @end defun | |
3744 | ||
3745 | @defun field-string-no-properties &optional pos | |
3746 | This function returns the contents of the field specified by @var{pos}, | |
3747 | as a string, discarding text properties. | |
3748 | @end defun | |
3749 | ||
3750 | @defun delete-field &optional pos | |
3751 | This function deletes the text of the field specified by @var{pos}. | |
3752 | @end defun | |
3753 | ||
3754 | @defun constrain-to-field new-pos old-pos &optional escape-from-edge only-in-line inhibit-capture-property | |
3755 | This function ``constrains'' @var{new-pos} to the field that | |
3756 | @var{old-pos} belongs to---in other words, it returns the position | |
3757 | closest to @var{new-pos} that is in the same field as @var{old-pos}. | |
3758 | ||
3759 | If @var{new-pos} is @code{nil}, then @code{constrain-to-field} uses | |
3760 | the value of point instead, and moves point to the resulting position | |
3761 | as well as returning it. | |
3762 | ||
3763 | If @var{old-pos} is at the boundary of two fields, then the acceptable | |
3764 | final positions depend on the argument @var{escape-from-edge}. If | |
3765 | @var{escape-from-edge} is @code{nil}, then @var{new-pos} must be in | |
3766 | the field whose @code{field} property equals what new characters | |
3767 | inserted at @var{old-pos} would inherit. (This depends on the | |
3768 | stickiness of the @code{field} property for the characters before and | |
3769 | after @var{old-pos}.) If @var{escape-from-edge} is non-@code{nil}, | |
3770 | @var{new-pos} can be anywhere in the two adjacent fields. | |
3771 | Additionally, if two fields are separated by another field with the | |
3772 | special value @code{boundary}, then any point within this special | |
3773 | field is also considered to be ``on the boundary.'' | |
3774 | ||
e4920bc9 | 3775 | Commands like @kbd{C-a} with no argument, that normally move backward |
b8d4c8d0 GM |
3776 | to a specific kind of location and stay there once there, probably |
3777 | should specify @code{nil} for @var{escape-from-edge}. Other motion | |
3778 | commands that check fields should probably pass @code{t}. | |
3779 | ||
3780 | If the optional argument @var{only-in-line} is non-@code{nil}, and | |
3781 | constraining @var{new-pos} in the usual way would move it to a different | |
3782 | line, @var{new-pos} is returned unconstrained. This used in commands | |
3783 | that move by line, such as @code{next-line} and | |
3784 | @code{beginning-of-line}, so that they respect field boundaries only in | |
3785 | the case where they can still move to the right line. | |
3786 | ||
3787 | If the optional argument @var{inhibit-capture-property} is | |
3788 | non-@code{nil}, and @var{old-pos} has a non-@code{nil} property of that | |
3789 | name, then any field boundaries are ignored. | |
3790 | ||
3791 | You can cause @code{constrain-to-field} to ignore all field boundaries | |
3792 | (and so never constrain anything) by binding the variable | |
3793 | @code{inhibit-field-text-motion} to a non-@code{nil} value. | |
3794 | @end defun | |
3795 | ||
3796 | @node Not Intervals | |
3797 | @subsection Why Text Properties are not Intervals | |
3798 | @cindex intervals | |
3799 | ||
3800 | Some editors that support adding attributes to text in the buffer do | |
3801 | so by letting the user specify ``intervals'' within the text, and adding | |
3802 | the properties to the intervals. Those editors permit the user or the | |
3803 | programmer to determine where individual intervals start and end. We | |
3804 | deliberately provided a different sort of interface in Emacs Lisp to | |
3805 | avoid certain paradoxical behavior associated with text modification. | |
3806 | ||
3807 | If the actual subdivision into intervals is meaningful, that means you | |
3808 | can distinguish between a buffer that is just one interval with a | |
3809 | certain property, and a buffer containing the same text subdivided into | |
3810 | two intervals, both of which have that property. | |
3811 | ||
3812 | Suppose you take the buffer with just one interval and kill part of | |
3813 | the text. The text remaining in the buffer is one interval, and the | |
3814 | copy in the kill ring (and the undo list) becomes a separate interval. | |
3815 | Then if you yank back the killed text, you get two intervals with the | |
3816 | same properties. Thus, editing does not preserve the distinction | |
3817 | between one interval and two. | |
3818 | ||
3819 | Suppose we ``fix'' this problem by coalescing the two intervals when | |
3820 | the text is inserted. That works fine if the buffer originally was a | |
3821 | single interval. But suppose instead that we have two adjacent | |
3822 | intervals with the same properties, and we kill the text of one interval | |
3823 | and yank it back. The same interval-coalescence feature that rescues | |
3824 | the other case causes trouble in this one: after yanking, we have just | |
3825 | one interval. One again, editing does not preserve the distinction | |
3826 | between one interval and two. | |
3827 | ||
3828 | Insertion of text at the border between intervals also raises | |
3829 | questions that have no satisfactory answer. | |
3830 | ||
3831 | However, it is easy to arrange for editing to behave consistently for | |
3832 | questions of the form, ``What are the properties of this character?'' | |
3833 | So we have decided these are the only questions that make sense; we have | |
3834 | not implemented asking questions about where intervals start or end. | |
3835 | ||
3836 | In practice, you can usually use the text property search functions in | |
3837 | place of explicit interval boundaries. You can think of them as finding | |
3838 | the boundaries of intervals, assuming that intervals are always | |
3839 | coalesced whenever possible. @xref{Property Search}. | |
3840 | ||
3841 | Emacs also provides explicit intervals as a presentation feature; see | |
3842 | @ref{Overlays}. | |
3843 | ||
3844 | @node Substitution | |
3845 | @section Substituting for a Character Code | |
3846 | ||
3847 | The following functions replace characters within a specified region | |
3848 | based on their character codes. | |
3849 | ||
3850 | @defun subst-char-in-region start end old-char new-char &optional noundo | |
3851 | @cindex replace characters | |
3852 | This function replaces all occurrences of the character @var{old-char} | |
3853 | with the character @var{new-char} in the region of the current buffer | |
3854 | defined by @var{start} and @var{end}. | |
3855 | ||
3856 | @cindex undo avoidance | |
3857 | If @var{noundo} is non-@code{nil}, then @code{subst-char-in-region} does | |
3858 | not record the change for undo and does not mark the buffer as modified. | |
3859 | This was useful for controlling the old selective display feature | |
3860 | (@pxref{Selective Display}). | |
3861 | ||
3862 | @code{subst-char-in-region} does not move point and returns | |
3863 | @code{nil}. | |
3864 | ||
3865 | @example | |
3866 | @group | |
3867 | ---------- Buffer: foo ---------- | |
3868 | This is the contents of the buffer before. | |
3869 | ---------- Buffer: foo ---------- | |
3870 | @end group | |
3871 | ||
3872 | @group | |
3873 | (subst-char-in-region 1 20 ?i ?X) | |
3874 | @result{} nil | |
3875 | ||
3876 | ---------- Buffer: foo ---------- | |
3877 | ThXs Xs the contents of the buffer before. | |
3878 | ---------- Buffer: foo ---------- | |
3879 | @end group | |
3880 | @end example | |
3881 | @end defun | |
3882 | ||
106e6894 | 3883 | @deffn Command translate-region start end table |
b8d4c8d0 GM |
3884 | This function applies a translation table to the characters in the |
3885 | buffer between positions @var{start} and @var{end}. | |
3886 | ||
3887 | The translation table @var{table} is a string or a char-table; | |
3888 | @code{(aref @var{table} @var{ochar})} gives the translated character | |
3889 | corresponding to @var{ochar}. If @var{table} is a string, any | |
3890 | characters with codes larger than the length of @var{table} are not | |
3891 | altered by the translation. | |
3892 | ||
3893 | The return value of @code{translate-region} is the number of | |
3894 | characters that were actually changed by the translation. This does | |
3895 | not count characters that were mapped into themselves in the | |
3896 | translation table. | |
106e6894 | 3897 | @end deffn |
b8d4c8d0 GM |
3898 | |
3899 | @node Registers | |
3900 | @section Registers | |
3901 | @cindex registers | |
3902 | ||
3903 | A register is a sort of variable used in Emacs editing that can hold a | |
3904 | variety of different kinds of values. Each register is named by a | |
3905 | single character. All @acronym{ASCII} characters and their meta variants | |
3906 | (but with the exception of @kbd{C-g}) can be used to name registers. | |
3907 | Thus, there are 255 possible registers. A register is designated in | |
3908 | Emacs Lisp by the character that is its name. | |
3909 | ||
3910 | @defvar register-alist | |
3911 | This variable is an alist of elements of the form @code{(@var{name} . | |
3912 | @var{contents})}. Normally, there is one element for each Emacs | |
3913 | register that has been used. | |
3914 | ||
3915 | The object @var{name} is a character (an integer) identifying the | |
3916 | register. | |
3917 | @end defvar | |
3918 | ||
3919 | The @var{contents} of a register can have several possible types: | |
3920 | ||
3921 | @table @asis | |
3922 | @item a number | |
3923 | A number stands for itself. If @code{insert-register} finds a number | |
3924 | in the register, it converts the number to decimal. | |
3925 | ||
3926 | @item a marker | |
3927 | A marker represents a buffer position to jump to. | |
3928 | ||
3929 | @item a string | |
3930 | A string is text saved in the register. | |
3931 | ||
3932 | @item a rectangle | |
3933 | A rectangle is represented by a list of strings. | |
3934 | ||
3935 | @item @code{(@var{window-configuration} @var{position})} | |
3936 | This represents a window configuration to restore in one frame, and a | |
3937 | position to jump to in the current buffer. | |
3938 | ||
3939 | @item @code{(@var{frame-configuration} @var{position})} | |
3940 | This represents a frame configuration to restore, and a position | |
3941 | to jump to in the current buffer. | |
3942 | ||
3943 | @item (file @var{filename}) | |
3944 | This represents a file to visit; jumping to this value visits file | |
3945 | @var{filename}. | |
3946 | ||
3947 | @item (file-query @var{filename} @var{position}) | |
3948 | This represents a file to visit and a position in it; jumping to this | |
3949 | value visits file @var{filename} and goes to buffer position | |
3950 | @var{position}. Restoring this type of position asks the user for | |
3951 | confirmation first. | |
3952 | @end table | |
3953 | ||
3954 | The functions in this section return unpredictable values unless | |
3955 | otherwise stated. | |
3956 | ||
3957 | @defun get-register reg | |
3958 | This function returns the contents of the register | |
3959 | @var{reg}, or @code{nil} if it has no contents. | |
3960 | @end defun | |
3961 | ||
3962 | @defun set-register reg value | |
3963 | This function sets the contents of register @var{reg} to @var{value}. | |
3964 | A register can be set to any value, but the other register functions | |
3965 | expect only certain data types. The return value is @var{value}. | |
3966 | @end defun | |
3967 | ||
3968 | @deffn Command view-register reg | |
3969 | This command displays what is contained in register @var{reg}. | |
3970 | @end deffn | |
3971 | ||
b8d4c8d0 GM |
3972 | @deffn Command insert-register reg &optional beforep |
3973 | This command inserts contents of register @var{reg} into the current | |
3974 | buffer. | |
3975 | ||
3976 | Normally, this command puts point before the inserted text, and the | |
3977 | mark after it. However, if the optional second argument @var{beforep} | |
3978 | is non-@code{nil}, it puts the mark before and point after. | |
3979 | You can pass a non-@code{nil} second argument @var{beforep} to this | |
3980 | function interactively by supplying any prefix argument. | |
3981 | ||
3982 | If the register contains a rectangle, then the rectangle is inserted | |
3983 | with its upper left corner at point. This means that text is inserted | |
3984 | in the current line and underneath it on successive lines. | |
3985 | ||
3986 | If the register contains something other than saved text (a string) or | |
3987 | a rectangle (a list), currently useless things happen. This may be | |
3988 | changed in the future. | |
3989 | @end deffn | |
3990 | ||
b8d4c8d0 GM |
3991 | @node Transposition |
3992 | @section Transposition of Text | |
3993 | ||
3994 | This subroutine is used by the transposition commands. | |
3995 | ||
3996 | @defun transpose-regions start1 end1 start2 end2 &optional leave-markers | |
3997 | This function exchanges two nonoverlapping portions of the buffer. | |
3998 | Arguments @var{start1} and @var{end1} specify the bounds of one portion | |
3999 | and arguments @var{start2} and @var{end2} specify the bounds of the | |
4000 | other portion. | |
4001 | ||
4002 | Normally, @code{transpose-regions} relocates markers with the transposed | |
4003 | text; a marker previously positioned within one of the two transposed | |
4004 | portions moves along with that portion, thus remaining between the same | |
4005 | two characters in their new position. However, if @var{leave-markers} | |
4006 | is non-@code{nil}, @code{transpose-regions} does not do this---it leaves | |
4007 | all markers unrelocated. | |
4008 | @end defun | |
4009 | ||
4010 | @node Base 64 | |
4011 | @section Base 64 Encoding | |
4012 | @cindex base 64 encoding | |
4013 | ||
4014 | Base 64 code is used in email to encode a sequence of 8-bit bytes as | |
4015 | a longer sequence of @acronym{ASCII} graphic characters. It is defined in | |
4016 | Internet RFC@footnote{ | |
4017 | An RFC, an acronym for @dfn{Request for Comments}, is a numbered | |
4018 | Internet informational document describing a standard. RFCs are | |
4019 | usually written by technical experts acting on their own initiative, | |
4020 | and are traditionally written in a pragmatic, experience-driven | |
4021 | manner. | |
4022 | }2045. This section describes the functions for | |
4023 | converting to and from this code. | |
4024 | ||
106e6894 | 4025 | @deffn Command base64-encode-region beg end &optional no-line-break |
b8d4c8d0 GM |
4026 | This function converts the region from @var{beg} to @var{end} into base |
4027 | 64 code. It returns the length of the encoded text. An error is | |
4028 | signaled if a character in the region is multibyte, i.e.@: in a | |
4029 | multibyte buffer the region must contain only characters from the | |
4030 | charsets @code{ascii}, @code{eight-bit-control} and | |
4031 | @code{eight-bit-graphic}. | |
4032 | ||
4033 | Normally, this function inserts newline characters into the encoded | |
4034 | text, to avoid overlong lines. However, if the optional argument | |
4035 | @var{no-line-break} is non-@code{nil}, these newlines are not added, so | |
4036 | the output is just one long line. | |
106e6894 | 4037 | @end deffn |
b8d4c8d0 | 4038 | |
106e6894 | 4039 | @deffn Command base64-encode-string string &optional no-line-break |
b8d4c8d0 GM |
4040 | This function converts the string @var{string} into base 64 code. It |
4041 | returns a string containing the encoded text. As for | |
4042 | @code{base64-encode-region}, an error is signaled if a character in the | |
4043 | string is multibyte. | |
4044 | ||
4045 | Normally, this function inserts newline characters into the encoded | |
4046 | text, to avoid overlong lines. However, if the optional argument | |
4047 | @var{no-line-break} is non-@code{nil}, these newlines are not added, so | |
4048 | the result string is just one long line. | |
106e6894 | 4049 | @end deffn |
b8d4c8d0 GM |
4050 | |
4051 | @defun base64-decode-region beg end | |
4052 | This function converts the region from @var{beg} to @var{end} from base | |
4053 | 64 code into the corresponding decoded text. It returns the length of | |
4054 | the decoded text. | |
4055 | ||
4056 | The decoding functions ignore newline characters in the encoded text. | |
4057 | @end defun | |
4058 | ||
4059 | @defun base64-decode-string string | |
4060 | This function converts the string @var{string} from base 64 code into | |
4061 | the corresponding decoded text. It returns a unibyte string containing the | |
4062 | decoded text. | |
4063 | ||
4064 | The decoding functions ignore newline characters in the encoded text. | |
4065 | @end defun | |
4066 | ||
4067 | @node MD5 Checksum | |
4068 | @section MD5 Checksum | |
4069 | @cindex MD5 checksum | |
4070 | @cindex message digest computation | |
4071 | ||
4072 | MD5 cryptographic checksums, or @dfn{message digests}, are 128-bit | |
4073 | ``fingerprints'' of a document or program. They are used to verify | |
4074 | that you have an exact and unaltered copy of the data. The algorithm | |
4075 | to calculate the MD5 message digest is defined in Internet | |
4076 | RFC@footnote{ | |
4077 | For an explanation of what is an RFC, see the footnote in @ref{Base | |
4078 | 64}. | |
4079 | }1321. This section describes the Emacs facilities for computing | |
4080 | message digests. | |
4081 | ||
4082 | @defun md5 object &optional start end coding-system noerror | |
4083 | This function returns the MD5 message digest of @var{object}, which | |
4084 | should be a buffer or a string. | |
4085 | ||
4086 | The two optional arguments @var{start} and @var{end} are character | |
4087 | positions specifying the portion of @var{object} to compute the | |
4088 | message digest for. If they are @code{nil} or omitted, the digest is | |
4089 | computed for the whole of @var{object}. | |
4090 | ||
4091 | The function @code{md5} does not compute the message digest directly | |
4092 | from the internal Emacs representation of the text (@pxref{Text | |
4093 | Representations}). Instead, it encodes the text using a coding | |
4094 | system, and computes the message digest from the encoded text. The | |
4095 | optional fourth argument @var{coding-system} specifies which coding | |
4096 | system to use for encoding the text. It should be the same coding | |
4097 | system that you used to read the text, or that you used or will use | |
4098 | when saving or sending the text. @xref{Coding Systems}, for more | |
4099 | information about coding systems. | |
4100 | ||
4101 | If @var{coding-system} is @code{nil} or omitted, the default depends | |
4102 | on @var{object}. If @var{object} is a buffer, the default for | |
4103 | @var{coding-system} is whatever coding system would be chosen by | |
4104 | default for writing this text into a file. If @var{object} is a | |
4105 | string, the user's most preferred coding system (@pxref{Recognize | |
4106 | Coding, prefer-coding-system, the description of | |
4107 | @code{prefer-coding-system}, emacs, GNU Emacs Manual}) is used. | |
4108 | ||
4109 | Normally, @code{md5} signals an error if the text can't be encoded | |
4110 | using the specified or chosen coding system. However, if | |
4111 | @var{noerror} is non-@code{nil}, it silently uses @code{raw-text} | |
4112 | coding instead. | |
4113 | @end defun | |
4114 | ||
381408e2 LMI |
4115 | @node Parsing HTML |
4116 | @section Parsing HTML | |
4117 | @cindex parsing html | |
381408e2 | 4118 | |
35a30759 N |
4119 | @defun libxml-parse-html-region start end &optional base-url |
4120 | This function provides HTML parsing via the @code{libxml2} library. | |
4121 | It parses ``real world'' HTML and tries to return a sensible parse tree | |
4122 | regardless. | |
381408e2 | 4123 | |
35a30759 N |
4124 | In addition to @var{start} and @var{end} (specifying the start and end |
4125 | of the region to act on), it takes an optional parameter, | |
4126 | @var{base-url}, which is used to expand relative URLs in the document, | |
4127 | if any. | |
381408e2 LMI |
4128 | |
4129 | Here's an example demonstrating the structure of the parsed data you | |
4130 | get out. Given this HTML document: | |
4131 | ||
4132 | @example | |
4133 | <html><hEad></head><body width=101><div class=thing>Foo<div>Yes | |
4134 | @end example | |
4135 | ||
4136 | You get this parse tree: | |
4137 | ||
4138 | @example | |
4139 | (html | |
4140 | (head) | |
4141 | (body | |
4142 | (:width . "101") | |
4143 | (div | |
4144 | (:class . "thing") | |
4145 | (text . "Foo") | |
4146 | (div | |
4147 | (text . "Yes\n"))))) | |
4148 | @end example | |
4149 | ||
4150 | It's a simple tree structure, where the @code{car} for each node is | |
4151 | the name of the node, and the @code{cdr} is the value, or the list of | |
4152 | values. | |
4153 | ||
4154 | Attributes are coded the same way as child nodes, but with @samp{:} as | |
4155 | the first character. | |
35a30759 N |
4156 | @end defun |
4157 | ||
4158 | @cindex parsing xml | |
4159 | @defun libxml-parse-xml-region start end &optional base-url | |
4160 | ||
4161 | This is much the same as @code{libxml-parse-html-region} above, but | |
4162 | operates on XML instead of HTML, and is correspondingly stricter about | |
4163 | syntax. | |
4164 | @end defun | |
381408e2 | 4165 | |
b8d4c8d0 GM |
4166 | @node Atomic Changes |
4167 | @section Atomic Change Groups | |
4168 | @cindex atomic changes | |
4169 | ||
35a30759 | 4170 | In database terminology, an @dfn{atomic} change is an indivisible |
b8d4c8d0 GM |
4171 | change---it can succeed entirely or it can fail entirely, but it |
4172 | cannot partly succeed. A Lisp program can make a series of changes to | |
4173 | one or several buffers as an @dfn{atomic change group}, meaning that | |
4174 | either the entire series of changes will be installed in their buffers | |
4175 | or, in case of an error, none of them will be. | |
4176 | ||
4177 | To do this for one buffer, the one already current, simply write a | |
4178 | call to @code{atomic-change-group} around the code that makes the | |
4179 | changes, like this: | |
4180 | ||
4181 | @example | |
4182 | (atomic-change-group | |
4183 | (insert foo) | |
4184 | (delete-region x y)) | |
4185 | @end example | |
4186 | ||
4187 | @noindent | |
4188 | If an error (or other nonlocal exit) occurs inside the body of | |
4189 | @code{atomic-change-group}, it unmakes all the changes in that buffer | |
4190 | that were during the execution of the body. This kind of change group | |
4191 | has no effect on any other buffers---any such changes remain. | |
4192 | ||
4193 | If you need something more sophisticated, such as to make changes in | |
4194 | various buffers constitute one atomic group, you must directly call | |
4195 | lower-level functions that @code{atomic-change-group} uses. | |
4196 | ||
4197 | @defun prepare-change-group &optional buffer | |
4198 | This function sets up a change group for buffer @var{buffer}, which | |
4199 | defaults to the current buffer. It returns a ``handle'' that | |
4200 | represents the change group. You must use this handle to activate the | |
4201 | change group and subsequently to finish it. | |
4202 | @end defun | |
4203 | ||
4204 | To use the change group, you must @dfn{activate} it. You must do | |
4205 | this before making any changes in the text of @var{buffer}. | |
4206 | ||
4207 | @defun activate-change-group handle | |
4208 | This function activates the change group that @var{handle} designates. | |
4209 | @end defun | |
4210 | ||
4211 | After you activate the change group, any changes you make in that | |
4212 | buffer become part of it. Once you have made all the desired changes | |
4213 | in the buffer, you must @dfn{finish} the change group. There are two | |
4214 | ways to do this: you can either accept (and finalize) all the changes, | |
4215 | or cancel them all. | |
4216 | ||
4217 | @defun accept-change-group handle | |
4218 | This function accepts all the changes in the change group specified by | |
4219 | @var{handle}, making them final. | |
4220 | @end defun | |
4221 | ||
4222 | @defun cancel-change-group handle | |
4223 | This function cancels and undoes all the changes in the change group | |
4224 | specified by @var{handle}. | |
4225 | @end defun | |
4226 | ||
4227 | Your code should use @code{unwind-protect} to make sure the group is | |
4228 | always finished. The call to @code{activate-change-group} should be | |
4229 | inside the @code{unwind-protect}, in case the user types @kbd{C-g} | |
4230 | just after it runs. (This is one reason why | |
4231 | @code{prepare-change-group} and @code{activate-change-group} are | |
4232 | separate functions, because normally you would call | |
4233 | @code{prepare-change-group} before the start of that | |
4234 | @code{unwind-protect}.) Once you finish the group, don't use the | |
4235 | handle again---in particular, don't try to finish the same group | |
4236 | twice. | |
4237 | ||
4238 | To make a multibuffer change group, call @code{prepare-change-group} | |
4239 | once for each buffer you want to cover, then use @code{nconc} to | |
4240 | combine the returned values, like this: | |
4241 | ||
4242 | @example | |
4243 | (nconc (prepare-change-group buffer-1) | |
4244 | (prepare-change-group buffer-2)) | |
4245 | @end example | |
4246 | ||
4247 | You can then activate the multibuffer change group with a single call | |
4248 | to @code{activate-change-group}, and finish it with a single call to | |
4249 | @code{accept-change-group} or @code{cancel-change-group}. | |
4250 | ||
4251 | Nested use of several change groups for the same buffer works as you | |
4252 | would expect. Non-nested use of change groups for the same buffer | |
4253 | will get Emacs confused, so don't let it happen; the first change | |
4254 | group you start for any given buffer should be the last one finished. | |
4255 | ||
4256 | @node Change Hooks | |
4257 | @section Change Hooks | |
4258 | @cindex change hooks | |
4259 | @cindex hooks for text changes | |
4260 | ||
4261 | These hook variables let you arrange to take notice of all changes in | |
4262 | all buffers (or in a particular buffer, if you make them buffer-local). | |
4263 | See also @ref{Special Properties}, for how to detect changes to specific | |
4264 | parts of the text. | |
4265 | ||
4266 | The functions you use in these hooks should save and restore the match | |
4267 | data if they do anything that uses regular expressions; otherwise, they | |
4268 | will interfere in bizarre ways with the editing operations that call | |
4269 | them. | |
4270 | ||
4271 | @defvar before-change-functions | |
4272 | This variable holds a list of functions to call before any buffer | |
4273 | modification. Each function gets two arguments, the beginning and end | |
4274 | of the region that is about to change, represented as integers. The | |
4275 | buffer that is about to change is always the current buffer. | |
4276 | @end defvar | |
4277 | ||
4278 | @defvar after-change-functions | |
4279 | This variable holds a list of functions to call after any buffer | |
4280 | modification. Each function receives three arguments: the beginning and | |
4281 | end of the region just changed, and the length of the text that existed | |
4282 | before the change. All three arguments are integers. The buffer that's | |
4283 | about to change is always the current buffer. | |
4284 | ||
4285 | The length of the old text is the difference between the buffer positions | |
4286 | before and after that text as it was before the change. As for the | |
4287 | changed text, its length is simply the difference between the first two | |
4288 | arguments. | |
4289 | @end defvar | |
4290 | ||
4291 | Output of messages into the @samp{*Messages*} buffer does not | |
4292 | call these functions. | |
4293 | ||
4294 | @defmac combine-after-change-calls body@dots{} | |
4295 | The macro executes @var{body} normally, but arranges to call the | |
4296 | after-change functions just once for a series of several changes---if | |
4297 | that seems safe. | |
4298 | ||
4299 | If a program makes several text changes in the same area of the buffer, | |
4300 | using the macro @code{combine-after-change-calls} around that part of | |
4301 | the program can make it run considerably faster when after-change hooks | |
4302 | are in use. When the after-change hooks are ultimately called, the | |
4303 | arguments specify a portion of the buffer including all of the changes | |
4304 | made within the @code{combine-after-change-calls} body. | |
4305 | ||
4306 | @strong{Warning:} You must not alter the values of | |
4307 | @code{after-change-functions} within | |
4308 | the body of a @code{combine-after-change-calls} form. | |
4309 | ||
4310 | @strong{Warning:} if the changes you combine occur in widely scattered | |
4311 | parts of the buffer, this will still work, but it is not advisable, | |
4312 | because it may lead to inefficient behavior for some change hook | |
4313 | functions. | |
4314 | @end defmac | |
4315 | ||
4316 | @defvar first-change-hook | |
4317 | This variable is a normal hook that is run whenever a buffer is changed | |
4318 | that was previously in the unmodified state. | |
4319 | @end defvar | |
4320 | ||
4321 | @defvar inhibit-modification-hooks | |
4322 | If this variable is non-@code{nil}, all of the change hooks are | |
4323 | disabled; none of them run. This affects all the hook variables | |
4324 | described above in this section, as well as the hooks attached to | |
4325 | certain special text properties (@pxref{Special Properties}) and overlay | |
4326 | properties (@pxref{Overlay Properties}). | |
4327 | ||
4328 | Also, this variable is bound to non-@code{nil} while running those | |
4329 | same hook variables, so that by default modifying the buffer from | |
4330 | a modification hook does not cause other modification hooks to be run. | |
4331 | If you do want modification hooks to be run in a particular piece of | |
4332 | code that is itself run from a modification hook, then rebind locally | |
4333 | @code{inhibit-modification-hooks} to @code{nil}. | |
4334 | @end defvar |