diff options
| -rw-r--r-- | doc/lispref/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/lispref/markers.texi | 13 |
2 files changed, 16 insertions, 2 deletions
diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 999714eaf73..68a8f0e4345 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog | |||
| @@ -1,3 +1,8 @@ | |||
| 1 | 2012-03-07 Glenn Morris <rgm@gnu.org> | ||
| 2 | |||
| 3 | * markers.texi (The Region): | ||
| 4 | Briefly mention use-empty-active-region and region-active-p. | ||
| 5 | |||
| 1 | 2012-03-07 Chong Yidong <cyd@gnu.org> | 6 | 2012-03-07 Chong Yidong <cyd@gnu.org> |
| 2 | 7 | ||
| 3 | * text.texi (Buffer Contents): Don't duplicate explanation of | 8 | * text.texi (Buffer Contents): Don't duplicate explanation of |
diff --git a/doc/lispref/markers.texi b/doc/lispref/markers.texi index 653418e8345..689d5d3bb1f 100644 --- a/doc/lispref/markers.texi +++ b/doc/lispref/markers.texi | |||
| @@ -58,8 +58,6 @@ with @code{insert-before-markers} (@pxref{Insertion}). | |||
| 58 | relocate them if necessary. This slows processing in a buffer with a | 58 | relocate them if necessary. This slows processing in a buffer with a |
| 59 | large number of markers. For this reason, it is a good idea to make a | 59 | large number of markers. For this reason, it is a good idea to make a |
| 60 | marker point nowhere if you are sure you don't need it any more. | 60 | marker point nowhere if you are sure you don't need it any more. |
| 61 | Unreferenced markers are garbage collected eventually, but until then | ||
| 62 | will continue to use time if they do point somewhere. | ||
| 63 | 61 | ||
| 64 | @cindex markers as numbers | 62 | @cindex markers as numbers |
| 65 | Because it is common to perform arithmetic operations on a marker | 63 | Because it is common to perform arithmetic operations on a marker |
| @@ -636,6 +634,9 @@ more marks than this are pushed onto the @code{mark-ring}, | |||
| 636 | @code{push-mark} discards an old mark when it adds a new one. | 634 | @code{push-mark} discards an old mark when it adds a new one. |
| 637 | @end defopt | 635 | @end defopt |
| 638 | 636 | ||
| 637 | @c There is also global-mark-ring-max, but this chapter explicitly | ||
| 638 | @c does not talk about the global mark. | ||
| 639 | |||
| 639 | @node The Region | 640 | @node The Region |
| 640 | @section The Region | 641 | @section The Region |
| 641 | @cindex region (between point and mark) | 642 | @cindex region (between point and mark) |
| @@ -673,4 +674,12 @@ This function returns @code{t} if Transient Mark mode is enabled, the | |||
| 673 | mark is active, and there is a valid region in the buffer. This | 674 | mark is active, and there is a valid region in the buffer. This |
| 674 | function is intended to be used by commands that operate on the | 675 | function is intended to be used by commands that operate on the |
| 675 | region, instead of on text near point, when the mark is active. | 676 | region, instead of on text near point, when the mark is active. |
| 677 | |||
| 678 | A region is valid if it has a non-zero size, or if the user option | ||
| 679 | @code{use-empty-active-region} is non-@code{nil} (by default, it is | ||
| 680 | @code{nil}). The function @code{region-active-p} is similar to | ||
| 681 | @code{use-region-p}, but considers all regions as valid. In most | ||
| 682 | cases, you should not use @code{region-active-p}, since if the region | ||
| 683 | is empty it is often more appropriate to operate on point. | ||
| 676 | @end defun | 684 | @end defun |
| 685 | |||