diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2016-01-12 21:21:12 +0200 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2016-01-12 21:21:12 +0200 |
| commit | a71783bd6c63b5d6a169ce28902da5185e294f30 (patch) | |
| tree | afd5e59d0150a7228bcc4bc6de0e5bb7cd57ddfd | |
| parent | bba8c532fa025a3efffdcccd40bfe66a4e9effd2 (diff) | |
Update documentation of 'deactivate-mark'.
* doc/lispref/markers.texi (The Mark): Document that
'deactivate-mark' is now buffer-local when set.
| -rw-r--r-- | doc/lispref/markers.texi | 2 | ||||
| -rw-r--r-- | etc/NEWS | 3 |
2 files changed, 4 insertions, 1 deletions
diff --git a/doc/lispref/markers.texi b/doc/lispref/markers.texi index bf18543138..1c904666cb 100644 --- a/doc/lispref/markers.texi +++ b/doc/lispref/markers.texi @@ -576,7 +576,7 @@ 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. +command is finished. Setting this variable makes it buffer-local. To write Lisp code that modifies the buffer without causing deactivation of the mark at the end of the command, bind @@ -1232,11 +1232,14 @@ If you want the old behavior of calling the function in the buffer from which the minibuffer was entered, use the new argument `switch-buffer' to `completion-table-dynamic'. +--- ** window-configurations no longer record the buffers' marks. +--- ** inhibit-modification-hooks now also inhibits lock-file checks, as well as active region handling. ++++ ** deactivate-mark is now buffer-local. ** `cl-the' now asserts that its argument is of the given type. |