2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1995, 1998-2014 Free Software Foundation, Inc.
4 @c See the file elisp.texi for copying conditions.
7 @cindex position (in buffer)
8 @cindex buffer position
10 A @dfn{position} is the index of a character in the text of a buffer.
11 More precisely, a position identifies the place between two characters
12 (or before the first character, or after the last character), so we can
13 speak of the character before or after a given position. However, we
14 often speak of the character ``at'' a position, meaning the character
17 Positions are usually represented as integers starting from 1, but
18 can also be represented as @dfn{markers}---special objects that
19 relocate automatically when text is inserted or deleted so they stay
20 with the surrounding characters. Functions that expect an argument to
21 be a position (an integer), but accept a marker as a substitute,
22 normally ignore which buffer the marker points into; they convert the
23 marker to an integer, and use that integer, exactly as if you had
24 passed the integer as the argument, even if the marker points to the
25 ``wrong'' buffer. A marker that points nowhere cannot convert to an
26 integer; using it instead of an integer causes an error.
29 See also the ``field'' feature (@pxref{Fields}), which provides
30 functions that are used by many cursor-motion commands.
33 * Point:: The special position where editing takes place.
34 * Motion:: Changing point.
35 * Excursions:: Temporary motion and buffer changes.
36 * Narrowing:: Restricting editing to a portion of the buffer.
43 @dfn{Point} is a special buffer position used by many editing
44 commands, including the self-inserting typed characters and text
45 insertion functions. Other commands move point through the text
46 to allow editing and insertion at different places.
48 Like other positions, point designates a place between two characters
49 (or before the first character, or after the last character), rather
50 than a particular character. Usually terminals display the cursor over
51 the character that immediately follows point; point is actually before
52 the character on which the cursor sits.
54 @cindex point with narrowing
55 The value of point is a number no less than 1, and no greater than the
56 buffer size plus 1. If narrowing is in effect (@pxref{Narrowing}), then
57 point is constrained to fall within the accessible portion of the buffer
58 (possibly at one end of it).
60 Each buffer has its own value of point, which is independent of the
61 value of point in other buffers. Each window also has a value of point,
62 which is independent of the value of point in other windows on the same
63 buffer. This is why point can have different values in various windows
64 that display the same buffer. When a buffer appears in only one window,
65 the buffer's point and the window's point normally have the same value,
66 so the distinction is rarely important. @xref{Window Point}, for more
70 @cindex current buffer position
71 This function returns the value of point in the current buffer,
84 This function returns the minimum accessible value of point in the
85 current buffer. This is normally 1, but if narrowing is in effect, it
86 is the position of the start of the region that you narrowed to.
91 This function returns the maximum accessible value of point in the
92 current buffer. This is @code{(1+ (buffer-size))}, unless narrowing is
93 in effect, in which case it is the position of the end of the region
94 that you narrowed to. (@xref{Narrowing}.)
97 @defun buffer-end flag
98 This function returns @code{(point-max)} if @var{flag} is greater than
99 0, @code{(point-min)} otherwise. The argument @var{flag} must be a
103 @defun buffer-size &optional buffer
104 This function returns the total number of characters in the current
105 buffer. In the absence of any narrowing (@pxref{Narrowing}),
106 @code{point-max} returns a value one larger than this.
108 If you specify a buffer, @var{buffer}, then the value is the
109 size of @var{buffer}.
125 @cindex motion by chars, words, lines, lists
127 Motion functions change the value of point, either relative to the
128 current value of point, relative to the beginning or end of the buffer,
129 or relative to the edges of the selected window. @xref{Point}.
132 * Character Motion:: Moving in terms of characters.
133 * Word Motion:: Moving in terms of words.
134 * Buffer End Motion:: Moving to the beginning or end of the buffer.
135 * Text Lines:: Moving in terms of lines of text.
136 * Screen Lines:: Moving in terms of lines as displayed.
137 * List Motion:: Moving by parsing lists and sexps.
138 * Skipping Characters:: Skipping characters belonging to a certain set.
141 @node Character Motion
142 @subsection Motion by Characters
144 These functions move point based on a count of characters.
145 @code{goto-char} is the fundamental primitive; the other functions use
148 @deffn Command goto-char position
149 This function sets point in the current buffer to the value
151 @c This behavior used to be documented until 2013/08.
153 If @var{position} is less than 1, it moves point to the beginning of
154 the buffer. If @var{position} is greater than the length of the
155 buffer, it moves point to the end.
158 If narrowing is in effect, @var{position} still counts from the
159 beginning of the buffer, but point cannot go outside the accessible
160 portion. If @var{position} is out of range, @code{goto-char} moves
161 point to the beginning or the end of the accessible portion.
163 When this function is called interactively, @var{position} is the
164 numeric prefix argument, if provided; otherwise it is read from the
167 @code{goto-char} returns @var{position}.
170 @deffn Command forward-char &optional count
171 @c @kindex beginning-of-buffer
172 @c @kindex end-of-buffer
173 This function moves point @var{count} characters forward, towards the
174 end of the buffer (or backward, towards the beginning of the buffer, if
175 @var{count} is negative). If @var{count} is @code{nil}, the default
178 If this attempts to move past the beginning or end of the buffer (or
179 the limits of the accessible portion, when narrowing is in effect), it
180 signals an error with error symbol @code{beginning-of-buffer} or
181 @code{end-of-buffer}.
183 In an interactive call, @var{count} is the numeric prefix argument.
186 @deffn Command backward-char &optional count
187 This is just like @code{forward-char} except that it moves
188 in the opposite direction.
192 @subsection Motion by Words
194 These functions for parsing words use the syntax table to decide
195 whether a given character is part of a word. @xref{Syntax Tables}.
197 @deffn Command forward-word &optional count
198 This function moves point forward @var{count} words (or backward if
199 @var{count} is negative). If @var{count} is omitted or @code{nil}, it
202 ``Moving one word'' means moving until point crosses a
203 word-constituent character and then encounters a word-separator
204 character. However, this function cannot move point past the boundary
205 of the accessible portion of the buffer, or across a field boundary
206 (@pxref{Fields}). The most common case of a field boundary is the end
207 of the prompt in the minibuffer.
209 If it is possible to move @var{count} words, without being stopped
210 prematurely by the buffer boundary or a field boundary, the value is
211 @code{t}. Otherwise, the return value is @code{nil} and point stops at
212 the buffer boundary or field boundary.
214 If @code{inhibit-field-text-motion} is non-@code{nil},
215 this function ignores field boundaries.
217 In an interactive call, @var{count} is specified by the numeric prefix
221 @deffn Command backward-word &optional count
222 This function is just like @code{forward-word}, except that it moves
223 backward until encountering the front of a word, rather than forward.
226 @defopt words-include-escapes
228 This variable affects the behavior of @code{forward-word} and everything
229 that uses it. If it is non-@code{nil}, then characters in the
230 ``escape'' and ``character quote'' syntax classes count as part of
231 words. Otherwise, they do not.
234 @defvar inhibit-field-text-motion
235 If this variable is non-@code{nil}, certain motion functions including
236 @code{forward-word}, @code{forward-sentence}, and
237 @code{forward-paragraph} ignore field boundaries.
240 @node Buffer End Motion
241 @subsection Motion to an End of the Buffer
242 @cindex move to beginning or end of buffer
244 To move point to the beginning of the buffer, write:
248 (goto-char (point-min))
253 Likewise, to move to the end of the buffer, use:
257 (goto-char (point-max))
261 Here are two commands that users use to do these things. They are
262 documented here to warn you not to use them in Lisp programs, because
263 they set the mark and display messages in the echo area.
265 @deffn Command beginning-of-buffer &optional n
266 This function moves point to the beginning of the buffer (or the limits
267 of the accessible portion, when narrowing is in effect), setting the
268 mark at the previous position (except in Transient Mark mode, if
269 the mark is already active, it does not set the mark.)
271 If @var{n} is non-@code{nil}, then it puts point @var{n} tenths of the
272 way from the beginning of the accessible portion of the buffer. In an
273 interactive call, @var{n} is the numeric prefix argument, if provided;
274 otherwise @var{n} defaults to @code{nil}.
276 @strong{Warning:} Don't use this function in Lisp programs!
279 @deffn Command end-of-buffer &optional n
280 This function moves point to the end of the buffer (or the limits of
281 the accessible portion, when narrowing is in effect), setting the mark
282 at the previous position (except in Transient Mark mode when the mark
283 is already active). If @var{n} is non-@code{nil}, then it puts point
284 @var{n} tenths of the way from the end of the accessible portion of
287 In an interactive call, @var{n} is the numeric prefix argument,
288 if provided; otherwise @var{n} defaults to @code{nil}.
290 @strong{Warning:} Don't use this function in Lisp programs!
294 @subsection Motion by Text Lines
297 Text lines are portions of the buffer delimited by newline characters,
298 which are regarded as part of the previous line. The first text line
299 begins at the beginning of the buffer, and the last text line ends at
300 the end of the buffer whether or not the last character is a newline.
301 The division of the buffer into text lines is not affected by the width
302 of the window, by line continuation in display, or by how tabs and
303 control characters are displayed.
305 @deffn Command beginning-of-line &optional count
306 This function moves point to the beginning of the current line. With an
307 argument @var{count} not @code{nil} or 1, it moves forward
308 @var{count}@minus{}1 lines and then to the beginning of the line.
310 This function does not move point across a field boundary
311 (@pxref{Fields}) unless doing so would move beyond there to a
312 different line; therefore, if @var{count} is @code{nil} or 1, and
313 point starts at a field boundary, point does not move. To ignore
314 field boundaries, either bind @code{inhibit-field-text-motion} to
315 @code{t}, or use the @code{forward-line} function instead. For
316 instance, @code{(forward-line 0)} does the same thing as
317 @code{(beginning-of-line)}, except that it ignores field boundaries.
319 If this function reaches the end of the buffer (or of the accessible
320 portion, if narrowing is in effect), it positions point there. No error
324 @defun line-beginning-position &optional count
325 Return the position that @code{(beginning-of-line @var{count})}
329 @deffn Command end-of-line &optional count
330 This function moves point to the end of the current line. With an
331 argument @var{count} not @code{nil} or 1, it moves forward
332 @var{count}@minus{}1 lines and then to the end of the line.
334 This function does not move point across a field boundary
335 (@pxref{Fields}) unless doing so would move beyond there to a
336 different line; therefore, if @var{count} is @code{nil} or 1, and
337 point starts at a field boundary, point does not move. To ignore
338 field boundaries, bind @code{inhibit-field-text-motion} to @code{t}.
340 If this function reaches the end of the buffer (or of the accessible
341 portion, if narrowing is in effect), it positions point there. No error
345 @defun line-end-position &optional count
346 Return the position that @code{(end-of-line @var{count})}
350 @deffn Command forward-line &optional count
351 @cindex beginning of line
352 This function moves point forward @var{count} lines, to the beginning of
353 the line. If @var{count} is negative, it moves point
354 @minus{}@var{count} lines backward, to the beginning of a line. If
355 @var{count} is zero, it moves point to the beginning of the current
356 line. If @var{count} is @code{nil}, that means 1.
358 If @code{forward-line} encounters the beginning or end of the buffer (or
359 of the accessible portion) before finding that many lines, it sets point
360 there. No error is signaled.
362 @code{forward-line} returns the difference between @var{count} and the
363 number of lines actually moved. If you attempt to move down five lines
364 from the beginning of a buffer that has only three lines, point stops at
365 the end of the last line, and the value will be 2.
367 In an interactive call, @var{count} is the numeric prefix argument.
370 @defun count-lines start end
371 @cindex lines in region
372 @anchor{Definition of count-lines}
373 This function returns the number of lines between the positions
374 @var{start} and @var{end} in the current buffer. If @var{start} and
375 @var{end} are equal, then it returns 0. Otherwise it returns at least
376 1, even if @var{start} and @var{end} are on the same line. This is
377 because the text between them, considered in isolation, must contain at
378 least one line unless it is empty.
381 @deffn Command count-words start end
382 @cindex words in region
383 This function returns the number of words between the positions
384 @var{start} and @var{end} in the current buffer.
386 This function can also be called interactively. In that case, it
387 prints a message reporting the number of lines, words, and characters
388 in the buffer, or in the region if the region is active.
391 @defun line-number-at-pos &optional pos
393 This function returns the line number in the current buffer
394 corresponding to the buffer position @var{pos}. If @var{pos} is @code{nil}
395 or omitted, the current buffer position is used.
400 The @code{previous-line} and @code{next-line} commands are functions
401 that should not be used in programs. They are for users and are
402 mentioned here only for completeness.
404 @deffn Command previous-line count
406 This function moves point up @var{count} lines (down if @var{count}
407 is negative). In moving, it attempts to keep point in the ``goal column''
408 (normally the same column that it was at the beginning of the move).
410 If there is no character in the target line exactly under the current
411 column, point is positioned after the character in that line which
412 spans this column, or at the end of the line if it is not long enough.
414 If it attempts to move beyond the top or bottom of the buffer (or clipped
415 region), then point is positioned in the goal column in the top or
416 bottom line. No error is signaled.
418 In an interactive call, @var{count} will be the numeric
421 The command @code{set-goal-column} can be used to create a semipermanent
422 goal column to which this command always moves. Then it does not try to
425 If you are thinking of using this in a Lisp program, consider using
426 @code{forward-line} with a negative argument instead. It is usually easier
427 to use and more reliable (no dependence on goal column, etc.).
430 @deffn Command next-line count
431 This function moves point down @var{count} lines (up if @var{count}
432 is negative). In moving, it attempts to keep point in the ``goal column''
433 (normally the same column that it was at the beginning of the move).
435 If there is no character in the target line exactly under the current
436 column, point is positioned after the character in that line which
437 spans this column, or at the end of the line if it is not long enough.
439 If it attempts to move beyond the top or bottom of the buffer (or clipped
440 region), then point is positioned in the goal column in the top or
441 bottom line. No error is signaled.
443 In the case where the @var{count} is 1, and point is on the last
444 line of the buffer (or clipped region), a new empty line is inserted at the
445 end of the buffer (or clipped region) and point moved there.
447 In an interactive call, @var{count} will be the numeric
450 The command @code{set-goal-column} can be used to create a semipermanent
451 goal column to which this command always moves. Then it does not try to
454 If you are thinking of using this in a Lisp program, consider using
455 @code{forward-line} instead. It is usually easier
456 to use and more reliable (no dependence on goal column, etc.).
462 Also see the functions @code{bolp} and @code{eolp} in @ref{Near Point}.
463 These functions do not move point, but test whether it is already at the
464 beginning or end of a line.
467 @subsection Motion by Screen Lines
469 The line functions in the previous section count text lines, delimited
470 only by newline characters. By contrast, these functions count screen
471 lines, which are defined by the way the text appears on the screen. A
472 text line is a single screen line if it is short enough to fit the width
473 of the selected window, but otherwise it may occupy several screen
476 In some cases, text lines are truncated on the screen rather than
477 continued onto additional screen lines. In these cases,
478 @code{vertical-motion} moves point much like @code{forward-line}.
481 Because the width of a given string depends on the flags that control
482 the appearance of certain characters, @code{vertical-motion} behaves
483 differently, for a given piece of text, depending on the buffer it is
484 in, and even on the selected window (because the width, the truncation
485 flag, and display table may vary between windows). @xref{Usual
488 These functions scan text to determine where screen lines break, and
489 thus take time proportional to the distance scanned.
491 If you intend to use them heavily, Emacs provides caches which may
492 improve the performance of your code. @xref{Truncation, cache-long-scans}.
495 @defun vertical-motion count &optional window
496 This function moves point to the start of the screen line @var{count}
497 screen lines down from the screen line containing point. If @var{count}
498 is negative, it moves up instead.
500 The @var{count} argument can be a cons cell, @code{(@var{cols}
501 . @var{lines})}, instead of an integer. Then the function moves by
502 @var{lines} screen lines, and puts point @var{cols} columns from the
503 visual start of that screen line. Note that @var{cols} are counted
504 from the @emph{visual} start of the line; if the window is scrolled
505 horizontally (@pxref{Horizontal Scrolling}), the column on which point
506 will end is in addition to the number of columns by which the text is
509 The return value is the number of screen lines over which point was
510 moved. The value may be less in absolute value than @var{count} if
511 the beginning or end of the buffer was reached.
513 The window @var{window} is used for obtaining parameters such as the
514 width, the horizontal scrolling, and the display table. But
515 @code{vertical-motion} always operates on the current buffer, even if
516 @var{window} currently displays some other buffer.
519 @defun count-screen-lines &optional beg end count-final-newline window
520 This function returns the number of screen lines in the text from
521 @var{beg} to @var{end}. The number of screen lines may be different
522 from the number of actual lines, due to line continuation, the display
523 table, etc. If @var{beg} and @var{end} are @code{nil} or omitted,
524 they default to the beginning and end of the accessible portion of the
527 If the region ends with a newline, that is ignored unless the optional
528 third argument @var{count-final-newline} is non-@code{nil}.
530 The optional fourth argument @var{window} specifies the window for
531 obtaining parameters such as width, horizontal scrolling, and so on.
532 The default is to use the selected window's parameters.
534 Like @code{vertical-motion}, @code{count-screen-lines} always uses the
535 current buffer, regardless of which buffer is displayed in
536 @var{window}. This makes possible to use @code{count-screen-lines} in
537 any buffer, whether or not it is currently displayed in some window.
540 @deffn Command move-to-window-line count
541 This function moves point with respect to the text currently displayed
542 in the selected window. It moves point to the beginning of the screen
543 line @var{count} screen lines from the top of the window. If
544 @var{count} is negative, that specifies a position
545 @w{@minus{}@var{count}} lines from the bottom (or the last line of the
546 buffer, if the buffer ends above the specified screen position).
548 If @var{count} is @code{nil}, then point moves to the beginning of the
549 line in the middle of the window. If the absolute value of @var{count}
550 is greater than the size of the window, then point moves to the place
551 that would appear on that screen line if the window were tall enough.
552 This will probably cause the next redisplay to scroll to bring that
553 location onto the screen.
555 In an interactive call, @var{count} is the numeric prefix argument.
557 The value returned is the window line number point has moved to, with
558 the top line in the window numbered 0.
561 @defun compute-motion from frompos to topos width offsets window
562 This function scans the current buffer, calculating screen positions.
563 It scans the buffer forward from position @var{from}, assuming that is
564 at screen coordinates @var{frompos}, to position @var{to} or coordinates
565 @var{topos}, whichever comes first. It returns the ending buffer
566 position and screen coordinates.
568 The coordinate arguments @var{frompos} and @var{topos} are cons cells of
569 the form @code{(@var{hpos} . @var{vpos})}.
571 The argument @var{width} is the number of columns available to display
572 text; this affects handling of continuation lines. @code{nil} means
573 the actual number of usable text columns in the window, which is
574 equivalent to the value returned by @code{(window-width window)}.
576 The argument @var{offsets} is either @code{nil} or a cons cell of the
577 form @code{(@var{hscroll} . @var{tab-offset})}. Here @var{hscroll} is
578 the number of columns not being displayed at the left margin; most
579 callers get this by calling @code{window-hscroll}. Meanwhile,
580 @var{tab-offset} is the offset between column numbers on the screen and
581 column numbers in the buffer. This can be nonzero in a continuation
582 line, when the previous screen lines' widths do not add up to a multiple
583 of @code{tab-width}. It is always zero in a non-continuation line.
585 The window @var{window} serves only to specify which display table to
586 use. @code{compute-motion} always operates on the current buffer,
587 regardless of what buffer is displayed in @var{window}.
589 The return value is a list of five elements:
592 (@var{pos} @var{hpos} @var{vpos} @var{prevhpos} @var{contin})
596 Here @var{pos} is the buffer position where the scan stopped, @var{vpos}
597 is the vertical screen position, and @var{hpos} is the horizontal screen
600 The result @var{prevhpos} is the horizontal position one character back
601 from @var{pos}. The result @var{contin} is @code{t} if the last line
602 was continued after (or within) the previous character.
604 For example, to find the buffer position of column @var{col} of screen line
605 @var{line} of a certain window, pass the window's display start location
606 as @var{from} and the window's upper-left coordinates as @var{frompos}.
607 Pass the buffer's @code{(point-max)} as @var{to}, to limit the scan to
608 the end of the accessible portion of the buffer, and pass @var{line} and
609 @var{col} as @var{topos}. Here's a function that does this:
612 (defun coordinates-of-position (col line)
613 (car (compute-motion (window-start)
618 (cons (window-hscroll) 0)
622 When you use @code{compute-motion} for the minibuffer, you need to use
623 @code{minibuffer-prompt-width} to get the horizontal position of the
624 beginning of the first screen line. @xref{Minibuffer Contents}.
628 @subsection Moving over Balanced Expressions
630 @cindex Lisp expression motion
632 @cindex balanced parenthesis motion
634 Here are several functions concerned with balanced-parenthesis
635 expressions (also called @dfn{sexps} in connection with moving across
636 them in Emacs). The syntax table controls how these functions interpret
637 various characters; see @ref{Syntax Tables}. @xref{Parsing
638 Expressions}, for lower-level primitives for scanning sexps or parts of
639 sexps. For user-level commands, see @ref{Parentheses,, Commands for
640 Editing with Parentheses, emacs, The GNU Emacs Manual}.
642 @deffn Command forward-list &optional arg
643 This function moves forward across @var{arg} (default 1) balanced groups of
644 parentheses. (Other syntactic entities such as words or paired string
648 @deffn Command backward-list &optional arg
649 This function moves backward across @var{arg} (default 1) balanced groups of
650 parentheses. (Other syntactic entities such as words or paired string
654 @deffn Command up-list &optional arg
655 This function moves forward out of @var{arg} (default 1) levels of parentheses.
656 A negative argument means move backward but still to a less deep spot.
659 @deffn Command down-list &optional arg
660 This function moves forward into @var{arg} (default 1) levels of
661 parentheses. A negative argument means move backward but still go
662 deeper in parentheses (@minus{}@var{arg} levels).
665 @deffn Command forward-sexp &optional arg
666 This function moves forward across @var{arg} (default 1) balanced expressions.
667 Balanced expressions include both those delimited by parentheses and
668 other kinds, such as words and string constants.
669 @xref{Parsing Expressions}. For example,
673 ---------- Buffer: foo ----------
674 (concat@point{} "foo " (car x) y z)
675 ---------- Buffer: foo ----------
682 ---------- Buffer: foo ----------
683 (concat "foo " (car x) y@point{} z)
684 ---------- Buffer: foo ----------
689 @deffn Command backward-sexp &optional arg
690 This function moves backward across @var{arg} (default 1) balanced expressions.
693 @deffn Command beginning-of-defun &optional arg
694 This function moves back to the @var{arg}th beginning of a defun. If
695 @var{arg} is negative, this actually moves forward, but it still moves
696 to the beginning of a defun, not to the end of one. @var{arg} defaults
700 @deffn Command end-of-defun &optional arg
701 This function moves forward to the @var{arg}th end of a defun. If
702 @var{arg} is negative, this actually moves backward, but it still moves
703 to the end of a defun, not to the beginning of one. @var{arg} defaults
707 @defopt defun-prompt-regexp
708 If non-@code{nil}, this buffer-local variable holds a regular
709 expression that specifies what text can appear before the
710 open-parenthesis that starts a defun. That is to say, a defun begins
711 on a line that starts with a match for this regular expression,
712 followed by a character with open-parenthesis syntax.
715 @defopt open-paren-in-column-0-is-defun-start
716 If this variable's value is non-@code{nil}, an open parenthesis in
717 column 0 is considered to be the start of a defun. If it is
718 @code{nil}, an open parenthesis in column 0 has no special meaning.
719 The default is @code{t}.
722 @defvar beginning-of-defun-function
723 If non-@code{nil}, this variable holds a function for finding the
724 beginning of a defun. The function @code{beginning-of-defun}
725 calls this function instead of using its normal method, passing it its
726 optional argument. If the argument is non-@code{nil}, the function
727 should move back by that many functions, like
728 @code{beginning-of-defun} does.
731 @defvar end-of-defun-function
732 If non-@code{nil}, this variable holds a function for finding the end of
733 a defun. The function @code{end-of-defun} calls this function instead
734 of using its normal method.
737 @node Skipping Characters
738 @subsection Skipping Characters
739 @cindex skipping characters
741 The following two functions move point over a specified set of
742 characters. For example, they are often used to skip whitespace. For
743 related functions, see @ref{Motion and Syntax}.
745 These functions convert the set string to multibyte if the buffer is
746 multibyte, and they convert it to unibyte if the buffer is unibyte, as
747 the search functions do (@pxref{Searching and Matching}).
749 @defun skip-chars-forward character-set &optional limit
750 This function moves point in the current buffer forward, skipping over a
751 given set of characters. It examines the character following point,
752 then advances point if the character matches @var{character-set}. This
753 continues until it reaches a character that does not match. The
754 function returns the number of characters moved over.
756 The argument @var{character-set} is a string, like the inside of a
757 @samp{[@dots{}]} in a regular expression except that @samp{]} does not
758 terminate it, and @samp{\} quotes @samp{^}, @samp{-} or @samp{\}.
759 Thus, @code{"a-zA-Z"} skips over all letters, stopping before the
760 first nonletter, and @code{"^a-zA-Z"} skips nonletters stopping before
761 the first letter. See @xref{Regular Expressions}. Character classes
762 can also be used, e.g., @code{"[:alnum:]"}. See @pxref{Char Classes}.
764 If @var{limit} is supplied (it must be a number or a marker), it
765 specifies the maximum position in the buffer that point can be skipped
766 to. Point will stop at or before @var{limit}.
768 In the following example, point is initially located directly before the
769 @samp{T}. After the form is evaluated, point is located at the end of
770 that line (between the @samp{t} of @samp{hat} and the newline). The
771 function skips all letters and spaces, but not newlines.
775 ---------- Buffer: foo ----------
776 I read "@point{}The cat in the hat
778 ---------- Buffer: foo ----------
782 (skip-chars-forward "a-zA-Z ")
785 ---------- Buffer: foo ----------
786 I read "The cat in the hat@point{}
788 ---------- Buffer: foo ----------
793 @defun skip-chars-backward character-set &optional limit
794 This function moves point backward, skipping characters that match
795 @var{character-set}, until @var{limit}. It is just like
796 @code{skip-chars-forward} except for the direction of motion.
798 The return value indicates the distance traveled. It is an integer that
806 It is often useful to move point ``temporarily'' within a localized
807 portion of the program. This is called an @dfn{excursion}, and it is
808 done with the @code{save-excursion} special form. This construct
809 remembers the initial identity of the current buffer, and its values
810 of point and the mark, and restores them after the excursion
811 completes. It is the standard way to move point within one part of a
812 program and avoid affecting the rest of the program, and is used
813 thousands of times in the Lisp sources of Emacs.
815 If you only need to save and restore the identity of the current
816 buffer, use @code{save-current-buffer} or @code{with-current-buffer}
817 instead (@pxref{Current Buffer}). If you need to save or restore
818 window configurations, see the forms described in @ref{Window
819 Configurations} and in @ref{Frame Configurations}. @c frameset?
821 @defspec save-excursion body@dots{}
822 @cindex mark excursion
823 @cindex point excursion
824 This special form saves the identity of the current buffer and the
825 values of point and the mark in it, evaluates @var{body}, and finally
826 restores the buffer and its saved values of point and the mark. All
827 three saved values are restored even in case of an abnormal exit via
828 @code{throw} or error (@pxref{Nonlocal Exits}).
830 The value returned by @code{save-excursion} is the result of the last
831 form in @var{body}, or @code{nil} if no body forms were given.
834 Because @code{save-excursion} only saves point and mark for the
835 buffer that was current at the start of the excursion, any changes
836 made to point and/or mark in other buffers, during the excursion, will
837 remain in effect afterward. This frequently leads to unintended
838 consequences, so the byte compiler warns if you call @code{set-buffer}
842 Warning: Use `with-current-buffer' rather than
843 save-excursion+set-buffer
847 To avoid such problems, you should call @code{save-excursion} only
848 after setting the desired current buffer, as in the following example:
852 (defun append-string-to-buffer (string buffer)
853 "Append STRING to the end of BUFFER."
854 (with-current-buffer buffer
856 (goto-char (point-max))
861 @cindex window excursions
862 Likewise, @code{save-excursion} does not restore window-buffer
863 correspondences altered by functions such as @code{switch-to-buffer}.
865 @strong{Warning:} Ordinary insertion of text adjacent to the saved
866 point value relocates the saved value, just as it relocates all
867 markers. More precisely, the saved value is a marker with insertion
868 type @code{nil}. @xref{Marker Insertion Types}. Therefore, when the
869 saved point value is restored, it normally comes before the inserted
872 Although @code{save-excursion} saves the location of the mark, it does
873 not prevent functions which modify the buffer from setting
874 @code{deactivate-mark}, and thus causing the deactivation of the mark
875 after the command finishes. @xref{The Mark}.
880 @cindex restriction (in a buffer)
881 @cindex accessible portion (of a buffer)
883 @dfn{Narrowing} means limiting the text addressable by Emacs editing
884 commands to a limited range of characters in a buffer. The text that
885 remains addressable is called the @dfn{accessible portion} of the
888 Narrowing is specified with two buffer positions, which become the
889 beginning and end of the accessible portion. For most editing
890 commands and primitives, these positions replace the values of the
891 beginning and end of the buffer. While narrowing is in effect, no
892 text outside the accessible portion is displayed, and point cannot
893 move outside the accessible portion. Note that narrowing does not
894 alter actual buffer positions (@pxref{Point}); it only determines
895 which positions are considered the accessible portion of the buffer.
896 Most functions refuse to operate on text that is outside the
899 Commands for saving buffers are unaffected by narrowing; they save
900 the entire buffer regardless of any narrowing.
902 If you need to display in a single buffer several very different
903 types of text, consider using an alternative facility described in
906 @deffn Command narrow-to-region start end
907 This function sets the accessible portion of the current buffer to start
908 at @var{start} and end at @var{end}. Both arguments should be character
911 In an interactive call, @var{start} and @var{end} are set to the bounds
912 of the current region (point and the mark, with the smallest first).
915 @deffn Command narrow-to-page &optional move-count
916 This function sets the accessible portion of the current buffer to
917 include just the current page. An optional first argument
918 @var{move-count} non-@code{nil} means to move forward or backward by
919 @var{move-count} pages and then narrow to one page. The variable
920 @code{page-delimiter} specifies where pages start and end
921 (@pxref{Standard Regexps}).
923 In an interactive call, @var{move-count} is set to the numeric prefix
929 This function cancels any narrowing in the current buffer, so that the
930 entire contents are accessible. This is called @dfn{widening}.
931 It is equivalent to the following expression:
934 (narrow-to-region 1 (1+ (buffer-size)))
938 @defun buffer-narrowed-p
939 This function returns non-@code{nil} if the buffer is narrowed, and
940 @code{nil} otherwise.
943 @defspec save-restriction body@dots{}
944 This special form saves the current bounds of the accessible portion,
945 evaluates the @var{body} forms, and finally restores the saved bounds,
946 thus restoring the same state of narrowing (or absence thereof) formerly
947 in effect. The state of narrowing is restored even in the event of an
948 abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}).
949 Therefore, this construct is a clean way to narrow a buffer temporarily.
951 The value returned by @code{save-restriction} is that returned by the
952 last form in @var{body}, or @code{nil} if no body forms were given.
954 @c Wordy to avoid overfull hbox. --rjc 16mar92
955 @strong{Caution:} it is easy to make a mistake when using the
956 @code{save-restriction} construct. Read the entire description here
959 If @var{body} changes the current buffer, @code{save-restriction} still
960 restores the restrictions on the original buffer (the buffer whose
961 restrictions it saved from), but it does not restore the identity of the
964 @code{save-restriction} does @emph{not} restore point and the mark; use
965 @code{save-excursion} for that. If you use both @code{save-restriction}
966 and @code{save-excursion} together, @code{save-excursion} should come
967 first (on the outside). Otherwise, the old point value would be
968 restored with temporary narrowing still in effect. If the old point
969 value were outside the limits of the temporary narrowing, this would
970 fail to restore it accurately.
972 Here is a simple example of correct use of @code{save-restriction}:
976 ---------- Buffer: foo ----------
977 This is the contents of foo
978 This is the contents of foo
979 This is the contents of foo@point{}
980 ---------- Buffer: foo ----------
988 (narrow-to-region 1 (point))
989 (goto-char (point-min))
990 (replace-string "foo" "bar")))
992 ---------- Buffer: foo ----------
993 This is the contents of bar
994 This is the contents of bar
995 This is the contents of foo@point{}
996 ---------- Buffer: foo ----------