aboutsummaryrefslogtreecommitdiffstats
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2005-04-17 15:49:52 +0000
committerRichard M. Stallman <[email protected]>2005-04-17 15:49:52 +0000
commitfdbc96cabad658b6299c6dad951f9b4b9b9d5c19 (patch)
treef2414f537af388bfa947e06f9d622ac9321f94d4 /lispref
parentfaa44aee7b057a841cf52fa2b51d4c7a127325b8 (diff)
(Positions): Clarify further.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/positions.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/lispref/positions.texi b/lispref/positions.texi
index 9a71cf29e3..3c1e642e6b 100644
--- a/lispref/positions.texi
+++ b/lispref/positions.texi
@@ -22,9 +22,10 @@ with the surrounding characters. Functions that expect an argument to
be a position (an integer), but accept a marker as a substitute,
normally ignore which buffer the marker points into; they convert the
marker to an integer, and use that integer, exactly as if you had
-passed the integer as the argument. Markers used this way usually
-point to a position in the buffer that the function will operate on,
-but if not, they are converted to integers anyway. @xref{Markers}.
+passed the integer as the argument, even if the marker points to the
+``wrong'' buffer. A marker that points nowhere cannot convert to an
+integer; using it instead of an integer causes an error.
+@xref{Markers}.
See also the ``field'' feature (@pxref{Fields}), which provides
functions that are used by many cursor-motion commands.