From fdbc96cabad658b6299c6dad951f9b4b9b9d5c19 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sun, 17 Apr 2005 15:49:52 +0000 Subject: [PATCH] (Positions): Clarify further. --- lispref/positions.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/lispref/positions.texi b/lispref/positions.texi index 9a71cf29e33..3c1e642e6b4 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. -- 2.39.2