text.texi 174 KB
Newer Older
Richard M. Stallman's avatar
Richard M. Stallman committed
1 2
@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
3
@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2000, 2001,
4
@c   2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
Richard M. Stallman's avatar
Richard M. Stallman committed
5 6
@c See the file elisp.texi for copying conditions.
@setfilename ../info/text
7
@node Text, Non-ASCII Characters, Markers, Top
Richard M. Stallman's avatar
Richard M. Stallman committed
8 9 10 11
@chapter Text
@cindex text

  This chapter describes the functions that deal with the text in a
12
buffer.  Most examine, insert, or delete text in the current buffer,
13 14 15
often operating at point or on text adjacent to point.  Many are
interactive.  All the functions that change the text provide for undoing
the changes (@pxref{Undo}).
Richard M. Stallman's avatar
Richard M. Stallman committed
16 17 18 19 20 21 22 23 24 25 26 27 28 29

  Many text-related functions operate on a region of text defined by two
buffer positions passed in arguments named @var{start} and @var{end}.
These arguments should be either markers (@pxref{Markers}) or numeric
character positions (@pxref{Positions}).  The order of these arguments
does not matter; it is all right for @var{start} to be the end of the
region and @var{end} the beginning.  For example, @code{(delete-region 1
10)} and @code{(delete-region 10 1)} are equivalent.  An
@code{args-out-of-range} error is signaled if either @var{start} or
@var{end} is outside the accessible portion of the buffer.  In an
interactive call, point and the mark are used for these arguments.

@cindex buffer contents
  Throughout this chapter, ``text'' refers to the characters in the
30 31 32
buffer, together with their properties (when relevant).  Keep in mind
that point is always between two characters, and the cursor appears on
the character after point.
Richard M. Stallman's avatar
Richard M. Stallman committed
33 34 35 36 37 38 39 40 41 42 43 44 45 46

@menu
* Near Point::       Examining text in the vicinity of point.
* Buffer Contents::  Examining text in a general fashion.
* Comparing Text::   Comparing substrings of buffers.
* Insertion::        Adding new text to a buffer.
* Commands for Insertion::  User-level commands to insert text.
* Deletion::         Removing text from a buffer.
* User-Level Deletion::     User-level commands to delete text.
* The Kill Ring::    Where removed text sometimes is saved for later use.
* Undo::             Undoing changes to the text of a buffer.
* Maintaining Undo:: How to enable and disable undo information.
			How to control how much information is kept.
* Filling::          Functions for explicit filling.
Karl Heuer's avatar
Karl Heuer committed
47
* Margins::          How to specify margins for filling commands.
Karl Heuer's avatar
Karl Heuer committed
48
* Adaptive Fill::    Adaptive Fill mode chooses a fill prefix from context.
Richard M. Stallman's avatar
Richard M. Stallman committed
49 50 51 52 53 54 55
* Auto Filling::     How auto-fill mode is implemented to break lines.
* Sorting::          Functions for sorting parts of the buffer.
* Columns::          Computing horizontal positions, and using them.
* Indentation::      Functions to insert or adjust indentation.
* Case Changes::     Case conversion of parts of the buffer.
* Text Properties::  Assigning Lisp property lists to text characters.
* Substitution::     Replacing a given character wherever it appears.
56
* Transposition::    Swapping two portions of a buffer.
Richard M. Stallman's avatar
Richard M. Stallman committed
57 58
* Registers::        How registers are implemented.  Accessing the text or
                       position stored in a register.
59
* Base 64::          Conversion to or from base 64 encoding.
60 61
* MD5 Checksum::     Compute the MD5 "message digest"/"checksum".
* Atomic Changes::   Installing several buffer changes "atomically".
Richard M. Stallman's avatar
Richard M. Stallman committed
62 63 64 65 66 67 68 69 70 71
* Change Hooks::     Supplying functions to be run when text is changed.
@end menu

@node Near Point
@section Examining Text Near Point

  Many functions are provided to look at the characters around point.
Several simple functions are described here.  See also @code{looking-at}
in @ref{Regexp Search}.

72 73 74
In the following four functions, ``beginning'' or ``end'' of buffer
refers to the beginning or end of the accessible portion.

75
@defun char-after &optional position
Richard M. Stallman's avatar
Richard M. Stallman committed
76 77 78
This function returns the character in the current buffer at (i.e.,
immediately after) position @var{position}.  If @var{position} is out of
range for this purpose, either before the beginning of the buffer, or at
79 80
or beyond the end, then the value is @code{nil}.  The default for
@var{position} is point.
Richard M. Stallman's avatar
Richard M. Stallman committed
81 82 83 84 85 86 87 88 89 90 91 92

In the following example, assume that the first character in the
buffer is @samp{@@}:

@example
@group
(char-to-string (char-after 1))
     @result{} "@@"
@end group
@end example
@end defun

93
@defun char-before &optional position
94 95
This function returns the character in the current buffer immediately
before position @var{position}.  If @var{position} is out of range for
96
this purpose, either at or before the beginning of the buffer, or beyond
97 98
the end, then the value is @code{nil}.  The default for
@var{position} is point.
99 100
@end defun

Richard M. Stallman's avatar
Richard M. Stallman committed
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151
@defun following-char
This function returns the character following point in the current
buffer.  This is similar to @code{(char-after (point))}.  However, if
point is at the end of the buffer, then @code{following-char} returns 0.

Remember that point is always between characters, and the terminal
cursor normally appears over the character following point.  Therefore,
the character returned by @code{following-char} is the character the
cursor is over.

In this example, point is between the @samp{a} and the @samp{c}.

@example
@group
---------- Buffer: foo ----------
Gentlemen may cry ``Pea@point{}ce! Peace!,''
but there is no peace.
---------- Buffer: foo ----------
@end group

@group
(char-to-string (preceding-char))
     @result{} "a"
(char-to-string (following-char))
     @result{} "c"
@end group
@end example
@end defun

@defun preceding-char
This function returns the character preceding point in the current
buffer.  See above, under @code{following-char}, for an example.  If
point is at the beginning of the buffer, @code{preceding-char} returns
0.
@end defun

@defun bobp
This function returns @code{t} if point is at the beginning of the
buffer.  If narrowing is in effect, this means the beginning of the
accessible portion of the text.  See also @code{point-min} in
@ref{Point}.
@end defun

@defun eobp
This function returns @code{t} if point is at the end of the buffer.
If narrowing is in effect, this means the end of accessible portion of
the text.  See also @code{point-max} in @xref{Point}.
@end defun

@defun bolp
This function returns @code{t} if point is at the beginning of a line.
152
@xref{Text Lines}.  The beginning of the buffer (or of its accessible
153
portion) always counts as the beginning of a line.
Richard M. Stallman's avatar
Richard M. Stallman committed
154 155 156 157 158 159 160 161 162 163 164
@end defun

@defun eolp
This function returns @code{t} if point is at the end of a line.  The
end of the buffer (or of its accessible portion) is always considered
the end of a line.
@end defun

@node Buffer Contents
@section Examining Buffer Contents

Richard M. Stallman's avatar
Richard M. Stallman committed
165
  This section describes functions that allow a Lisp program to
Richard M. Stallman's avatar
Richard M. Stallman committed
166 167 168 169 170 171 172 173 174 175 176 177 178
convert any portion of the text in the buffer into a string.

@defun buffer-substring start end
This function returns a string containing a copy of the text of the
region defined by positions @var{start} and @var{end} in the current
buffer.  If the arguments are not positions in the accessible portion of
the buffer, @code{buffer-substring} signals an @code{args-out-of-range}
error.

