# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1150471083 0
# Node ID c46f87481f13c24813fa9cac7c7663ba0caf00ac
# Parent  a5f28e1a3fa6af1e16213abe8aa3da42437d000e
(Using Interactive): Explain problem of markers, etc., in command-history.

diff -r a5f28e1a3fa6 -r c46f87481f13 lispref/commands.texi
--- a/lispref/commands.texi	Fri Jun 16 15:15:30 2006 +0000
+++ b/lispref/commands.texi	Fri Jun 16 15:18:03 2006 +0000
@@ -233,6 +233,20 @@
  (let ((string (read-string "Foo: " nil 'my-history)))
    (list (region-beginning) (region-end) string)))
 @end smallexample
+
+@strong{Warning:} the argument values should not include any data
+types that can't be printed and then read.  Some facilities save
+@code{command-history} in a file to be read in the subsequent
+sessions; if a command's arguments contain a data type that prints
+using @samp{#<@dots{}>} syntax, those facilities won't work.
+
+There are, however, a few exceptions: it is ok to use a limited set of
+expressions such as @code{(point)}, @code{(mark)},
+@code{(region-beginning)}, and @code{(region-end)}, because Emacs
+recognizes them specially and puts the expression (rather than its
+value) into the command history.  To see whether the expression you
+wrote is one of these exceptions, run the command, then examine
+@code{(car command-history)}.
 @end itemize
 
 @cindex examining the @code{interactive} form