2 @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, 2007, 2008, 2009 Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../../info/positions
7 @node Positions, Markers, Frames, Top
9 @cindex position (in buffer)
11 A @dfn{position} is the index of a character in the text of a buffer.
12 More precisely, a position identifies the place between two characters
13 (or before the first character, or after the last character), so we can
14 speak of the character before or after a given position. However, we
15 often speak of the character ``at'' a position, meaning the character
18 Positions are usually represented as integers starting from 1, but
19 can also be represented as @dfn{markers}---special objects that
20 relocate automatically when text is inserted or deleted so they stay
21 with the surrounding characters. Functions that expect an argument to
22 be a position (an integer), but accept a marker as a substitute,
23 normally ignore which buffer the marker points into; they convert the
24 marker to an integer, and use that integer, exactly as if you had
25 passed the integer as the argument, even if the marker points to the
26 ``wrong'' buffer. A marker that points nowhere cannot convert to an
27 integer; using it instead of an integer causes an error.
30 See also the ``field'' feature (@pxref{Fields}), which provides
31 functions that are used by many cursor-motion commands.
34 * Point:: The special position where editing takes place.
35 * Motion:: Changing point.
36 * Excursions:: Temporary motion and buffer changes.
37 * Narrowing:: Restricting editing to a portion of the buffer.
44 @dfn{Point} is a special buffer position used by many editing
45 commands, including the self-inserting typed characters and text
46 insertion functions. Other commands move point through the text
47 to allow editing and insertion at different places.
49 Like other positions, point designates a place between two characters
50 (or before the first character, or after the last character), rather
51 than a particular character. Usually terminals display the cursor over
52 the character that immediately follows point; point is actually before
53 the character on which the cursor sits.
55 @cindex point with narrowing
56 The value of point is a number no less than 1, and no greater than the
57 buffer size plus 1. If narrowing is in effect (@pxref{Narrowing}), then
58 point is constrained to fall within the accessible portion of the buffer
59 (possibly at one end of it).
61 Each buffer has its own value of point, which is independent of the
62 value of point in other buffers. Each window also has a value of point,
63 which is independent of the value of point in other windows on the same
64 buffer. This is why point can have different values in various windows
65 that display the same buffer. When a buffer appears in only one window,
66 the buffer's point and the window's point normally have the same value,
67 so the distinction is rarely important. @xref{Window Point}, for more
71 @cindex current buffer position
72 This function returns the value of point in the current buffer,
85 This function returns the minimum accessible value of point in the
86 current buffer. This is normally 1, but if narrowing is in effect, it
87 is the position of the start of the region that you narrowed to.
92 This function returns the maximum accessible value of point in the
93 current buffer. This is @code{(1+ (buffer-size))}, unless narrowing is
94 in effect, in which case it is the position of the end of the region
95 that you narrowed to. (@xref{Narrowing}.)
98 @defun buffer-end flag
99 This function returns @code{(point-max)} if @var{flag} is greater than
100 0, @code{(point-min)} otherwise. The argument @var{flag} must be a
104 @defun buffer-size &optional buffer
105 This function returns the total number of characters in the current
106 buffer. In the absence of any narrowing (@pxref{Narrowing}),
107 @code{point-max} returns a value one larger than this.
109 If you specify a buffer, @var{buffer}, then the value is the
110 size of @var{buffer}.
126 @cindex motion by chars, words, lines, lists
128 Motion functions change the value of point, either relative to the
129 current value of point, relative to the beginning or end of the buffer,
130 or relative to the edges of the selected window. @xref{Point}.
133 * Character Motion:: Moving in terms of characters.
134 * Word Motion:: Moving in terms of words.
135 * Buffer End Motion:: Moving to the beginning or end of the buffer.
136 * Text Lines:: Moving in terms of lines of text.
137 * Screen Lines:: Moving in terms of lines as displayed.
138 * List Motion:: Moving by parsing lists and sexps.
139 * Skipping Characters:: Skipping characters belonging to a certain set.
142 @node Character Motion
143 @subsection Motion by Characters
145 These functions move point based on a count of characters.
146 @code{goto-char} is the fundamental primitive; the other functions use
149 @deffn Command goto-char position
150 This function sets point in the current buffer to the value
151 @var{position}. If @var{position} is less than 1, it moves point to the
152 beginning of the buffer. If @var{position} is greater than the length
153 of the buffer, it moves point to the end.
155 If narrowing is in effect, @var{position} still counts from the
156 beginning of the buffer, but point cannot go outside the accessible
157 portion. If @var{position} is out of range, @code{goto-char} moves
158 point to the beginning or the end of the accessible portion.
160 When this function is called interactively, @var{position} is the
161 numeric prefix argument, if provided; otherwise it is read from the
164 @code{goto-char} returns @var{position}.
167 @deffn Command forward-char &optional count
168 @c @kindex beginning-of-buffer
169 @c @kindex end-of-buffer
170 This function moves point @var{count} characters forward, towards the
171 end of the buffer (or backward, towards the beginning of the buffer, if
172 @var{count} is negative). If @var{count} is @code{nil}, the default
175 If this attempts to move past the beginning or end of the buffer (or
176 the limits of the accessible portion, when narrowing is in effect), it
177 signals an error with error symbol @code{beginning-of-buffer} or
178 @code{end-of-buffer}.
180 In an interactive call, @var{count} is the numeric prefix argument.
183 @deffn Command backward-char &optional count
184 This is just like @code{forward-char} except that it moves
185 in the opposite direction.
189 @subsection Motion by Words
191 These functions for parsing words use the syntax table to decide
192 whether a given character is part of a word. @xref{Syntax Tables}.
194 @deffn Command forward-word &optional count
195 This function moves point forward @var{count} words (or backward if
196 @var{count} is negative). If @var{count} is @code{nil}, it moves
199 ``Moving one word'' means moving until point crosses a
200 word-constituent character and then encounters a word-separator
201 character. However, this function cannot move point past the boundary
202 of the accessible portion of the buffer, or across a field boundary
203 (@pxref{Fields}). The most common case of a field boundary is the end
204 of the prompt in the minibuffer.
206 If it is possible to move @var{count} words, without being stopped
207 prematurely by the buffer boundary or a field boundary, the value is
208 @code{t}. Otherwise, the return value is @code{nil} and point stops at
209 the buffer boundary or field boundary.
211 If @code{inhibit-field-text-motion} is non-@code{nil},
212 this function ignores field boundaries.
214 In an interactive call, @var{count} is specified by the numeric prefix
215 argument. If @var{count} is omitted or @code{nil}, it defaults to 1.
218 @deffn Command backward-word &optional count
219 This function is just like @code{forward-word}, except that it moves
220 backward until encountering the front of a word, rather than forward.
223 @defopt words-include-escapes
225 This variable affects the behavior of @code{forward-word} and everything
226 that uses it. If it is non-@code{nil}, then characters in the
227 ``escape'' and ``character quote'' syntax classes count as part of
228 words. Otherwise, they do not.
231 @defvar inhibit-field-text-motion
232 If this variable is non-@code{nil}, certain motion functions including
233 @code{forward-word}, @code{forward-sentence}, and
234 @code{forward-paragraph} ignore field boundaries.
237 @node Buffer End Motion
238 @subsection Motion to an End of the Buffer
239 @cindex move to beginning or end of buffer
241 To move point to the beginning of the buffer, write:
245 (goto-char (point-min))
250 Likewise, to move to the end of the buffer, use:
254 (goto-char (point-max))
258 Here are two commands that users use to do these things. They are
259 documented here to warn you not to use them in Lisp programs, because
260 they set the mark and display messages in the echo area.
262 @deffn Command beginning-of-buffer &optional n
263 This function moves point to the beginning of the buffer (or the limits
264 of the accessible portion, when narrowing is in effect), setting the
265 mark at the previous position (except in Transient Mark mode, if
266 the mark is already active, it does not set the mark.)
268 If @var{n} is non-@code{nil}, then it puts point @var{n} tenths of the
269 way from the beginning of the accessible portion of the buffer. In an
270 interactive call, @var{n} is the numeric prefix argument, if provided;
271 otherwise @var{n} defaults to @code{nil}.
273 @strong{Warning:} Don't use this function in Lisp programs!
276 @deffn Command end-of-buffer &optional n
277 This function moves point to the end of the buffer (or the limits of
278 the accessible portion, when narrowing is in effect), setting the mark
279 at the previous position (except in Transient Mark mode when the mark
280 is already active). If @var{n} is non-@code{nil}, then it puts point
281 @var{n} tenths of the way from the end of the accessible portion of
284 In an interactive call, @var{n} is the numeric prefix argument,
285 if provided; otherwise @var{n} defaults to @code{nil}.
287 @strong{Warning:} Don't use this function in Lisp programs!
291 @subsection Motion by Text Lines
294 Text lines are portions of the buffer delimited by newline characters,
295 which are regarded as part of the previous line. The first text line
296 begins at the beginning of the buffer, and the last text line ends at
297 the end of the buffer whether or not the last character is a newline.
298 The division of the buffer into text lines is not affected by the width
299 of the window, by line continuation in display, or by how tabs and
300 control characters are displayed.
302 @deffn Command beginning-of-line &optional count
303 This function moves point to the beginning of the current line. With an
304 argument @var{count} not @code{nil} or 1, it moves forward
305 @var{count}@minus{}1 lines and then to the beginning of the line.
307 This function does not move point across a field boundary
308 (@pxref{Fields}) unless doing so would move beyond there to a
309 different line; therefore, if @var{count} is @code{nil} or 1, and
310 point starts at a field boundary, point does not move. To ignore
311 field boundaries, either bind @code{inhibit-field-text-motion} to
312 @code{t}, or use the @code{forward-line} function instead. For
313 instance, @code{(forward-line 0)} does the same thing as
314 @code{(beginning-of-line)}, except that it ignores field boundaries.
316 If this function reaches the end of the buffer (or of the accessible
317 portion, if narrowing is in effect), it positions point there. No error
321 @defun line-beginning-position &optional count
322 Return the position that @code{(beginning-of-line @var{count})}
326 @deffn Command end-of-line &optional count
327 This function moves point to the end of the current line. With an
328 argument @var{count} not @code{nil} or 1, it moves forward
329 @var{count}@minus{}1 lines and then to the end of the line.
331 This function does not move point across a field boundary
332 (@pxref{Fields}) unless doing so would move beyond there to a
333 different line; therefore, if @var{count} is @code{nil} or 1, and
334 point starts at a field boundary, point does not move. To ignore
335 field boundaries, bind @code{inhibit-field-text-motion} to @code{t}.
337 If this function reaches the end of the buffer (or of the accessible
338 portion, if narrowing is in effect), it positions point there. No error
342 @defun line-end-position &optional count
343 Return the position that @code{(end-of-line @var{count})}
347 @deffn Command forward-line &optional count
348 @cindex beginning of line
349 This function moves point forward @var{count} lines, to the beginning of
350 the line. If @var{count} is negative, it moves point
351 @minus{}@var{count} lines backward, to the beginning of a line. If
352 @var{count} is zero, it moves point to the beginning of the current
353 line. If @var{count} is @code{nil}, that means 1.
355 If @code{forward-line} encounters the beginning or end of the buffer (or
356 of the accessible portion) before finding that many lines, it sets point
357 there. No error is signaled.
359 @code{forward-line} returns the difference between @var{count} and the
360 number of lines actually moved. If you attempt to move down five lines
361 from the beginning of a buffer that has only three lines, point stops at
362 the end of the last line, and the value will be 2.
364 In an interactive call, @var{count} is the numeric prefix argument.
367 @defun count-lines start end
368 @cindex lines in region
369 @anchor{Definition of count-lines}
370 This function returns the number of lines between the positions
371 @var{start} and @var{end} in the current buffer. If @var{start} and
372 @var{end} are equal, then it returns 0. Otherwise it returns at least
373 1, even if @var{start} and @var{end} are on the same line. This is
374 because the text between them, considered in isolation, must contain at
375 least one line unless it is empty.
377 Here is an example of using @code{count-lines}:
381 (defun current-line ()
382 "Return the vertical position of point@dots{}"
383 (+ (count-lines (window-start) (point))
384 (if (= (current-column) 0) 1 0)))
389 @defun line-number-at-pos &optional pos
391 This function returns the line number in the current buffer
392 corresponding to the buffer position @var{pos}. If @var{pos} is @code{nil}
393 or omitted, the current buffer position is used.
398 The @code{previous-line} and @code{next-line} commands are functions
399 that should not be used in programs. They are for users and are
400 mentioned here only for completeness.
402 @deffn Command previous-line count
404 This function moves point up @var{count} lines (down if @var{count}
405 is negative). In moving, it attempts to keep point in the ``goal column''
406 (normally the same column that it was at the beginning of the move).
408 If there is no character in the target line exactly under the current
409 column, point is positioned after the character in that line which
410 spans this column, or at the end of the line if it is not long enough.
412 If it attempts to move beyond the top or bottom of the buffer (or clipped
413 region), then point is positioned in the goal column in the top or
414 bottom line. No error is signaled.
416 In an interactive call, @var{count} will be the numeric
419 The command @code{set-goal-column} can be used to create a semipermanent
420 goal column to which this command always moves. Then it does not try to
423 If you are thinking of using this in a Lisp program, consider using
424 @code{forward-line} with a negative argument instead. It is usually easier
425 to use and more reliable (no dependence on goal column, etc.).
428 @deffn Command next-line count
429 This function moves point down @var{count} lines (up if @var{count}
430 is negative). In moving, it attempts to keep point in the ``goal column''
431 (normally the same column that it was at the beginning of the move).
433 If there is no character in the target line exactly under the current
434 column, point is positioned after the character in that line which
435 spans this column, or at the end of the line if it is not long enough.
437 If it attempts to move beyond the top or bottom of the buffer (or clipped
438 region), then point is positioned in the goal column in the top or
439 bottom line. No error is signaled.
441 In the case where the @var{count} is 1, and point is on the last
442 line of the buffer (or clipped region), a new empty line is inserted at the
443 end of the buffer (or clipped region) and point moved there.
445 In an interactive call, @var{count} will be the numeric
448 The command @code{set-goal-column} can be used to create a semipermanent
449 goal column to which this command always moves. Then it does not try to
452 If you are thinking of using this in a Lisp program, consider using
453 @code{forward-line} instead. It is usually easier
454 to use and more reliable (no dependence on goal column, etc.).
460 Also see the functions @code{bolp} and @code{eolp} in @ref{Near Point}.
461 These functions do not move point, but test whether it is already at the
462 beginning or end of a line.
465 @subsection Motion by Screen Lines
467 The line functions in the previous section count text lines, delimited
468 only by newline characters. By contrast, these functions count screen
469 lines, which are defined by the way the text appears on the screen. A
470 text line is a single screen line if it is short enough to fit the width
471 of the selected window, but otherwise it may occupy several screen
474 In some cases, text lines are truncated on the screen rather than
475 continued onto additional screen lines. In these cases,
476 @code{vertical-motion} moves point much like @code{forward-line}.
479 Because the width of a given string depends on the flags that control
480 the appearance of certain characters, @code{vertical-motion} behaves
481 differently, for a given piece of text, depending on the buffer it is
482 in, and even on the selected window (because the width, the truncation
483 flag, and display table may vary between windows). @xref{Usual
486 These functions scan text to determine where screen lines break, and
487 thus take time proportional to the distance scanned. If you intend to
488 use them heavily, Emacs provides caches which may improve the
489 performance of your code. @xref{Truncation, cache-long-line-scans}.
491 @defun vertical-motion count &optional window
492 This function moves point to the start of the screen line @var{count}
493 screen lines down from the screen line containing point. If @var{count}
494 is negative, it moves up instead.
496 The @var{count} argument can be a cons cell, @code{(@var{cols}
497 . @var{lines})}, instead of an integer. Then the function moves by
498 @var{lines} screen lines, and puts point @var{cols} columns from the
499 start of that screen line.
501 The return value is the number of screen lines over which point was
502 moved. The value may be less in absolute value than @var{count} if
503 the beginning or end of the buffer was reached.
505 The window @var{window} is used for obtaining parameters such as the
506 width, the horizontal scrolling, and the display table. But
507 @code{vertical-motion} always operates on the current buffer, even if
508 @var{window} currently displays some other buffer.
511 @defun count-screen-lines &optional beg end count-final-newline window
512 This function returns the number of screen lines in the text from
513 @var{beg} to @var{end}. The number of screen lines may be different
514 from the number of actual lines, due to line continuation, the display
515 table, etc. If @var{beg} and @var{end} are @code{nil} or omitted,
516 they default to the beginning and end of the accessible portion of the
519 If the region ends with a newline, that is ignored unless the optional
520 third argument @var{count-final-newline} is non-@code{nil}.
522 The optional fourth argument @var{window} specifies the window for
523 obtaining parameters such as width, horizontal scrolling, and so on.
524 The default is to use the selected window's parameters.
526 Like @code{vertical-motion}, @code{count-screen-lines} always uses the
527 current buffer, regardless of which buffer is displayed in
528 @var{window}. This makes possible to use @code{count-screen-lines} in
529 any buffer, whether or not it is currently displayed in some window.
532 @deffn Command move-to-window-line count
533 This function moves point with respect to the text currently displayed
534 in the selected window. It moves point to the beginning of the screen
535 line @var{count} screen lines from the top of the window. If
536 @var{count} is negative, that specifies a position
537 @w{@minus{}@var{count}} lines from the bottom (or the last line of the
538 buffer, if the buffer ends above the specified screen position).
540 If @var{count} is @code{nil}, then point moves to the beginning of the
541 line in the middle of the window. If the absolute value of @var{count}
542 is greater than the size of the window, then point moves to the place
543 that would appear on that screen line if the window were tall enough.
544 This will probably cause the next redisplay to scroll to bring that
545 location onto the screen.
547 In an interactive call, @var{count} is the numeric prefix argument.
549 The value returned is the window line number point has moved to, with
550 the top line in the window numbered 0.
553 @defun compute-motion from frompos to topos width offsets window
554 This function scans the current buffer, calculating screen positions.
555 It scans the buffer forward from position @var{from}, assuming that is
556 at screen coordinates @var{frompos}, to position @var{to} or coordinates
557 @var{topos}, whichever comes first. It returns the ending buffer
558 position and screen coordinates.
560 The coordinate arguments @var{frompos} and @var{topos} are cons cells of
561 the form @code{(@var{hpos} . @var{vpos})}.
563 The argument @var{width} is the number of columns available to display
564 text; this affects handling of continuation lines. @code{nil} means
565 the actual number of usable text columns in the window, which is
566 equivalent to the value returned by @code{(window-width window)}.
568 The argument @var{offsets} is either @code{nil} or a cons cell of the
569 form @code{(@var{hscroll} . @var{tab-offset})}. Here @var{hscroll} is
570 the number of columns not being displayed at the left margin; most
571 callers get this by calling @code{window-hscroll}. Meanwhile,
572 @var{tab-offset} is the offset between column numbers on the screen and
573 column numbers in the buffer. This can be nonzero in a continuation
574 line, when the previous screen lines' widths do not add up to a multiple
575 of @code{tab-width}. It is always zero in a non-continuation line.
577 The window @var{window} serves only to specify which display table to
578 use. @code{compute-motion} always operates on the current buffer,
579 regardless of what buffer is displayed in @var{window}.
581 The return value is a list of five elements:
584 (@var{pos} @var{hpos} @var{vpos} @var{prevhpos} @var{contin})
588 Here @var{pos} is the buffer position where the scan stopped, @var{vpos}
589 is the vertical screen position, and @var{hpos} is the horizontal screen
592 The result @var{prevhpos} is the horizontal position one character back
593 from @var{pos}. The result @var{contin} is @code{t} if the last line
594 was continued after (or within) the previous character.
596 For example, to find the buffer position of column @var{col} of screen line
597 @var{line} of a certain window, pass the window's display start location
598 as @var{from} and the window's upper-left coordinates as @var{frompos}.
599 Pass the buffer's @code{(point-max)} as @var{to}, to limit the scan to
600 the end of the accessible portion of the buffer, and pass @var{line} and
601 @var{col} as @var{topos}. Here's a function that does this:
604 (defun coordinates-of-position (col line)
605 (car (compute-motion (window-start)
610 (cons (window-hscroll) 0)
614 When you use @code{compute-motion} for the minibuffer, you need to use
615 @code{minibuffer-prompt-width} to get the horizontal position of the
616 beginning of the first screen line. @xref{Minibuffer Contents}.
620 @comment node-name, next, previous, up
621 @subsection Moving over Balanced Expressions
623 @cindex Lisp expression motion
625 @cindex balanced parenthesis motion
627 Here are several functions concerned with balanced-parenthesis
628 expressions (also called @dfn{sexps} in connection with moving across
629 them in Emacs). The syntax table controls how these functions interpret
630 various characters; see @ref{Syntax Tables}. @xref{Parsing
631 Expressions}, for lower-level primitives for scanning sexps or parts of
632 sexps. For user-level commands, see @ref{Parentheses,, Commands for
633 Editing with Parentheses, emacs, The GNU Emacs Manual}.
635 @deffn Command forward-list &optional arg
636 This function moves forward across @var{arg} (default 1) balanced groups of
637 parentheses. (Other syntactic entities such as words or paired string
641 @deffn Command backward-list &optional arg
642 This function moves backward across @var{arg} (default 1) balanced groups of
643 parentheses. (Other syntactic entities such as words or paired string
647 @deffn Command up-list &optional arg
648 This function moves forward out of @var{arg} (default 1) levels of parentheses.
649 A negative argument means move backward but still to a less deep spot.
652 @deffn Command down-list &optional arg
653 This function moves forward into @var{arg} (default 1) levels of
654 parentheses. A negative argument means move backward but still go
655 deeper in parentheses (@minus{}@var{arg} levels).
658 @deffn Command forward-sexp &optional arg
659 This function moves forward across @var{arg} (default 1) balanced expressions.
660 Balanced expressions include both those delimited by parentheses and
661 other kinds, such as words and string constants.
662 @xref{Parsing Expressions}. For example,
666 ---------- Buffer: foo ----------
667 (concat@point{} "foo " (car x) y z)
668 ---------- Buffer: foo ----------
675 ---------- Buffer: foo ----------
676 (concat "foo " (car x) y@point{} z)
677 ---------- Buffer: foo ----------
682 @deffn Command backward-sexp &optional arg
683 This function moves backward across @var{arg} (default 1) balanced expressions.
686 @deffn Command beginning-of-defun &optional arg
687 This function moves back to the @var{arg}th beginning of a defun. If
688 @var{arg} is negative, this actually moves forward, but it still moves
689 to the beginning of a defun, not to the end of one. @var{arg} defaults
693 @deffn Command end-of-defun &optional arg
694 This function moves forward to the @var{arg}th end of a defun. If
695 @var{arg} is negative, this actually moves backward, but it still moves
696 to the end of a defun, not to the beginning of one. @var{arg} defaults
700 @defopt defun-prompt-regexp
701 If non-@code{nil}, this buffer-local variable holds a regular
702 expression that specifies what text can appear before the
703 open-parenthesis that starts a defun. That is to say, a defun begins
704 on a line that starts with a match for this regular expression,
705 followed by a character with open-parenthesis syntax.
708 @defopt open-paren-in-column-0-is-defun-start
709 If this variable's value is non-@code{nil}, an open parenthesis in
710 column 0 is considered to be the start of a defun. If it is
711 @code{nil}, an open parenthesis in column 0 has no special meaning.
712 The default is @code{t}.
715 @defvar beginning-of-defun-function
716 If non-@code{nil}, this variable holds a function for finding the
717 beginning of a defun. The function @code{beginning-of-defun}
718 calls this function instead of using its normal method, passing it its
719 optional argument. If the argument is non-@code{nil}, the function
720 should move back by that many functions, like
721 @code{beginning-of-defun} does.
724 @defvar end-of-defun-function
725 If non-@code{nil}, this variable holds a function for finding the end of
726 a defun. The function @code{end-of-defun} calls this function instead
727 of using its normal method.
730 @node Skipping Characters
731 @comment node-name, next, previous, up
732 @subsection Skipping Characters
733 @cindex skipping characters
735 The following two functions move point over a specified set of
736 characters. For example, they are often used to skip whitespace. For
737 related functions, see @ref{Motion and Syntax}.
739 These functions convert the set string to multibyte if the buffer is
740 multibyte, and they convert it to unibyte if the buffer is unibyte, as
741 the search functions do (@pxref{Searching and Matching}).
743 @defun skip-chars-forward character-set &optional limit
744 This function moves point in the current buffer forward, skipping over a
745 given set of characters. It examines the character following point,
746 then advances point if the character matches @var{character-set}. This
747 continues until it reaches a character that does not match. The
748 function returns the number of characters moved over.
750 The argument @var{character-set} is a string, like the inside of a
751 @samp{[@dots{}]} in a regular expression except that @samp{]} does not
752 terminate it, and @samp{\} quotes @samp{^}, @samp{-} or @samp{\}.
753 Thus, @code{"a-zA-Z"} skips over all letters, stopping before the
754 first nonletter, and @code{"^a-zA-Z"} skips nonletters stopping before
755 the first letter. See @xref{Regular Expressions}. Character classes
756 can also be used, e.g. @code{"[:alnum:]"}. See @pxref{Char Classes}.
758 If @var{limit} is supplied (it must be a number or a marker), it
759 specifies the maximum position in the buffer that point can be skipped
760 to. Point will stop at or before @var{limit}.
762 In the following example, point is initially located directly before the
763 @samp{T}. After the form is evaluated, point is located at the end of
764 that line (between the @samp{t} of @samp{hat} and the newline). The
765 function skips all letters and spaces, but not newlines.
769 ---------- Buffer: foo ----------
770 I read "@point{}The cat in the hat
772 ---------- Buffer: foo ----------
776 (skip-chars-forward "a-zA-Z ")
779 ---------- Buffer: foo ----------
780 I read "The cat in the hat@point{}
782 ---------- Buffer: foo ----------
787 @defun skip-chars-backward character-set &optional limit
788 This function moves point backward, skipping characters that match
789 @var{character-set}, until @var{limit}. It is just like
790 @code{skip-chars-forward} except for the direction of motion.
792 The return value indicates the distance traveled. It is an integer that
800 It is often useful to move point ``temporarily'' within a localized
801 portion of the program, or to switch buffers temporarily. This is
802 called an @dfn{excursion}, and it is done with the @code{save-excursion}
803 special form. This construct initially remembers the identity of the
804 current buffer, and its values of point and the mark, and restores them
805 after the completion of the excursion.
807 The forms for saving and restoring the configuration of windows are
808 described elsewhere (see @ref{Window Configurations}, and @pxref{Frame
811 @defspec save-excursion body@dots{}
812 @cindex mark excursion
813 @cindex point excursion
814 The @code{save-excursion} special form saves the identity of the current
815 buffer and the values of point and the mark in it, evaluates
816 @var{body}, and finally restores the buffer and its saved values of
817 point and the mark. All three saved values are restored even in case of
818 an abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}).
820 The @code{save-excursion} special form is the standard way to switch
821 buffers or move point within one part of a program and avoid affecting
822 the rest of the program. It is used more than 4000 times in the Lisp
825 @code{save-excursion} does not save the values of point and the mark for
826 other buffers, so changes in other buffers remain in effect after
827 @code{save-excursion} exits.
829 @cindex window excursions
830 Likewise, @code{save-excursion} does not restore window-buffer
831 correspondences altered by functions such as @code{switch-to-buffer}.
832 One way to restore these correspondences, and the selected window, is to
833 use @code{save-window-excursion} inside @code{save-excursion}
834 (@pxref{Window Configurations}).
836 The value returned by @code{save-excursion} is the result of the last
837 form in @var{body}, or @code{nil} if no body forms were given.
841 (save-excursion @var{forms})
843 (let ((old-buf (current-buffer))
844 (old-pnt (point-marker))
846 (old-mark (copy-marker (mark-marker))))
852 (set-marker (mark-marker) old-mark)))
857 @strong{Warning:} Ordinary insertion of text adjacent to the saved
858 point value relocates the saved value, just as it relocates all markers.
859 More precisely, the saved value is a marker with insertion type
860 @code{nil}. @xref{Marker Insertion Types}. Therefore, when the saved
861 point value is restored, it normally comes before the inserted text.
863 Although @code{save-excursion} saves the location of the mark, it does
864 not prevent functions which modify the buffer from setting
865 @code{deactivate-mark}, and thus causing the deactivation of the mark
866 after the command finishes. @xref{The Mark}.
871 @cindex restriction (in a buffer)
872 @cindex accessible portion (of a buffer)
874 @dfn{Narrowing} means limiting the text addressable by Emacs editing
875 commands to a limited range of characters in a buffer. The text that
876 remains addressable is called the @dfn{accessible portion} of the
879 Narrowing is specified with two buffer positions which become the
880 beginning and end of the accessible portion. For most editing commands
881 and most Emacs primitives, these positions replace the values of the
882 beginning and end of the buffer. While narrowing is in effect, no text
883 outside the accessible portion is displayed, and point cannot move
884 outside the accessible portion.
886 Values such as positions or line numbers, which usually count from the
887 beginning of the buffer, do so despite narrowing, but the functions
888 which use them refuse to operate on text that is inaccessible.
890 The commands for saving buffers are unaffected by narrowing; they save
891 the entire buffer regardless of any narrowing.
893 If you need to display in a single buffer several very different
894 types of text, consider using an alternative facility described in
897 @deffn Command narrow-to-region start end
898 This function sets the accessible portion of the current buffer to start
899 at @var{start} and end at @var{end}. Both arguments should be character
902 In an interactive call, @var{start} and @var{end} are set to the bounds
903 of the current region (point and the mark, with the smallest first).
906 @deffn Command narrow-to-page &optional move-count
907 This function sets the accessible portion of the current buffer to
908 include just the current page. An optional first argument
909 @var{move-count} non-@code{nil} means to move forward or backward by
910 @var{move-count} pages and then narrow to one page. The variable
911 @code{page-delimiter} specifies where pages start and end
912 (@pxref{Standard Regexps}).
914 In an interactive call, @var{move-count} is set to the numeric prefix
920 This function cancels any narrowing in the current buffer, so that the
921 entire contents are accessible. This is called @dfn{widening}.
922 It is equivalent to the following expression:
925 (narrow-to-region 1 (1+ (buffer-size)))
929 @defspec save-restriction body@dots{}
930 This special form saves the current bounds of the accessible portion,
931 evaluates the @var{body} forms, and finally restores the saved bounds,
932 thus restoring the same state of narrowing (or absence thereof) formerly
933 in effect. The state of narrowing is restored even in the event of an
934 abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}).
935 Therefore, this construct is a clean way to narrow a buffer temporarily.
937 The value returned by @code{save-restriction} is that returned by the
938 last form in @var{body}, or @code{nil} if no body forms were given.
940 @c Wordy to avoid overfull hbox. --rjc 16mar92
941 @strong{Caution:} it is easy to make a mistake when using the
942 @code{save-restriction} construct. Read the entire description here
945 If @var{body} changes the current buffer, @code{save-restriction} still
946 restores the restrictions on the original buffer (the buffer whose
947 restrictions it saved from), but it does not restore the identity of the
950 @code{save-restriction} does @emph{not} restore point and the mark; use
951 @code{save-excursion} for that. If you use both @code{save-restriction}
952 and @code{save-excursion} together, @code{save-excursion} should come
953 first (on the outside). Otherwise, the old point value would be
954 restored with temporary narrowing still in effect. If the old point
955 value were outside the limits of the temporary narrowing, this would
956 fail to restore it accurately.
958 Here is a simple example of correct use of @code{save-restriction}:
962 ---------- Buffer: foo ----------
963 This is the contents of foo
964 This is the contents of foo
965 This is the contents of foo@point{}
966 ---------- Buffer: foo ----------
974 (narrow-to-region 1 (point))
975 (goto-char (point-min))
976 (replace-string "foo" "bar")))
978 ---------- Buffer: foo ----------
979 This is the contents of bar
980 This is the contents of bar
981 This is the contents of foo@point{}
982 ---------- Buffer: foo ----------
988 arch-tag: 56e8ff26-4ffe-4832-a141-7e991a2d0f87