It is not necessary for @var{start} to be less than @var{end}; the
arguments can be given in either order.  But most often the smaller
argument is written first.

179
Here's an example which assumes Font-Lock mode is not enabled:
Karl Heuer's avatar
Karl Heuer committed
180

Richard M. Stallman's avatar
Richard M. Stallman committed
181 182 183 184 185 186 187 188 189 190
@example
@group
---------- Buffer: foo ----------
This is the contents of buffer foo

---------- Buffer: foo ----------
@end group

@group
(buffer-substring 1 10)
191
     @result{} "This is t"
Richard M. Stallman's avatar
Richard M. Stallman committed
192 193 194
@end group
@group
(buffer-substring (point-max) 10)
195
     @result{} "he contents of buffer foo\n"
Richard M. Stallman's avatar
Richard M. Stallman committed
196 197
@end group
@end example
198 199 200 201 202 203 204 205 206 207 208 209 210 211 212

If the text being copied has any text properties, these are copied into
the string along with the characters they belong to.  @xref{Text
Properties}.  However, overlays (@pxref{Overlays}) in the buffer and
their properties are ignored, not copied.

For example, if Font-Lock mode is enabled, you might get results like
these:

@example
@group
(buffer-substring 1 10)
     @result{} #("This is t" 0 1 (fontified t) 1 9 (fontified t))
@end group
@end example
Richard M. Stallman's avatar
Richard M. Stallman committed
213 214
@end defun

215
@defun buffer-substring-no-properties start end
Karl Heuer's avatar
Karl Heuer committed
216 217 218 219
This is like @code{buffer-substring}, except that it does not copy text
properties, just the characters themselves.  @xref{Text Properties}.
@end defun

220
@defun filter-buffer-substring start end &optional delete noprops
221 222 223 224 225 226 227 228 229 230 231
This function passes the buffer text between @var{start} and @var{end}
through the filter functions specified by the variable
@code{buffer-substring-filters}, and returns the value from the last
filter function.  If @code{buffer-substring-filters} is @code{nil},
the value is the unaltered text from the buffer, what
@code{buffer-substring} would return.

If @var{delete} is non-@code{nil}, this function deletes the text
between @var{start} and @var{end} after copying it, like
@code{delete-and-extract-region}.

232 233 234 235 236 237
If @var{noprops} is non-@code{nil}, the final string returned does not
include text properties, while the string passed through the filters
still includes text properties from the buffer text.

Lisp code should use this function instead of @code{buffer-substring},
@code{buffer-substring-no-properties},
238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259
or @code{delete-and-extract-region} when copying into user-accessible
data structures such as the kill-ring, X clipboard, and registers.
Major and minor modes can add functions to
@code{buffer-substring-filters} to alter such text as it is copied out
of the buffer.
@end defun

@defvar buffer-substring-filters
This variable should be a list of functions that accept a single
argument, a string, and return a string.
@code{filter-buffer-substring} passes the buffer substring to the
first function in this list, and the return value of each function is
passed to the next function.  The return value of the last function is
used as the return value of @code{filter-buffer-substring}.

As a special convention, point is set to the start of the buffer text
being operated on (i.e., the @var{start} argument for
@code{filter-buffer-substring}) before these functions are called.

If this variable is @code{nil}, no filtering is performed.
@end defvar

Richard M. Stallman's avatar
Richard M. Stallman committed
260
@defun buffer-string
261
This function returns the contents of the entire accessible portion of
262 263 264 265 266
the current buffer as a string.  It is equivalent to

@example
(buffer-substring (point-min) (point-max))
@end example
Richard M. Stallman's avatar
Richard M. Stallman committed
267 268 269 270 271 272 273 274 275

@example
@group
---------- Buffer: foo ----------
This is the contents of buffer foo

---------- Buffer: foo ----------

(buffer-string)
276
     @result{} "This is the contents of buffer foo\n"
Richard M. Stallman's avatar
Richard M. Stallman committed
277 278 279 280
@end group
@end example
@end defun

281 282 283 284
@defun current-word &optional strict really-word
This function returns the symbol (or word) at or near point, as a string.
The return value includes no text properties.

285 286 287
If the optional argument @var{really-word} is non-@code{nil}, it finds a
word; otherwise, it finds a symbol (which includes both word
characters and symbol constituent characters).
288 289 290 291 292 293 294

If the optional argument @var{strict} is non-@code{nil}, then point
must be in or next to the symbol or word---if no symbol or word is
there, the function returns @code{nil}.  Otherwise, a nearby symbol or
word on the same line is acceptable.
@end defun

295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317
@defun thing-at-point thing
Return the @var{thing} around or next to point, as a string.

The argument @var{thing} is a symbol which specifies a kind of syntactic
entity.  Possibilities include @code{symbol}, @code{list}, @code{sexp},
@code{defun}, @code{filename}, @code{url}, @code{word}, @code{sentence},
@code{whitespace}, @code{line}, @code{page}, and others.

@example
---------- Buffer: foo ----------
Gentlemen may cry ``Pea@point{}ce! Peace!,''
but there is no peace.
---------- Buffer: foo ----------

