# HG changeset patch
# User Juri Linkov <juri@jurta.org>
# Date 1103106146 0
# Node ID f23a14da8463f2a90b719f37b74f3cf5cfed7628
# Parent  7fed010105d94c07a04ef77ebead5b6772a943bb
(Transient Mark, Mark Ring): M-< and other
movement commands don't set mark in Transient Mark mode
if mark is active.

diff -r 7fed010105d9 -r f23a14da8463 man/mark.texi
--- a/man/mark.texi	Wed Dec 15 10:10:54 2004 +0000
+++ b/man/mark.texi	Wed Dec 15 10:22:26 2004 +0000
@@ -191,7 +191,9 @@
 (@code{exchange-point-and-mark}).
 
 @item
-@kbd{C-s} when the mark is active does not alter the mark.
+Commands that normally set the mark before moving long distances (like
+@kbd{M-<} and @kbd{C-s}) do not alter the mark in Transient Mark mode
+when the mark is active.
 
 @item
 Some commands operate on the region if a region is active.  For
@@ -384,9 +386,10 @@
   Many commands that can move long distances, such as @kbd{M-<}
 (@code{beginning-of-buffer}), start by setting the mark and saving the
 old mark on the mark ring.  This is to make it easier for you to move
-back later.  Searches set the mark if they move point.  You can tell
-when a command sets the mark because it displays @samp{Mark set} in the
-echo area.
+back later.  Searches set the mark if they move point.  However, in
+Transient Mark mode, these commands do not set the mark when the mark
+is already active.  You can tell when a command sets the mark because
+it displays @samp{Mark set} in the echo area.
 
   If you want to move back to the same place over and over, the mark
 ring may not be convenient enough.  If so, you can record the position