Mercurial > emacs
view lispref/markers.texi @ 73331:f21883dcffa9
Merge from upstream, upto version 5.22.
After 5.0:
`cperl-add-tags-recurse-noxs-fullpath': new function (for -batch mode)
After 5.1:
;; Major edit. Summary of most visible changes:
;; a) Multiple <<HERE per line allowed.
;; b) Handles multiline subroutine declaration headers (with comments).
;; (The exception is `cperl-etags' - but it is not used in the rest
;; of the mode.)
;; c) Fontifies multiline my/our declarations (even with comments,
;; and with legacy `font-lock').
;; d) Major speedup of syntaxification, both immediate and postponed
;; (3.5x to 15x [for different CPUs and versions of Emacs] on the
;; huge real-life document I tested).
;; e) New bindings, edits to imenu.
;; f) "_" is made into word-char during fontification/syntaxification;
;; some attempts to recognize non-word "_" during other operations too.
;; g) Detect bug in Emacs with `looking-at' inside `narrow' and bulk out.
;; h) autoload some more perldoc-related stuff
;; i) Some new convenience features: ISpell POD/HEREDOCs, narrow-to-HEREDOC
;; j) Attempt to incorporate XEmacs edits which reached me
Fine-grained changelog:
`cperl-hook-after-change': New configuration variable
`cperl-vc-sccs-header': Likewise.
`cperl-vc-sccs-header': Likewise.
`cperl-vc-header-alist': Default via two preceding variables
`cperl-invalid-face': Remove double quoting under XEmacs
(still needed under 21.2)
`cperl-tips': Update URLs for resources
`cperl-problems': Likewise.
`cperl-praise': Mention new features
New C-c key bindings: for `cperl-find-bad-style',
`cperl-pod-spell', `cperl-here-doc-spell', `cperl-narrow-to-here-doc',
`cperl-perdoc', `cperl-perldoc-at-point'
CPerl Mode menu changes: "Fix style by spaces", "Imenu on Perl Info"
moved, new submenu of Tools with Ispell entries and narrowing.
`cperl-after-sub-regexp': New defsubst
`cperl-imenu--function-name-regexp-perl': Use `cperl-after-sub-regexp',
Allows heads up to head4
Allow "package;"
`defun-prompt-regexp': Use `cperl-after-sub-regexp',
`paren-backwards-message': ??? Something for XEmacs???
`cperl-mode': Never auto-switch abbrev-mode off
Try to allow '_' be non-word char
Do not use `font-lock-unfontify-region-function' on XEmacs
Reset syntax cache on mode start
Support multiline facification (even
on legacy `font-lock')
`cperl-facemenu-add-face-function': ??? Some contributed code ???
`cperl-after-change-function': Since `font-lock' and `lazy-lock'
refuse to inform us whether the fontification is due to lazy
calling or due to edit to a buffer, install our own hook
(controlled by `cperl-hook-after-change')
`cperl-electric-pod': =cut may have been recognized as start
`cperl-block-p': Moved, updated for attributes
`cperl-calculate-indent': Try to allow '_' be non-word char
Support subs with attributes
`cperl-where-am-i': Queit (?) a warning
`cperl-cached-syntax-table' New function
`cperl-forward-re': Use `cperl-cached-syntax-table'
`cperl-unwind-to-safe': Recognize `syntax-type' property
changing in a middle of line
`cperl-find-sub-attrs': New function
`cperl-find-pods-heres': Allow many <<EOP per line
Allow subs with attributes
Major speedups (3.5x..15x on a real-life
test file nph-proxy.pl)
Recognize "extproc " (OS/2)
case-folded and only at start
/x on s///x with empty replacement was
not recognized
Better comments
`cperl-after-block-p': Remarks on diff with `cperl-block-p'
Allow subs with attributes, labels
Do not confuse "else::foo" with "else"
Minor optimizations...
`cperl-after-expr-p': Try to allow '_' be non-word char
`cperl-fill-paragraph': Try to detect a major bug in Emacs
with `looking-at' inside `narrow' and bulk out if found
`cperl-imenu--create-perl-index': Updates for new
`cperl-imenu--function-name-regexp-perl'
`cperl-outline-level': Likewise.
`cperl-init-faces': Allow multiline subroutine headers
and my/our declarations, and ones with comments
Allow subroutine attributes
`cperl-imenu-on-info': Better docstring.
`cperl-etags' Rudimentary support for attributes
Support for packages and "package;"
`cperl-add-tags-recurse-noxs': Better (?) docstring
`cperl-add-tags-recurse-noxs-fullpath': Likewise.
`cperl-tags-hier-init': Misprint for `fboundp' fixed
`cperl-not-bad-style-regexp': Try to allow '_' be non-word char
`cperl-perldoc': Add autoload
`cperl-perldoc-at-point': Likewise.
`cperl-here-doc-spell': New function
`cperl-pod-spell': Likewise.
`cperl-map-pods-heres': Likewise.
`cperl-get-here-doc-region': Likewise.
`cperl-font-lock-fontify-region-function': Likewise (backward compatibility
for legacy `font-lock')
`cperl-font-lock-unfontify-region-function': Fix style
`cperl-fontify-syntaxically': Recognize and optimize away
deferred calls with no-change. Governed by `cperl-hook-after-change'
`cperl-fontify-update': Recognize that syntaxification region
can be larger than fontification one.
XXXX we leave `cperl-postpone' property, so this is quadratic...
`cperl-fontify-update-bad': Temporary placeholder until
it is clear how to implement `cperl-fontify-update'.
`cperl-time-fontification': New function
`attrib-group': New text attribute
`multiline': New value: `syntax-type' text attribute
After 5.2:
`cperl-emulate-lazy-lock': New function
`cperl-fontify-syntaxically': Would skip large regions
Add `cperl-time-fontification', `cperl-emulate-lazy-lock' to menu
Some globals were declared, but uninitialized
After 5.3, 5.4:
`cperl-facemenu-add-face-function': Add docs, fix U<>
Copyright message updated.
`cperl-init-faces': Work around a bug in `font-lock'. May slow
facification down a bit.
Misprint for my|our|local for old `font-lock'
"our" was not fontified same as "my|local"
Highlight variables after "my" etc even in
a middle of an expression
Do not facify multiple variables after my etc
unless parentheses are present
After 5.5, 5.6
`cperl-fontify-syntaxically': after-change hook could reset
`cperl-syntax-done-to' to a middle of line; unwind to BOL.
After 5.7:
`cperl-init-faces': Allow highlighting of local ($/)
`cperl-problems-old-emaxen': New variable (for the purpose of DOCSTRING).
`cperl-problems': Remove fixed problems.
`cperl-find-pods-heres': Recognize #-comments in m##x too
Recognize charclasses (unless delimiter is \).
`cperl-fontify-syntaxically': Unwinding to safe was done in wrong order
`cperl-regexp-scan': Update docs
`cperl-beautify-regexp-piece': use information got from regexp scan
After 5.8:
Major user visible changes:
Recognition and fontification of character classes in RExen.
Variable indentation of RExen according to groups
`cperl-find-pods-heres': Recognize POSIX classes in REx charclasses
Fontify REx charclasses in variable-name face
Fontify POSIX charclasses in "type" face
Fontify unmatched "]" in function-name face
Mark first-char of HERE-doc as `front-sticky'
Reset `front-sticky' property when needed
`cperl-calculate-indent': Indents //x -RExen accordning to parens level
`cperl-to-comment-or-eol': Recognize ends of `syntax-type' constructs
`cperl-backward-to-noncomment': Recognize stringy `syntax-type' constructs
Support `narrow'ed buffers.
`cperl-praise': Remove a reservation
`cperl-make-indent': New function
`cperl-indent-for-comment': Use `cperl-make-indent'
`cperl-indent-line': Likewise.
`cperl-lineup': Likewise.
`cperl-beautify-regexp-piece': Likewise.
`cperl-contract-level': Likewise.
`cperl-toggle-set-debug-unwind': New function
New menu entry for this
`fill-paragraph-function': Use when `boundp'
`cperl-calculate-indent': Take into account groups when indenting RExen
`cperl-to-comment-or-eol': Recognize # which end a string
`cperl-modify-syntax-type': Make only syntax-table property non-sticky
`cperl-fill-paragraph': Return t: needed for `fill-paragraph-function'
`cperl-fontify-syntaxically': More clear debugging message
`cperl-pod2man-build-command': XEmacs portability: check `Man-filter-list'
`cperl-init-faces': More complicated highlight even on XEmacs (new)
Merge cosmetic changes from XEmacs
After 5.9:
`cperl-1+': Moved to before the first use
`cperl-1-': Likewise.
After 5.10:
This code may lock Emacs hard!!! Use on your own risk!
`cperl-font-locking': New internal variable
`cperl-beginning-of-property': New function
`cperl-calculate-indent': Use `cperl-beginning-of-property'
instead of `previous-single-property-change'
`cperl-unwind-to-safe': Likewise.
`cperl-after-expr-p': Likewise.
`cperl-get-here-doc-region': Likewise.
`cperl-font-lock-fontify-region-function': Likewise.
`cperl-to-comment-or-eol': Do not call `cperl-update-syntaxification'
recursively
Bound `next-single-property-change'
via `point-max'
`cperl-unwind-to-safe': Bound likewise
`cperl-font-lock-fontify-region-function': Likewise.
`cperl-find-pods-heres': Mark as recursive for `cperl-to-comment-or-eol'
Initialization of
`cperl-font-lock-multiline-start' could be missed if the "main"
fontification did not run due to the keyword being already fontified.
`cperl-pod-spell': Return t from do-one-chunk function
`cperl-map-pods-heres': Stop when the worker returns nil
Call `cperl-update-syntaxification'
`cperl-get-here-doc-region': Call `cperl-update-syntaxification'
`cperl-get-here-doc-delim': Remove unused function
After 5.11:
The possible lockup of Emacs (introduced in 5.10) fixed
`cperl-unwind-to-safe': `cperl-beginning-of-property' won't return nil
`cperl-syntaxify-for-menu': New customization variable
`cperl-select-this-pod-or-here-doc': New function
`cperl-get-here-doc-region': Extra argument
Do not adjust pos by 1
New menu entries (Perl/Tools): Selection of current POD or HERE-DOC section
(Debugging CPerl:) backtrace on fontification
After 5.12:
`cperl-cached-syntax-table': use `car-safe'
`cperl-forward-re': Remove spurious argument SET-ST
Add documentation
`cperl-forward-group-in-re': New function
`cperl-find-pods-heres': Find and highlight (?{}) blocks in RExen
(XXXX Temporary (?) hack is to syntax-mark them as comment)
After 5.13:
`cperl-string-syntax-table': Make { and } not-grouping
(Sometimes they ARE grouping in RExen, but matching them would only
confuse in many situations when they are not)
`beginning-of-buffer': Replaced two occurences with goto-char...
`cperl-calculate-indent': `char-after' could be nil...
`cperl-find-pods-heres': REx can start after "[" too
Hightlight (??{}) in RExen too
`cperl-maybe-white-and-comment-rex': New constant
`cperl-white-and-comment-rex': Likewise.
XXXX Not very efficient, but hard to make
better while keeping 1 group
After 5.13:
`cperl-find-pods-heres': $foo << identifier() is not a HERE-DOC
Likewise for 1 << identifier
After 5.14:
`cperl-find-pods-heres': Different logic for $foo .= <<EOF etc
Error-less condition-case could fail
`cperl-font-lock-fontify-region-function': Likewise.
`cperl-init-faces': Likewise.
After 5.15:
`cperl-find-pods-heres': Support property REx-part2
`cperl-calculate-indent': Likewise.
Don't special-case REx with non-empty 1st line
`cperl-find-pods-heres': In RExen, highlight non-literal backslashes
Invert highlighting of charclasses:
now the envelop is highlighted
Highlight many others 0-length builtins
`cperl-praise': Mention indenting and highlight in RExen
After 5.15:
`cperl-find-pods-heres': Highlight capturing parens in REx
After 5.16:
`cperl-find-pods-heres': Highlight '|' for alternation
Initialize `font-lock-warning-face' if not present
`cperl-find-pods-heres': Use `font-lock-warning-face' instead of
`font-lock-function-name-face'
`cperl-look-at-leading-count': Likewise.
`cperl-find-pods-heres': localize `font-lock-variable-name-face'
`font-lock-keyword-face' (needed for
batch processing) etc
Use `font-lock-builtin-face' for builtin in REx
Now `font-lock-variable-name-face'
is used for interpolated variables
Use "talking aliases" for faces inside REx
Highlight parts of REx (except in charclasses)
according to the syntax and/or semantic
Syntax-mark a {}-part of (?{}) as "comment"
(it was the ()-part)
Better logic to distinguish what is what in REx
`cperl-tips-faces': Document REx highlighting
`cperl-praise': Mention REx syntax highlight etc.
After 5.17:
`cperl-find-sub-attrs': Would not always manage to print error message
`cperl-find-pods-heres': localize `font-lock-constant-face'
After 5.18:
`cperl-find-pods-heres': Misprint in REx for parsing REx
Very minor optimization
`my-cperl-REx-modifiers-face' got quoted
Recognize "print $foo <<END" as HERE-doc
Put `REx-interpolated' text attribute if needed
`cperl-invert-if-unless-modifiers': New function
`cperl-backward-to-start-of-expr': Likewise.
`cperl-forward-to-end-of-expr': Likewise.
`cperl-invert-if-unless': Works in "the opposite way" too
Cursor position on return is on the switch-word
Indents comments better
`REx-interpolated': New text attribute
`cperl-next-interpolated-REx': New function
`cperl-next-interpolated-REx-0': Likewise.
`cperl-next-interpolated-REx-1': Likewise.
"\C-c\C-x", "\C-c\C-y", "\C-c\C-v": New keybinding for these functions
Perl/Regexp menu: 3 new entries for `cperl-next-interpolated-REx'
`cperl-praise': Mention finded interpolated RExen
After 5.19:
`cperl-init-faces': Highlight %$foo, @$foo too
`cperl-short-docs': Better docs for system, exec
`cperl-find-pods-heres': Better detect << after print {FH} <<EOF etc.
Would not find HERE-doc ended by EOF without NL
`cperl-short-docs': Correct not-doubled \-escapes
start block: Put some `defvar' for stuff gone from XEmacs
After 5.20:
initial comment: Extend copyright, fix email address
`cperl-indent-comment-at-column-0': New customization variable
`cperl-comment-indent': Indentation after $#a would increasy by 1
`cperl-mode': Make `defun-prompt-regexp' grok BEGIN/END etc
`cperl-find-pods-heres': Mark CODE of s///e as `syntax-type' `multiline'
`cperl-at-end-of-expr': Would fail if @BAR=12 follows after ";"
`cperl-init-faces': If `cperl-highlight-variables-indiscriminately'
highlight $ in $foo too (UNTESTED)
`cperl-set-style': Docstring missed some available styles
toplevel: Menubar/Perl/Indent-Styles had FSF, now K&R
Change "Current" to "Memorize Current"
`cperl-indent-wrt-brace': New customization variable; the default is
as for pre-5.2 version
`cperl-styles-entries': Keep `cperl-extra-newline-before-brace-multiline'
`cperl-style-alist': Likewise.
`cperl-fix-line-spacing': Support `cperl-merge-trailing-else' being nil,
and `cperl-extra-newline-before-brace' etc
being t
`cperl-indent-exp': Plans B and C to find continuation blocks even
if `cperl-extra-newline-before-brace' is t
After 5.21:
Improve some docstrings concerning indentation.
`cperl-indent-rules-alist': New variable
`cperl-sniff-for-indent': New function name
(separated from `cperl-calculate-indent')
`cperl-calculate-indent': Separated the sniffer and the indenter;
uses `cperl-sniff-for-indent' now
`cperl-comment-indent': Test for `cperl-indent-comment-at-column-0'
was inverted;
Support `comment-column' = 0
author | Stefan Monnier <monnier@iro.umontreal.ca> |
---|---|
date | Wed, 11 Oct 2006 06:47:35 +0000 |
parents | 17479ca5deda |
children | 6d19c76d81c5 8a8e69664178 |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the GNU Emacs Lisp Reference Manual. @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2002, 2003, @c 2004, 2005, 2006 Free Software Foundation, Inc. @c See the file elisp.texi for copying conditions. @setfilename ../info/markers @node Markers, Text, Positions, Top @chapter Markers @cindex markers A @dfn{marker} is a Lisp object used to specify a position in a buffer relative to the surrounding text. A marker changes its offset from the beginning of the buffer automatically whenever text is inserted or deleted, so that it stays with the two characters on either side of it. @menu * Overview of Markers:: The components of a marker, and how it relocates. * Predicates on Markers:: Testing whether an object is a marker. * Creating Markers:: Making empty markers or markers at certain places. * Information from Markers:: Finding the marker's buffer or character position. * Marker Insertion Types:: Two ways a marker can relocate when you insert where it points. * Moving Markers:: Moving the marker to a new buffer or position. * The Mark:: How "the mark" is implemented with a marker. * The Region:: How to access "the region". @end menu @node Overview of Markers @section Overview of Markers A marker specifies a buffer and a position in that buffer. The marker can be used to represent a position in the functions that require one, just as an integer could be used. In that case, the marker's buffer is normally ignored. Of course, a marker used in this way usually points to a position in the buffer that the function operates on, but that is entirely the programmer's responsibility. @xref{Positions}, for a complete description of positions. A marker has three attributes: the marker position, the marker buffer, and the insertion type. The marker position is an integer that is equivalent (at a given time) to the marker as a position in that buffer. But the marker's position value can change often during the life of the marker. Insertion and deletion of text in the buffer relocate the marker. The idea is that a marker positioned between two characters remains between those two characters despite insertion and deletion elsewhere in the buffer. Relocation changes the integer equivalent of the marker. @cindex marker relocation Deleting text around a marker's position leaves the marker between the characters immediately before and after the deleted text. Inserting text at the position of a marker normally leaves the marker either in front of or after the new text, depending on the marker's @dfn{insertion type} (@pxref{Marker Insertion Types})---unless the insertion is done with @code{insert-before-markers} (@pxref{Insertion}). @cindex marker garbage collection Insertion and deletion in a buffer must check all the markers and relocate them if necessary. This slows processing in a buffer with a large number of markers. For this reason, it is a good idea to make a marker point nowhere if you are sure you don't need it any more. Unreferenced markers are garbage collected eventually, but until then will continue to use time if they do point somewhere. @cindex markers as numbers Because it is common to perform arithmetic operations on a marker position, most of the arithmetic operations (including @code{+} and @code{-}) accept markers as arguments. In such cases, the marker stands for its current position. Here are examples of creating markers, setting markers, and moving point to markers: @example @group ;; @r{Make a new marker that initially does not point anywhere:} (setq m1 (make-marker)) @result{} #<marker in no buffer> @end group @group ;; @r{Set @code{m1} to point between the 99th and 100th characters} ;; @r{in the current buffer:} (set-marker m1 100) @result{} #<marker at 100 in markers.texi> @end group @group ;; @r{Now insert one character at the beginning of the buffer:} (goto-char (point-min)) @result{} 1 (insert "Q") @result{} nil @end group @group ;; @r{@code{m1} is updated appropriately.} m1 @result{} #<marker at 101 in markers.texi> @end group @group ;; @r{Two markers that point to the same position} ;; @r{are not @code{eq}, but they are @code{equal}.} (setq m2 (copy-marker m1)) @result{} #<marker at 101 in markers.texi> (eq m1 m2) @result{} nil (equal m1 m2) @result{} t @end group @group ;; @r{When you are finished using a marker, make it point nowhere.} (set-marker m1 nil) @result{} #<marker in no buffer> @end group @end example @node Predicates on Markers @section Predicates on Markers You can test an object to see whether it is a marker, or whether it is either an integer or a marker. The latter test is useful in connection with the arithmetic functions that work with both markers and integers. @defun markerp object This function returns @code{t} if @var{object} is a marker, @code{nil} otherwise. Note that integers are not markers, even though many functions will accept either a marker or an integer. @end defun @defun integer-or-marker-p object This function returns @code{t} if @var{object} is an integer or a marker, @code{nil} otherwise. @end defun @defun number-or-marker-p object This function returns @code{t} if @var{object} is a number (either integer or floating point) or a marker, @code{nil} otherwise. @end defun @node Creating Markers @section Functions that Create Markers When you create a new marker, you can make it point nowhere, or point to the present position of point, or to the beginning or end of the accessible portion of the buffer, or to the same place as another given marker. The next four functions all return markers with insertion type @code{nil}. @xref{Marker Insertion Types}. @defun make-marker This function returns a newly created marker that does not point anywhere. @example @group (make-marker) @result{} #<marker in no buffer> @end group @end example @end defun @defun point-marker This function returns a new marker that points to the present position of point in the current buffer. @xref{Point}. For an example, see @code{copy-marker}, below. @end defun @defun point-min-marker This function returns a new marker that points to the beginning of the accessible portion of the buffer. This will be the beginning of the buffer unless narrowing is in effect. @xref{Narrowing}. @end defun @defun point-max-marker @cindex end of buffer marker This function returns a new marker that points to the end of the accessible portion of the buffer. This will be the end of the buffer unless narrowing is in effect. @xref{Narrowing}. Here are examples of this function and @code{point-min-marker}, shown in a buffer containing a version of the source file for the text of this chapter. @example @group (point-min-marker) @result{} #<marker at 1 in markers.texi> (point-max-marker) @result{} #<marker at 15573 in markers.texi> @end group @group (narrow-to-region 100 200) @result{} nil @end group @group (point-min-marker) @result{} #<marker at 100 in markers.texi> @end group @group (point-max-marker) @result{} #<marker at 200 in markers.texi> @end group @end example @end defun @defun copy-marker marker-or-integer &optional insertion-type If passed a marker as its argument, @code{copy-marker} returns a new marker that points to the same place and the same buffer as does @var{marker-or-integer}. If passed an integer as its argument, @code{copy-marker} returns a new marker that points to position @var{marker-or-integer} in the current buffer. The new marker's insertion type is specified by the argument @var{insertion-type}. @xref{Marker Insertion Types}. If passed an integer argument less than 1, @code{copy-marker} returns a new marker that points to the beginning of the current buffer. If passed an integer argument greater than the length of the buffer, @code{copy-marker} returns a new marker that points to the end of the buffer. @example @group (copy-marker 0) @result{} #<marker at 1 in markers.texi> @end group @group (copy-marker 20000) @result{} #<marker at 7572 in markers.texi> @end group @end example An error is signaled if @var{marker} is neither a marker nor an integer. @end defun Two distinct markers are considered @code{equal} (even though not @code{eq}) to each other if they have the same position and buffer, or if they both point nowhere. @example @group (setq p (point-marker)) @result{} #<marker at 2139 in markers.texi> @end group @group (setq q (copy-marker p)) @result{} #<marker at 2139 in markers.texi> @end group @group (eq p q) @result{} nil @end group @group (equal p q) @result{} t @end group @end example @node Information from Markers @section Information from Markers This section describes the functions for accessing the components of a marker object. @defun marker-position marker This function returns the position that @var{marker} points to, or @code{nil} if it points nowhere. @end defun @defun marker-buffer marker This function returns the buffer that @var{marker} points into, or @code{nil} if it points nowhere. @example @group (setq m (make-marker)) @result{} #<marker in no buffer> @end group @group (marker-position m) @result{} nil @end group @group (marker-buffer m) @result{} nil @end group @group (set-marker m 3770 (current-buffer)) @result{} #<marker at 3770 in markers.texi> @end group @group (marker-buffer m) @result{} #<buffer markers.texi> @end group @group (marker-position m) @result{} 3770 @end group @end example @end defun @defun buffer-has-markers-at position This function returns @code{t} if one or more markers point at position @var{position} in the current buffer. @end defun @node Marker Insertion Types @section Marker Insertion Types @cindex insertion type of a marker When you insert text directly at the place where a marker points, there are two possible ways to relocate that marker: it can point before the inserted text, or point after it. You can specify which one a given marker should do by setting its @dfn{insertion type}. Note that use of @code{insert-before-markers} ignores markers' insertion types, always relocating a marker to point after the inserted text. @defun set-marker-insertion-type marker type This function sets the insertion type of marker @var{marker} to @var{type}. If @var{type} is @code{t}, @var{marker} will advance when text is inserted at its position. If @var{type} is @code{nil}, @var{marker} does not advance when text is inserted there. @end defun @defun marker-insertion-type marker This function reports the current insertion type of @var{marker}. @end defun Most functions that create markers, without an argument allowing to specify the insertion type, create them with insertion type @code{nil}. Also, the mark has, by default, insertion type @code{nil}. @node Moving Markers @section Moving Marker Positions This section describes how to change the position of an existing marker. When you do this, be sure you know whether the marker is used outside of your program, and, if so, what effects will result from moving it---otherwise, confusing things may happen in other parts of Emacs. @defun set-marker marker position &optional buffer This function moves @var{marker} to @var{position} in @var{buffer}. If @var{buffer} is not provided, it defaults to the current buffer. If @var{position} is less than 1, @code{set-marker} moves @var{marker} to the beginning of the buffer. If @var{position} is greater than the size of the buffer, @code{set-marker} moves marker to the end of the buffer. If @var{position} is @code{nil} or a marker that points nowhere, then @var{marker} is set to point nowhere. The value returned is @var{marker}. @example @group (setq m (point-marker)) @result{} #<marker at 4714 in markers.texi> @end group @group (set-marker m 55) @result{} #<marker at 55 in markers.texi> @end group @group (setq b (get-buffer "foo")) @result{} #<buffer foo> @end group @group (set-marker m 0 b) @result{} #<marker at 1 in foo> @end group @end example @end defun @defun move-marker marker position &optional buffer This is another name for @code{set-marker}. @end defun @node The Mark @section The Mark @cindex mark, the @cindex mark ring One special marker in each buffer is designated @dfn{the mark}. It specifies a position to bound a range of text for commands such as @code{kill-region} and @code{indent-rigidly}. Lisp programs should set the mark only to values that have a potential use to the user, and never for their own internal purposes. For example, the @code{replace-regexp} command sets the mark to the value of point before doing any replacements, because this enables the user to move back there conveniently after the replace is finished. Many commands are designed to operate on the text between point and the mark when called interactively. If you are writing such a command, don't examine the mark directly; instead, use @code{interactive} with the @samp{r} specification. This provides the values of point and the mark as arguments to the command in an interactive call, but permits other Lisp programs to specify arguments explicitly. @xref{Interactive Codes}. Each buffer has its own value of the mark that is independent of the value of the mark in other buffers. When a buffer is created, the mark exists but does not point anywhere. We consider this state as ``the absence of a mark in that buffer.'' Once the mark ``exists'' in a buffer, it normally never ceases to exist. However, it may become @dfn{inactive}, if Transient Mark mode is enabled. The variable @code{mark-active}, which is always buffer-local in all buffers, indicates whether the mark is active: non-@code{nil} means yes. A command can request deactivation of the mark upon return to the editor command loop by setting @code{deactivate-mark} to a non-@code{nil} value (but this causes deactivation only if Transient Mark mode is enabled). The main motivation for using Transient Mark mode is that this mode also enables highlighting of the region when the mark is active. @xref{Display}. In addition to the mark, each buffer has a @dfn{mark ring} which is a list of markers containing previous values of the mark. When editing commands change the mark, they should normally save the old value of the mark on the mark ring. The variable @code{mark-ring-max} specifies the maximum number of entries in the mark ring; once the list becomes this long, adding a new element deletes the last element. There is also a separate global mark ring, but that is used only in a few particular user-level commands, and is not relevant to Lisp programming. So we do not describe it here. @defun mark &optional force @cindex current buffer mark This function returns the current buffer's mark position as an integer, or @code{nil} if no mark has ever been set in this buffer. If Transient Mark mode is enabled, and @code{mark-even-if-inactive} is @code{nil}, @code{mark} signals an error if the mark is inactive. However, if @var{force} is non-@code{nil}, then @code{mark} disregards inactivity of the mark, and returns the mark position anyway (or @code{nil}). @end defun @defun mark-marker This function returns the current buffer's mark. This is the very marker that records the mark location inside Emacs, not a copy. Therefore, changing this marker's position will directly affect the position of the mark. Don't do it unless that is the effect you want. @example @group (setq m (mark-marker)) @result{} #<marker at 3420 in markers.texi> @end group @group (set-marker m 100) @result{} #<marker at 100 in markers.texi> @end group @group (mark-marker) @result{} #<marker at 100 in markers.texi> @end group @end example Like any marker, this marker can be set to point at any buffer you like. We don't recommend that you make it point at any buffer other than the one of which it is the mark. If you do, it will yield perfectly consistent, but rather odd, results. @end defun @ignore @deffn Command set-mark-command jump If @var{jump} is @code{nil}, this command sets the mark to the value of point and pushes the previous value of the mark on the mark ring. The message @samp{Mark set} is also displayed in the echo area. If @var{jump} is not @code{nil}, this command sets point to the value of the mark, and sets the mark to the previous saved mark value, which is popped off the mark ring. This function is @emph{only} intended for interactive use. @end deffn @end ignore @defun set-mark position This function sets the mark to @var{position}, and activates the mark. The old value of the mark is @emph{not} pushed onto the mark ring. @strong{Please note:} Use this function only if you want the user to see that the mark has moved, and you want the previous mark position to be lost. Normally, when a new mark is set, the old one should go on the @code{mark-ring}. For this reason, most applications should use @code{push-mark} and @code{pop-mark}, not @code{set-mark}. Novice Emacs Lisp programmers often try to use the mark for the wrong purposes. The mark saves a location for the user's convenience. An editing command should not alter the mark unless altering the mark is part of the user-level functionality of the command. (And, in that case, this effect should be documented.) To remember a location for internal use in the Lisp program, store it in a Lisp variable. For example: @example @group (let ((beg (point))) (forward-line 1) (delete-region beg (point))). @end group @end example @end defun @c for interactive use only @ignore @deffn Command exchange-point-and-mark This function exchanges the positions of point and the mark. It is intended for interactive use. @end deffn @end ignore @defun push-mark &optional position nomsg activate This function sets the current buffer's mark to @var{position}, and pushes a copy of the previous mark onto @code{mark-ring}. If @var{position} is @code{nil}, then the value of point is used. @code{push-mark} returns @code{nil}. The function @code{push-mark} normally @emph{does not} activate the mark. To do that, specify @code{t} for the argument @var{activate}. A @samp{Mark set} message is displayed unless @var{nomsg} is non-@code{nil}. @end defun @defun pop-mark This function pops off the top element of @code{mark-ring} and makes that mark become the buffer's actual mark. This does not move point in the buffer, and it does nothing if @code{mark-ring} is empty. It deactivates the mark. The return value is not meaningful. @end defun @defopt transient-mark-mode @cindex Transient Mark mode This variable if non-@code{nil} enables Transient Mark mode, in which every buffer-modifying primitive sets @code{deactivate-mark}. The consequence of this is that commands that modify the buffer normally make the mark inactive. Lisp programs can set @code{transient-mark-mode} to @code{only} to enable Transient Mark mode for the following command only. During that following command, the value of @code{transient-mark-mode} is @code{identity}. If it is still @code{identity} at the end of the command, it changes to @code{nil}. @end defopt @defopt mark-even-if-inactive If this is non-@code{nil}, Lisp programs and the Emacs user can use the mark even when it is inactive. This option affects the behavior of Transient Mark mode. When the option is non-@code{nil}, deactivation of the mark turns off region highlighting, but commands that use the mark behave as if the mark were still active. @end defopt @defvar deactivate-mark If an editor command sets this variable non-@code{nil}, then the editor command loop deactivates the mark after the command returns (if Transient Mark mode is enabled). All the primitives that change the buffer set @code{deactivate-mark}, to deactivate the mark when the command is finished. To write Lisp code that modifies the buffer without causing deactivation of the mark at the end of the command, bind @code{deactivate-mark} to @code{nil} around the code that does the modification. For example: @example (let (deactivate-mark) (insert " ")) @end example @end defvar @defun deactivate-mark This function deactivates the mark, if Transient Mark mode is enabled. Otherwise it does nothing. @end defun @defvar mark-active The mark is active when this variable is non-@code{nil}. This variable is always buffer-local in each buffer. @end defvar @defvar activate-mark-hook @defvarx deactivate-mark-hook These normal hooks are run, respectively, when the mark becomes active and when it becomes inactive. The hook @code{activate-mark-hook} is also run at the end of a command if the mark is active and it is possible that the region may have changed. @end defvar @defvar mark-ring The value of this buffer-local variable is the list of saved former marks of the current buffer, most recent first. @example @group mark-ring @result{} (#<marker at 11050 in markers.texi> #<marker at 10832 in markers.texi> @dots{}) @end group @end example @end defvar @defopt mark-ring-max The value of this variable is the maximum size of @code{mark-ring}. If more marks than this are pushed onto the @code{mark-ring}, @code{push-mark} discards an old mark when it adds a new one. @end defopt @node The Region @section The Region @cindex region, the The text between point and the mark is known as @dfn{the region}. Various functions operate on text delimited by point and the mark, but only those functions specifically related to the region itself are described here. The next two functions signal an error if the mark does not point anywhere. If Transient Mark mode is enabled and @code{mark-even-if-inactive} is @code{nil}, they also signal an error if the mark is inactive. @defun region-beginning This function returns the position of the beginning of the region (as an integer). This is the position of either point or the mark, whichever is smaller. @end defun @defun region-end This function returns the position of the end of the region (as an integer). This is the position of either point or the mark, whichever is larger. @end defun Few programs need to use the @code{region-beginning} and @code{region-end} functions. A command designed to operate on a region should normally use @code{interactive} with the @samp{r} specification to find the beginning and end of the region. This lets other Lisp programs specify the bounds explicitly as arguments. (@xref{Interactive Codes}.) @ignore arch-tag: b1ba2e7a-a0f3-4c5e-875c-7d8e22d73299 @end ignore