(thing-at-point 'word)
     @result{} "Peace"
(thing-at-point 'line)
     @result{} "Gentlemen may cry ``Peace! Peace!,''\n"
(thing-at-point 'whitespace)
     @result{} nil
@end example
@end defun

Richard M. Stallman's avatar
Richard M. Stallman committed
318 319 320 321 322 323 324 325 326 327
@node Comparing Text
@section Comparing Text
@cindex comparing buffer text

  This function lets you compare portions of the text in a buffer, without
copying them into strings first.

@defun compare-buffer-substrings buffer1 start1 end1 buffer2 start2 end2
This function lets you compare two substrings of the same buffer or two
different buffers.  The first three arguments specify one substring,
328 329 330 331
giving a buffer (or a buffer name) and two positions within the
buffer.  The last three arguments specify the other substring in the
same way.  You can use @code{nil} for @var{buffer1}, @var{buffer2}, or
both to stand for the current buffer.
Richard M. Stallman's avatar
Richard M. Stallman committed
332 333 334 335 336 337 338

The value is negative if the first substring is less, positive if the
first is greater, and zero if they are equal.  The absolute value of
the result is one plus the index of the first differing characters
within the substrings.

This function ignores case when comparing characters
Karl Heuer's avatar
Karl Heuer committed
339 340
if @code{case-fold-search} is non-@code{nil}.  It always ignores
text properties.
Richard M. Stallman's avatar
Richard M. Stallman committed
341 342 343 344 345 346 347

Suppose the current buffer contains the text @samp{foobarbar
haha!rara!}; then in this example the two substrings are @samp{rbar }
and @samp{rara!}.  The value is 2 because the first substring is greater
at the second character.

@example
348
(compare-buffer-substrings nil 6 11 nil 16 21)
Richard M. Stallman's avatar
Richard M. Stallman committed
349 350 351 352 353
     @result{} 2
@end example
@end defun

@node Insertion
Karl Heuer's avatar
Karl Heuer committed
354
@section Inserting Text
Richard M. Stallman's avatar
Richard M. Stallman committed
355 356 357
@cindex insertion of text
@cindex text insertion

358 359
@cindex insertion before point
@cindex before point, insertion
Richard M. Stallman's avatar
Richard M. Stallman committed
360 361
  @dfn{Insertion} means adding new text to a buffer.  The inserted text
goes at point---between the character before point and the character
362 363 364
after point.  Some insertion functions leave point before the inserted
text, while other functions leave it after.  We call the former
insertion @dfn{after point} and the latter insertion @dfn{before point}.
Richard M. Stallman's avatar
Richard M. Stallman committed
365 366 367 368

  Insertion relocates markers that point at positions after the
insertion point, so that they stay with the surrounding text
(@pxref{Markers}).  When a marker points at the place of insertion,
369 370 371 372 373
insertion may or may not relocate the marker, depending on the marker's
insertion type (@pxref{Marker Insertion Types}).  Certain special
functions such as @code{insert-before-markers} relocate all such markers
to point after the inserted text, regardless of the markers' insertion
type.
Richard M. Stallman's avatar
Richard M. Stallman committed
374 375

  Insertion functions signal an error if the current buffer is
376
read-only or if they insert within read-only text.
Richard M. Stallman's avatar
Richard M. Stallman committed
377

Karl Heuer's avatar
Karl Heuer committed
378 379 380 381 382 383
  These functions copy text characters from strings and buffers along
with their properties.  The inserted characters have exactly the same
properties as the characters they were copied from.  By contrast,
characters specified as separate arguments, not part of a string or
buffer, inherit their text properties from the neighboring text.

384 385 386 387 388 389 390
  The insertion functions convert text from unibyte to multibyte in
order to insert in a multibyte buffer, and vice versa---if the text
comes from a string or from a buffer.  However, they do not convert
unibyte character codes 128 through 255 to multibyte characters, not
even if the current buffer is a multibyte buffer.  @xref{Converting
Representations}.

Richard M. Stallman's avatar
Richard M. Stallman committed
391 392
@defun insert &rest args
This function inserts the strings and/or characters @var{args} into the
393 394 395
current buffer, at point, moving point forward.  In other words, it
inserts the text before point.  An error is signaled unless all
@var{args} are either strings or characters.  The value is @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
396 397 398 399 400 401 402 403 404 405
@end defun

@defun insert-before-markers &rest args
This function inserts the strings and/or characters @var{args} into the
current buffer, at point, moving point forward.  An error is signaled
unless all @var{args} are either strings or characters.  The value is
@code{nil}.

This function is unlike the other insertion functions in that it
relocates markers initially pointing at the insertion point, to point
Richard M. Stallman's avatar
Richard M. Stallman committed
406 407 408 409
after the inserted text.  If an overlay begins at the insertion point,
the inserted text falls outside the overlay; if a nonempty overlay
ends at the insertion point, the inserted text falls inside that
overlay.
Richard M. Stallman's avatar
Richard M. Stallman committed
410 411
@end defun

412
@defun insert-char character count &optional inherit
Richard M. Stallman's avatar
Richard M. Stallman committed
413
This function inserts @var{count} instances of @var{character} into the
414 415
current buffer before point.  The argument @var{count} should be an
integer, and @var{character} must be a character.  The value is @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
416

417 418 419 420
This function does not convert unibyte character codes 128 through 255
to multibyte characters, not even if the current buffer is a multibyte
buffer.  @xref{Converting Representations}.

Richard M. Stallman's avatar
Richard M. Stallman committed
421 422 423
If @var{inherit} is non-@code{nil}, then the inserted characters inherit
sticky text properties from the two characters before and after the
insertion point.  @xref{Sticky Properties}.
Richard M. Stallman's avatar
Richard M. Stallman committed
424 425 426 427 428
@end defun

@defun insert-buffer-substring from-buffer-or-name &optional start end
This function inserts a portion of buffer @var{from-buffer-or-name}
(which must already exist) into the current buffer before point.  The
429
text inserted is the region between @var{start} and @var{end}.  (These
Richard M. Stallman's avatar
Richard M. Stallman committed
430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447
arguments default to the beginning and end of the accessible portion of
that buffer.)  This function returns @code{nil}.

In this example, the form is executed with buffer @samp{bar} as the
current buffer.  We assume that buffer @samp{bar} is initially empty.

@example
@group
---------- Buffer: foo ----------
We hold these truths to be self-evident, that all
---------- Buffer: foo ----------
@end group

@group
(insert-buffer-substring "foo" 1 20)
     @result{} nil

---------- Buffer: bar ----------
448
We hold these truth@point{}
Richard M. Stallman's avatar
Richard M. Stallman committed
449 450 451
---------- Buffer: bar ----------
@end group
@end example
452 453 454 455 456
@end defun

@defun insert-buffer-substring-no-properties from-buffer-or-name &optional start end
This is like @code{insert-buffer-substring} except that it does not
copy any text properties.
Richard M. Stallman's avatar
Richard M. Stallman committed
457 458 459
@end defun

  @xref{Sticky Properties}, for other insertion functions that inherit
460
text properties from the nearby text in addition to inserting it.
Richard M. Stallman's avatar
Richard M. Stallman committed
461 462
Whitespace inserted by indentation functions also inherits text
properties.
Richard M. Stallman's avatar
Richard M. Stallman committed
463 464 465 466 467 468 469 470 471

@node Commands for Insertion
@section User-Level Insertion Commands

  This section describes higher-level commands for inserting text,
commands intended primarily for the user but useful also in Lisp
programs.

@deffn Command insert-buffer from-buffer-or-name
472 473 474 475
This command inserts the entire accessible contents of
@var{from-buffer-or-name} (which must exist) into the current buffer
after point.  It leaves the mark after the inserted text.  The value
is @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
476 477 478 479 480
@end deffn

@deffn Command self-insert-command count
@cindex character insertion
@cindex self-insertion
481 482 483 484 485
This command inserts the last character typed; it does so @var{count}
times, before point, and returns @code{nil}.  Most printing characters
are bound to this command.  In routine use, @code{self-insert-command}
is the most frequently called function in Emacs, but programs rarely use
it except to install it on a keymap.
Richard M. Stallman's avatar
Richard M. Stallman committed
486 487 488

In an interactive call, @var{count} is the numeric prefix argument.

489 490 491
Self-insertion translates the input character through
@code{translation-table-for-input}.  @xref{Translation of Characters}.

Karl Heuer's avatar
Karl Heuer committed
492
This command calls @code{auto-fill-function} whenever that is
Dave Love's avatar
Dave Love committed
493 494
non-@code{nil} and the character inserted is in the table
@code{auto-fill-chars} (@pxref{Auto Filling}).
Richard M. Stallman's avatar
Richard M. Stallman committed
495 496

@c Cross refs reworded to prevent overfull hbox.  --rjc 15mar92
Karl Heuer's avatar
Karl Heuer committed
497
This command performs abbrev expansion if Abbrev mode is enabled and
Richard M. Stallman's avatar
Richard M. Stallman committed
498
the inserted character does not have word-constituent
499 500 501
syntax. (@xref{Abbrevs}, and @ref{Syntax Class Table}.)  It is also
responsible for calling @code{blink-paren-function} when the inserted
character has close parenthesis syntax (@pxref{Blinking}).
Phillip Rulon's avatar
Phillip Rulon committed
502 503 504 505

Do not try substituting your own definition of
@code{self-insert-command} for the standard one.  The editor command
loop handles this function specially.
Richard M. Stallman's avatar
Richard M. Stallman committed
506 507
@end deffn

508
@deffn Command newline &optional number-of-newlines
Richard M. Stallman's avatar
Richard M. Stallman committed
509 510 511 512 513
This command inserts newlines into the current buffer before point.
If @var{number-of-newlines} is supplied, that many newline characters
are inserted.

@cindex newline and Auto Fill mode
514 515 516 517 518 519 520
This function calls @code{auto-fill-function} if the current column
number is greater than the value of @code{fill-column} and
@var{number-of-newlines} is @code{nil}.  Typically what
@code{auto-fill-function} does is insert a newline; thus, the overall
result in this case is to insert two newlines at different places: one
at point, and another earlier in the line.  @code{newline} does not
auto-fill if @var{number-of-newlines} is non-@code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
521

Karl Heuer's avatar
Karl Heuer committed
522 523 524
This command indents to the left margin if that is not zero.
@xref{Margins}.

Richard M. Stallman's avatar
Richard M. Stallman committed
525 526 527 528 529 530
The value returned is @code{nil}.  In an interactive call, @var{count}
is the numeric prefix argument.
@end deffn

@deffn Command split-line
This command splits the current line, moving the portion of the line
531
after point down vertically so that it is on the next line directly
Richard M. Stallman's avatar
Richard M. Stallman committed
532 533 534 535 536 537 538 539
below where it was before.  Whitespace is inserted as needed at the
beginning of the lower line, using the @code{indent-to} function.
@code{split-line} returns the position of point.

Programs hardly ever use this function.
@end deffn

@defvar overwrite-mode
540 541 542 543 544 545
This variable controls whether overwrite mode is in effect.  The value
should be @code{overwrite-mode-textual}, @code{overwrite-mode-binary},
or @code{nil}.  @code{overwrite-mode-textual} specifies textual
overwrite mode (treats newlines and tabs specially), and
@code{overwrite-mode-binary} specifies binary overwrite mode (treats
newlines and tabs like any other characters).
Richard M. Stallman's avatar
Richard M. Stallman committed
546 547 548
@end defvar

@node Deletion
Karl Heuer's avatar
Karl Heuer committed
549
@section Deleting Text
Richard M. Stallman's avatar
Richard M. Stallman committed
550 551 552 553 554

@cindex deletion vs killing
  Deletion means removing part of the text in a buffer, without saving
it in the kill ring (@pxref{The Kill Ring}).  Deleted text can't be
yanked, but can be reinserted using the undo mechanism (@pxref{Undo}).
555 556
Some deletion functions do save text in the kill ring in some special
cases.
Richard M. Stallman's avatar
Richard M. Stallman committed
557

558
  All of the deletion functions operate on the current buffer.
Richard M. Stallman's avatar
Richard M. Stallman committed
559

560
@deffn Command erase-buffer
561 562
This function deletes the entire text of the current buffer
(@emph{not} just the accessible portion), leaving it
Richard M. Stallman's avatar
Richard M. Stallman committed
563
empty.  If the buffer is read-only, it signals a @code{buffer-read-only}
564 565 566
error; if some of the text in it is read-only, it signals a
@code{text-read-only} error.  Otherwise, it deletes the text without
asking for any confirmation.  It returns @code{nil}.
567

Richard M. Stallman's avatar
Richard M. Stallman committed
568
Normally, deleting a large amount of text from a buffer inhibits further
569
auto-saving of that buffer ``because it has shrunk.''  However,
Richard M. Stallman's avatar
Richard M. Stallman committed
570 571 572
@code{erase-buffer} does not do this, the idea being that the future
text is not really related to the former text, and its size should not
be compared with that of the former text.
573
@end deffn
Richard M. Stallman's avatar
Richard M. Stallman committed
574 575

@deffn Command delete-region start end
576 577 578
This command deletes the text between positions @var{start} and
@var{end} in the current buffer, and returns @code{nil}.  If point was
inside the deleted region, its value afterward is @var{start}.
579
Otherwise, point relocates with the surrounding text, as markers do.
Richard M. Stallman's avatar
Richard M. Stallman committed
580 581
@end deffn

582 583 584 585 586 587 588 589 590 591
@defun delete-and-extract-region start end
This function deletes the text between positions @var{start} and
@var{end} in the current buffer, and returns a string containing the
text just deleted.

If point was inside the deleted region, its value afterward is
@var{start}.  Otherwise, point relocates with the surrounding text, as
markers do.
@end defun

Richard M. Stallman's avatar
Richard M. Stallman committed
592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642
@deffn Command delete-char count &optional killp
This command deletes @var{count} characters directly after point, or
before point if @var{count} is negative.  If @var{killp} is
non-@code{nil}, then it saves the deleted characters in the kill ring.

In an interactive call, @var{count} is the numeric prefix argument, and
@var{killp} is the unprocessed prefix argument.  Therefore, if a prefix
argument is supplied, the text is saved in the kill ring.  If no prefix
argument is supplied, then one character is deleted, but not saved in
the kill ring.

The value returned is always @code{nil}.
@end deffn

@deffn Command delete-backward-char count &optional killp
@cindex delete previous char
This command deletes @var{count} characters directly before point, or
after point if @var{count} is negative.  If @var{killp} is
non-@code{nil}, then it saves the deleted characters in the kill ring.

In an interactive call, @var{count} is the numeric prefix argument, and
@var{killp} is the unprocessed prefix argument.  Therefore, if a prefix
argument is supplied, the text is saved in the kill ring.  If no prefix
argument is supplied, then one character is deleted, but not saved in
the kill ring.

The value returned is always @code{nil}.
@end deffn

@deffn Command backward-delete-char-untabify count &optional killp
@cindex tab deletion
This command deletes @var{count} characters backward, changing tabs
into spaces.  When the next character to be deleted is a tab, it is
first replaced with the proper number of spaces to preserve alignment
and then one of those spaces is deleted instead of the tab.  If
@var{killp} is non-@code{nil}, then the command saves the deleted
characters in the kill ring.

Conversion of tabs to spaces happens only if @var{count} is positive.
If it is negative, exactly @minus{}@var{count} characters after point
are deleted.

In an interactive call, @var{count} is the numeric prefix argument, and
@var{killp} is the unprocessed prefix argument.  Therefore, if a prefix
argument is supplied, the text is saved in the kill ring.  If no prefix
argument is supplied, then one character is deleted, but not saved in
the kill ring.

The value returned is always @code{nil}.
@end deffn

643 644 645 646
@defopt backward-delete-char-untabify-method
This option specifies how @code{backward-delete-char-untabify} should
deal with whitespace.  Possible values include @code{untabify}, the
default, meaning convert a tab to many spaces and delete one;
647 648 649
@code{hungry}, meaning delete all tabs and spaces before point with
one command; @code{all} meaning delete all tabs, spaces and newlines
before point, and @code{nil}, meaning do nothing special for
650 651 652
whitespace characters.
@end defopt

Richard M. Stallman's avatar
Richard M. Stallman committed
653 654 655 656 657 658 659
@node User-Level Deletion
@section User-Level Deletion Commands

  This section describes higher-level commands for deleting text,
commands intended primarily for the user but useful also in Lisp
programs.

660
@deffn Command delete-horizontal-space &optional backward-only
Richard M. Stallman's avatar
Richard M. Stallman committed
661 662 663 664
@cindex deleting whitespace
This function deletes all spaces and tabs around point.  It returns
@code{nil}.

665 666 667
If @var{backward-only} is non-@code{nil}, the function deletes
spaces and tabs before point, but not after point.

Richard M. Stallman's avatar
Richard M. Stallman committed
668 669
In the following examples, we call @code{delete-horizontal-space} four
times, once on each line, with point between the second and third
670
characters on the line each time.
Richard M. Stallman's avatar
Richard M. Stallman committed
671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695

@example
@group
---------- Buffer: foo ----------
I @point{}thought
I @point{}     thought
We@point{} thought
Yo@point{}u thought
---------- Buffer: foo ----------
@end group

@group
(delete-horizontal-space)   ; @r{Four times.}
     @result{} nil

---------- Buffer: foo ----------
Ithought
Ithought
Wethought
You thought
---------- Buffer: foo ----------
@end group
@end example
@end deffn

696
@deffn Command delete-indentation &optional join-following-p
Richard M. Stallman's avatar
Richard M. Stallman committed
697 698 699 700
This function joins the line point is on to the previous line, deleting
any whitespace at the join and in some cases replacing it with one
space.  If @var{join-following-p} is non-@code{nil},
@code{delete-indentation} joins this line to the following line
701
instead.  The function returns @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
702 703 704

If there is a fill prefix, and the second of the lines being joined
starts with the prefix, then @code{delete-indentation} deletes the
Karl Heuer's avatar
Karl Heuer committed
705
fill prefix before joining the lines.  @xref{Margins}.
Richard M. Stallman's avatar
Richard M. Stallman committed
706 707 708 709 710 711

In the example below, point is located on the line starting
@samp{events}, and it makes no difference if there are trailing spaces
in the preceding line.

@smallexample
712
@group
Richard M. Stallman's avatar
Richard M. Stallman committed
713 714 715 716
---------- Buffer: foo ----------
When in the course of human
@point{}    events, it becomes necessary
---------- Buffer: foo ----------
717
@end group
Richard M. Stallman's avatar
Richard M. Stallman committed
718 719 720 721

(delete-indentation)
     @result{} nil

722
@group
Richard M. Stallman's avatar
Richard M. Stallman committed
723 724 725
---------- Buffer: foo ----------
When in the course of human@point{} events, it becomes necessary
---------- Buffer: foo ----------
726
@end group
Richard M. Stallman's avatar
Richard M. Stallman committed
727 728 729 730 731 732
@end smallexample

After the lines are joined, the function @code{fixup-whitespace} is
responsible for deciding whether to leave a space at the junction.
@end deffn

733 734 735 736
@deffn Command fixup-whitespace
This function replaces all the horizontal whitespace surrounding point
with either one space or no space, according to the context.  It
returns @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
737 738 739 740 741 742 743 744

At the beginning or end of a line, the appropriate amount of space is
none.  Before a character with close parenthesis syntax, or after a
character with open parenthesis or expression-prefix syntax, no space is
also appropriate.  Otherwise, one space is appropriate.  @xref{Syntax
Class Table}.

In the example below, @code{fixup-whitespace} is called the first time
745 746
with point before the word @samp{spaces} in the first line.  For the
second invocation, point is directly after the @samp{(}.
Richard M. Stallman's avatar
Richard M. Stallman committed
747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769

@smallexample
@group
---------- Buffer: foo ----------
This has too many     @point{}spaces
This has too many spaces at the start of (@point{}   this list)
---------- Buffer: foo ----------
@end group

@group
(fixup-whitespace)
     @result{} nil
(fixup-whitespace)
     @result{} nil
@end group

@group
---------- Buffer: foo ----------
This has too many spaces
This has too many spaces at the start of (this list)
---------- Buffer: foo ----------
@end group
@end smallexample
770
@end deffn
Richard M. Stallman's avatar
Richard M. Stallman committed
771

772
@deffn Command just-one-space &optional n
Richard M. Stallman's avatar
Richard M. Stallman committed
773 774
@comment !!SourceFile simple.el
This command replaces any spaces and tabs around point with a single
775 776
space, or @var{n} spaces if @var{n} is specified.  It returns
@code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
777 778 779 780 781 782 783
@end deffn

@deffn Command delete-blank-lines
This function deletes blank lines surrounding point.  If point is on a
blank line with one or more blank lines before or after it, then all but
one of them are deleted.  If point is on an isolated blank line, then it
is deleted.  If point is on a nonblank line, the command deletes all
784
blank lines immediately following it.
Richard M. Stallman's avatar
Richard M. Stallman committed
785 786 787 788 789 790 791 792 793 794

A blank line is defined as a line containing only tabs and spaces.

@code{delete-blank-lines} returns @code{nil}.
@end deffn

@node The Kill Ring
@section The Kill Ring
@cindex kill ring

795
  @dfn{Kill functions} delete text like the deletion functions, but save
Richard M. Stallman's avatar
Richard M. Stallman committed
796 797 798 799 800 801 802 803 804
it so that the user can reinsert it by @dfn{yanking}.  Most of these
functions have @samp{kill-} in their name.  By contrast, the functions
whose names start with @samp{delete-} normally do not save text for
yanking (though they can still be undone); these are ``deletion''
functions.

  Most of the kill commands are primarily for interactive use, and are
not described here.  What we do describe are the functions provided for
use in writing such commands.  You can use these functions to write
805
commands for killing text.  When you need to delete text for internal
Richard M. Stallman's avatar
Richard M. Stallman committed
806 807 808 809 810
purposes within a Lisp function, you should normally use deletion
functions, so as not to disturb the kill ring contents.
@xref{Deletion}.

  Killed text is saved for later yanking in the @dfn{kill ring}.  This
811 812 813 814 815 816
is a list that holds a number of recent kills, not just the last text
kill.  We call this a ``ring'' because yanking treats it as having
elements in a cyclic order.  The list is kept in the variable
@code{kill-ring}, and can be operated on with the usual functions for
lists; there are also specialized functions, described in this section,
that treat it as a ring.
Richard M. Stallman's avatar
Richard M. Stallman committed
817 818

  Some people think this use of the word ``kill'' is unfortunate, since
819
it refers to operations that specifically @emph{do not} destroy the
820
entities ``killed.''  This is in sharp contrast to ordinary life, in
Richard M. Stallman's avatar
Richard M. Stallman committed
821 822 823 824 825 826 827 828 829
which death is permanent and ``killed'' entities do not come back to
life.  Therefore, other metaphors have been proposed.  For example, the
term ``cut ring'' makes sense to people who, in pre-computer days, used
scissors and paste to cut up and rearrange manuscripts.  However, it
would be difficult to change the terminology now.

@menu
* Kill Ring Concepts::     What text looks like in the kill ring.
* Kill Functions::         Functions that kill text.
830
* Yanking::                How yanking is done.
Richard M. Stallman's avatar
Richard M. Stallman committed
831
* Yank Commands::          Commands that access the kill ring.
832
* Low-Level Kill Ring::	   Functions and variables for kill ring access.
833
* Internals of Kill Ring:: Variables that hold kill ring data.
Richard M. Stallman's avatar
Richard M. Stallman committed
834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852
@end menu

@node Kill Ring Concepts
@comment  node-name,  next,  previous,  up
@subsection Kill Ring Concepts

  The kill ring records killed text as strings in a list, most recent
first.  A short kill ring, for example, might look like this:

@example
("some text" "a different piece of text" "even older text")
@end example

@noindent
When the list reaches @code{kill-ring-max} entries in length, adding a
new entry automatically deletes the last entry.

  When kill commands are interwoven with other commands, each kill
command makes a new entry in the kill ring.  Multiple kill commands in
853
succession build up a single kill ring entry, which would be yanked as a
854 855
unit; the second and subsequent consecutive kill commands add text to
the entry made by the first one.
Richard M. Stallman's avatar
Richard M. Stallman committed
856 857 858 859 860 861 862 863 864 865 866 867 868 869 870

  For yanking, one entry in the kill ring is designated the ``front'' of
the ring.  Some yank commands ``rotate'' the ring by designating a
different element as the ``front.''  But this virtual rotation doesn't
change the list itself---the most recent entry always comes first in the
list.

@node Kill Functions
@comment  node-name,  next,  previous,  up
@subsection Functions for Killing

  @code{kill-region} is the usual subroutine for killing text.  Any
command that calls this function is a ``kill command'' (and should
probably have @samp{kill} in its name).  @code{kill-region} puts the
newly killed text in a new element at the beginning of the kill ring or
871 872
adds it to the most recent element.  It determines automatically (using
@code{last-command}) whether the previous command was a kill command,
873
and if so appends the killed text to the most recent entry.
Richard M. Stallman's avatar
Richard M. Stallman committed
874

875
@deffn Command kill-region start end &optional yank-handler
Richard M. Stallman's avatar
Richard M. Stallman committed
876
This function kills the text in the region defined by @var{start} and
Karl Heuer's avatar
Karl Heuer committed
877 878
@var{end}.  The text is deleted but saved in the kill ring, along with
its text properties.  The value is always @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
879 880 881 882 883

In an interactive call, @var{start} and @var{end} are point and
the mark.

@c Emacs 19 feature
884 885 886 887
If the buffer or text is read-only, @code{kill-region} modifies the kill
ring just the same, then signals an error without modifying the buffer.
This is convenient because it lets the user use a series of kill
commands to copy text from a read-only buffer into the kill ring.
888 889

If @var{yank-handler} is non-@code{nil}, this puts that value onto
890 891 892 893
the string of killed text, as a @code{yank-handler} text property.
@xref{Yanking}.  Note that if @var{yank-handler} is @code{nil}, any
@code{yank-handler} properties present on the killed text are copied
onto the kill ring, like other text properties.
Richard M. Stallman's avatar
Richard M. Stallman committed
894 895
@end deffn

896
@defopt kill-read-only-ok
897 898 899
If this option is non-@code{nil}, @code{kill-region} does not signal an
error if the buffer or text is read-only.  Instead, it simply returns,
updating the kill ring but not changing the buffer.
900 901
@end defopt

Richard M. Stallman's avatar
Richard M. Stallman committed
902 903
@deffn Command copy-region-as-kill start end
This command saves the region defined by @var{start} and @var{end} on
Karl Heuer's avatar
Karl Heuer committed
904
the kill ring (including text properties), but does not delete the text
905
from the buffer.  It returns @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
906

Karl Heuer's avatar
Karl Heuer committed
907 908 909
The command does not set @code{this-command} to @code{kill-region}, so a
subsequent kill command does not append to the same kill ring entry.

Richard M. Stallman's avatar
Richard M. Stallman committed
910
Don't call @code{copy-region-as-kill} in Lisp programs unless you aim to
911 912 913
support Emacs 18.  For newer Emacs versions, it is better to use
@code{kill-new} or @code{kill-append} instead.  @xref{Low-Level Kill
Ring}.
Richard M. Stallman's avatar
Richard M. Stallman committed
914 915
@end deffn

916 917 918 919 920 921 922 923 924 925 926
@node Yanking
@subsection Yanking

  Yanking means inserting text from the kill ring, but it does
not insert the text blindly.  Yank commands and some other commands
use @code{insert-for-yank} to perform special processing on the
text that they copy into the buffer.

@defun insert-for-yank string
This function normally works like @code{insert} except that it doesn't
insert the text properties in the @code{yank-excluded-properties}
927 928 929
list.  However, if any part of @var{string} has a non-@code{nil}
@code{yank-handler} text property, that property can do various
special processing on that part of the text being inserted.
930 931 932 933 934 935 936 937
@end defun

@defun insert-buffer-substring-as-yank buf &optional start end
This function resembles @code{insert-buffer-substring} except that it
doesn't insert the text properties in the
@code{yank-excluded-properties} list.
@end defun

938 939 940 941 942
  You can put a @code{yank-handler} text property on all or part of
the text to control how it will be inserted if it is yanked.  The
@code{insert-for-yank} function looks for that property.  The property
value must be a list of one to four elements, with the following
format (where elements after the first may be omitted):
943 944 945 946 947 948 949 950 951

@example
(@var{function} @var{param} @var{noexclude} @var{undo})
@end example

  Here is what the elements do:

@table @var
@item function
952
When @var{function} is present and non-@code{nil}, it is called instead of
953 954 955 956 957
@code{insert} to insert the string.  @var{function} takes one
argument---the string to insert.

@item param
If @var{param} is present and non-@code{nil}, it replaces @var{string}
958 959 960 961
(or the part of @var{string} being processed) as the object passed to
@var{function} (or @code{insert}); for example, if @var{function} is
@code{yank-rectangle}, @var{param} should be a list of strings to
insert as a rectangle.
962 963 964 965 966 967 968 969

@item noexclude
If @var{noexclude} is present and non-@code{nil}, the normal removal of the
yank-excluded-properties is not performed; instead @var{function} is
responsible for removing those properties.  This may be necessary
if @var{function} adjusts point before or after inserting the object.

@item undo
970
If @var{undo} is present and non-@code{nil}, it is a function that will be
971 972 973 974 975 976
called by @code{yank-pop} to undo the insertion of the current object.
It is called with two arguments, the start and end of the current
region.  @var{function} can set @code{yank-undo-function} to override
the @var{undo} value.
@end table

Richard M. Stallman's avatar
Richard M. Stallman committed
977 978 979 980 981
@node Yank Commands
@comment  node-name,  next,  previous,  up
@subsection Functions for Yanking

  @dfn{Yanking} means reinserting an entry of previously killed text
Karl Heuer's avatar
Karl Heuer committed
982
from the kill ring.  The text properties are copied too.
Richard M. Stallman's avatar
Richard M. Stallman committed
983 984 985

@deffn Command yank &optional arg
@cindex inserting killed text
986
This command inserts before point the text at the front of the
Richard M. Stallman's avatar
Richard M. Stallman committed
987 988 989
kill ring.  It positions the mark at the beginning of that text, and
point at the end.

990 991 992 993
If @var{arg} is a non-@code{nil} list (which occurs interactively when
the user types @kbd{C-u} with no digits), then @code{yank} inserts the
text as described above, but puts point before the yanked text and
puts the mark after it.
Richard M. Stallman's avatar
Richard M. Stallman committed
994

995 996 997 998
If @var{arg} is a number, then @code{yank} inserts the @var{arg}th
most recently killed text---the @var{arg}th element of the kill ring
list, counted cyclically from the front, which is considered the
first element for this purpose.
Richard M. Stallman's avatar
Richard M. Stallman committed
999

1000 1001 1002 1003 1004 1005
@code{yank} does not alter the contents of the kill ring, unless it
used text provided by another program, in which case it pushes that text
onto the kill ring.  However if @var{arg} is an integer different from
one, it rotates the kill ring to place the yanked string at the front.

@code{yank} returns @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1006 1007
@end deffn

1008
@deffn Command yank-pop &optional arg
Richard M. Stallman's avatar
Richard M. Stallman committed
1009 1010 1011 1012 1013 1014 1015 1016
This command replaces the just-yanked entry from the kill ring with a
different entry from the kill ring.

This is allowed only immediately after a @code{yank} or another
@code{yank-pop}.  At such a time, the region contains text that was just
inserted by yanking.  @code{yank-pop} deletes that text and inserts in
its place a different piece of killed text.  It does not add the deleted
text to the kill ring, since it is already in the kill ring somewhere.
1017 1018
It does however rotate the kill ring to place the newly yanked string at
the front.
Richard M. Stallman's avatar
Richard M. Stallman committed
1019 1020 1021 1022 1023 1024 1025 1026 1027 1028

If @var{arg} is @code{nil}, then the replacement text is the previous
element of the kill ring.  If @var{arg} is numeric, the replacement is
the @var{arg}th previous kill.  If @var{arg} is negative, a more recent
kill is the replacement.

The sequence of kills in the kill ring wraps around, so that after the
oldest one comes the newest one, and before the newest one goes the
oldest.

1029
The return value is always @code{nil}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1030 1031
@end deffn

1032 1033 1034 1035
@defvar yank-undo-function
If this variable is non-@code{nil}, the function @code{yank-pop} uses
its value instead of @code{delete-region} to delete the text
inserted by the previous @code{yank} or
1036 1037
@code{yank-pop} command.  The value must be a function of two
arguments, the start and end of the current region.
1038 1039 1040 1041 1042 1043

The function @code{insert-for-yank} automatically sets this variable
according to the @var{undo} element of the @code{yank-handler}
text property, if there is one.
@end defvar

1044 1045
@node Low-Level Kill Ring
@subsection Low-Level Kill Ring
Richard M. Stallman's avatar
Richard M. Stallman committed
1046

1047 1048 1049 1050
  These functions and variables provide access to the kill ring at a
lower level, but still convenient for use in Lisp programs, because they
take care of interaction with window system selections
(@pxref{Window System Selections}).
Richard M. Stallman's avatar
Richard M. Stallman committed
1051 1052

@defun current-kill n &optional do-not-move
1053 1054
The function @code{current-kill} rotates the yanking pointer, which
designates the ``front'' of the kill ring, by @var{n} places (from newer
1055
kills to older ones), and returns the text at that place in the ring.
Richard M. Stallman's avatar
Richard M. Stallman committed
1056 1057 1058

If the optional second argument @var{do-not-move} is non-@code{nil},
then @code{current-kill} doesn't alter the yanking pointer; it just
1059
returns the @var{n}th kill, counting from the current yanking pointer.
Richard M. Stallman's avatar
Richard M. Stallman committed
1060 1061 1062

If @var{n} is zero, indicating a request for the latest kill,
@code{current-kill} calls the value of
1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076
@code{interprogram-paste-function} (documented below) before
consulting the kill ring.  If that value is a function and calling it
returns a string, @code{current-kill} pushes that string onto the kill
ring and returns it.  It also sets the yanking pointer to point to
that new entry, regardless of the value of @var{do-not-move}.
Otherwise, @code{current-kill} does not treat a zero value for @var{n}
specially: it returns the entry pointed at by the yanking pointer and
does not move the yanking pointer.
@end defun

@defun kill-new string &optional replace yank-handler
This function pushes the text @var{string} onto the kill ring and
makes the yanking pointer point to it.  It discards the oldest entry
if appropriate.  It also invokes the value of
Richard M. Stallman's avatar
Richard M. Stallman committed
1077
@code{interprogram-cut-function} (see below).
1078

1079 1080 1081 1082
If @var{replace} is non-@code{nil}, then @code{kill-new} replaces the
first element of the kill ring with @var{string}, rather than pushing
@var{string} onto the kill ring.

1083 1084
If @var{yank-handler} is non-@code{nil}, this puts that value onto
the string of killed text, as a @code{yank-handler} property.
1085 1086 1087
@xref{Yanking}.  Note that if @var{yank-handler} is @code{nil}, then
@code{kill-new} copies any @code{yank-handler} properties present on
@var{string} onto the kill ring, as it does with other text properties.
Richard M. Stallman's avatar
Richard M. Stallman committed
1088 1089
@end defun

1090
@defun kill-append string before-p &optional yank-handler
Richard M. Stallman's avatar
Richard M. Stallman committed
1091
This function appends the text @var{string} to the first entry in the
1092 1093
kill ring and makes the yanking pointer point to the combined entry.
Normally @var{string} goes at the end of the entry, but if
Richard M. Stallman's avatar
Richard M. Stallman committed
1094
@var{before-p} is non-@code{nil}, it goes at the beginning.  This
1095 1096 1097 1098 1099 1100
function also invokes the value of @code{interprogram-cut-function}
(see below).  This handles @var{yank-handler} just like
@code{kill-new}, except that if @var{yank-handler} is different from
the @code{yank-handler} property of the first entry of the kill ring,
@code{kill-append} pushes the concatenated string onto the kill ring,
instead of replacing the original first entry with it.
Richard M. Stallman's avatar
Richard M. Stallman committed
1101 1102 1103 1104 1105 1106 1107 1108
@end defun

@defvar interprogram-paste-function
This variable provides a way of transferring killed text from other
programs, when you are using a window system.  Its value should be
@code{nil} or a function of no arguments.

If the value is a function, @code{current-kill} calls it to get the
1109 1110
``most recent kill.''  If the function returns a non-@code{nil} value,
then that value is used as the ``most recent kill.''  If it returns
1111
@code{nil}, then the front of the kill ring is used.
Richard M. Stallman's avatar
Richard M. Stallman committed
1112

1113 1114 1115
The normal use of this hook is to get the window system's primary
selection as the most recent kill, even if the selection belongs to
another application.  @xref{Window System Selections}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1116 1117 1118
@end defvar

@defvar interprogram-cut-function
1119 1120
This variable provides a way of communicating killed text to other
programs, when you are using a window system.  Its value should be
1121
@code{nil} or a function of one required and one optional argument.
Richard M. Stallman's avatar
Richard M. Stallman committed
1122 1123

If the value is a function, @code{kill-new} and @code{kill-append} call
1124 1125 1126 1127
it with the new first element of the kill ring as the first argument.
The second, optional, argument has the same meaning as the @var{push}
argument to @code{x-set-cut-buffer} (@pxref{Definition of
x-set-cut-buffer}) and only affects the second and later cut buffers.
Richard M. Stallman's avatar
Richard M. Stallman committed
1128

1129
The normal use of this hook is to set the window system's primary
1130 1131
selection (and first cut buffer) from the newly killed text.
@xref{Window System Selections}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1132 1133 1134 1135 1136 1137 1138 1139
@end defvar

@node Internals of Kill Ring
@comment  node-name,  next,  previous,  up
@subsection Internals of the Kill Ring

  The variable @code{kill-ring} holds the kill ring contents, in the
form of a list of strings.  The most recent kill is always at the front
1140
of the list.
Richard M. Stallman's avatar
Richard M. Stallman committed
1141 1142

  The @code{kill-ring-yank-pointer} variable points to a link in the
1143 1144
kill ring list, whose @sc{car} is the text to yank next.  We say it
identifies the ``front'' of the ring.  Moving
Richard M. Stallman's avatar
Richard M. Stallman committed
1145
@code{kill-ring-yank-pointer} to a different link is called
1146 1147 1148 1149
@dfn{rotating the kill ring}.  We call the kill ring a ``ring'' because
the functions that move the yank pointer wrap around from the end of the
list to the beginning, or vice-versa.  Rotation of the kill ring is
virtual; it does not change the value of @code{kill-ring}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1150 1151 1152 1153 1154 1155 1156 1157 1158 1159

  Both @code{kill-ring} and @code{kill-ring-yank-pointer} are Lisp
variables whose values are normally lists.  The word ``pointer'' in the
name of the @code{kill-ring-yank-pointer} indicates that the variable's
purpose is to identify one element of the list for use by the next yank
command.

  The value of @code{kill-ring-yank-pointer} is always @code{eq} to one
of the links in the kill ring list.  The element it identifies is the
@sc{car} of that link.  Kill commands, which change the kill ring, also
1160 1161
set this variable to the value of @code{kill-ring}.  The effect is to
rotate the ring so that the newly killed text is at the front.
Richard M. Stallman's avatar
Richard M. Stallman committed
1162 1163 1164

  Here is a diagram that shows the variable @code{kill-ring-yank-pointer}
pointing to the second entry in the kill ring @code{("some text" "a
1165
different piece of text" "yet older text")}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1166 1167 1168

@example
@group
1169 1170 1171 1172 1173 1174
kill-ring                  ---- kill-ring-yank-pointer
  |                       |
  |                       v
  |     --- ---          --- ---      --- ---
   --> |   |   |------> |   |   |--> |   |   |--> nil
        --- ---          --- ---      --- ---
1175 1176 1177
         |                |            |
         |                |            |
         |                |             -->"yet older text"
Richard M. Stallman's avatar
Richard M. Stallman committed
1178
         |                |
1179
         |                 --> "a different piece of text"
Richard M. Stallman's avatar
Richard M. Stallman committed
1180 1181 1182 1183 1184 1185 1186 1187 1188 1189
         |
          --> "some text"
@end group
@end example

@noindent
This state of affairs might occur after @kbd{C-y} (@code{yank})
immediately followed by @kbd{M-y} (@code{yank-pop}).

@defvar kill-ring
1190 1191
This variable holds the list of killed text sequences, most recently
killed first.
Richard M. Stallman's avatar
Richard M. Stallman committed
1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203
@end defvar

@defvar kill-ring-yank-pointer
This variable's value indicates which element of the kill ring is at the
``front'' of the ring for yanking.  More precisely, the value is a tail
of the value of @code{kill-ring}, and its @sc{car} is the kill string
that @kbd{C-y} should yank.
@end defvar

@defopt kill-ring-max
The value of this variable is the maximum length to which the kill
ring can grow, before elements are thrown away at the end.  The default
1204
value for @code{kill-ring-max} is 60.
Richard M. Stallman's avatar
Richard M. Stallman committed
1205 1206 1207 1208 1209 1210 1211
@end defopt

@node Undo
@comment  node-name,  next,  previous,  up
@section Undo
@cindex redo

1212 1213 1214
  Most buffers have an @dfn{undo list}, which records all changes made
to the buffer's text so that they can be undone.  (The buffers that
don't have one are usually special-purpose buffers for which Emacs
1215 1216 1217
assumes that undoing is not useful.  In particular, any buffer whose
name begins with a space has its undo recording off by default,
see @ref{Buffer Names}.)  All the primitives that modify the
1218 1219
text in the buffer automatically add elements to the front of the undo
list, which is in the variable @code{buffer-undo-list}.
Richard M. Stallman's avatar
Richard M. Stallman committed
1220 1221

@defvar buffer-undo-list
1222 1223
This buffer-local variable's value is the undo list of the current
buffer. A value of @code{t} disables the recording of undo information.
Richard M. Stallman's avatar
Richard M. Stallman committed
1224 1225 1226 1227 1228
@end defvar

Here are the kinds of elements an undo list can have:

@table @code
1229 1230 1231 1232 1233
@item @var{position}
This kind of element records a previous value of point; undoing this
element moves point to @var{position}.  Ordinary cursor motion does not
make any sort of undo record, but deletion operations use these entries
to record where point was before the command.
Richard M. Stallman's avatar
Richard M. Stallman committed
1234 1235 1236

@item (@var{beg} . @var{end})
This kind of element indicates how to delete text that was inserted.
1237
Upon insertion, the text occupied the range @var{beg}--@var{end} in the
Richard M. Stallman's avatar
Richard M. Stallman committed
1238 1239
buffer.

Richard M. Stallman's avatar
Richard M. Stallman committed
1240
@item (@var{text} . @var{position})
Richard M. Stallman's avatar
Richard M. Stallman committed
1241
This kind of element indicates how to reinsert text that was deleted.
Richard M. Stallman's avatar
Richard M. Stallman committed
1242
The deleted text itself is the string @var{text}.  The place to
1243 1244 1245
reinsert it is @code{(abs @var{position})}.  If @var{position} is
positive, point was at the beginning of the deleted text, otherwise it
was at the end.
Richard M. Stallman's avatar
Richard M. Stallman committed
1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261

@item (t @var{high} . @var{low})
This kind of element indicates that an unmodified buffer became
modified.  The elements @var{high} and @var{low} are two integers, each
recording 16 bits of the visited file's modification time as of when it
was previously visited or saved.  @code{primitive-undo} uses those
values to determine whether to mark the buffer as unmodified once again;
it does so only if the file's modification time matches those numbers.

@item (nil @var{property} @var{value} @var{beg} . @var{end})
This kind of element records a change in a text property.
Here's how you might undo the change:

@example
(put-text-property @var{beg} @var{end} @var{property} @var{value})
@end example
Richard M. Stallman's avatar
Richard M. Stallman committed
1262

1263 1264 1265 1266 1267 1268
@item (@var{marker} . @var{adjustment})
This kind of element records the fact that the marker @var{marker} was
relocated due to deletion of surrounding text, and that it moved
@var{adjustment} character positions.  Undoing this element moves
@var{marker} @minus{} @var{adjustment} characters.

1269 1270 1271 1272 1273 1274 1275 1276 1277 1278
@item (apply @var{funname} . @var{args})
This is an extensible undo item, which is undone by calling
@var{funname} with arguments @var{args}.

@item (apply @var{delta} @var{beg} @var{end} @var{funname} . @var{args})
This is an extensible undo item, which records a change limited to the
range @var{beg} to @var{end}, which increased the size of the buffer
by @var{delta}.  It is undone by calling @var{funname} with arguments
@var{args}.

1279 1280 1281
This kind of element enables undo limited to a region to determine
whether the element pertains to that region.

Richard M. Stallman's avatar
Richard M. Stallman committed
1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293
@item nil
This element is a boundary.  The elements between two boundaries are
called a @dfn{change group}; normally, each change group corresponds to
one keyboard command, and undo commands normally undo an entire group as
a unit.
@end table

@defun undo-boundary
This function places a boundary element in the undo list.  The undo
command stops at such a boundary, and successive undo commands undo
to earlier and earlier boundaries.  This function returns @code{nil}.

1294 1295 1296 1297 1298 1299 1300 1301 1302
The editor command loop automatically creates an undo boundary before
each key sequence is executed.  Thus, each undo normally undoes the
effects of one command.  Self-inserting input characters are an
exception.  The command loop makes a boundary for the first such
character; the next 19 consecutive self-inserting input characters do
not make boundaries, and then the 20th does, and so on as long as
self-inserting characters continue.

All buffer modifications add a boundary whenever the previous undoable
1303 1304
change was made in some other buffer.  This is to ensure that
each command makes a boundary in each buffer where it makes changes.
1305 1306 1307 1308 1309

Calling this function explicitly is useful for splitting the effects of
a command into more than one unit.  For example, @code{query-replace}
calls @code{undo-boundary} after each replacement, so that the user can
undo individual replacements one by one.
Richard M. Stallman's avatar
Richard M. Stallman committed
1310 1311
@end defun

1312 1313 1314 1315 1316 1317
@defvar undo-in-progress
This variable is normally @code{nil}, but the undo commands bind it to
@code{t}.  This is so that various kinds of change hooks can tell when
they're being called for the sake of undoing.
@end defvar

Richard M. Stallman's avatar
Richard M. Stallman committed
1318 1319 1320 1321 1322 1323 1324 1325 1326