aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-04-17 15:49:52 +0000
committerRichard M. Stallman2005-04-17 15:49:52 +0000
commitfdbc96cabad658b6299c6dad951f9b4b9b9d5c19 (patch)
treef2414f537af388bfa947e06f9d622ac9321f94d4
parentfaa44aee7b057a841cf52fa2b51d4c7a127325b8 (diff)
downloademacs-fdbc96cabad658b6299c6dad951f9b4b9b9d5c19.tar.gz
emacs-fdbc96cabad658b6299c6dad951f9b4b9b9d5c19.zip
(Positions): Clarify further.
-rw-r--r--lispref/positions.texi7
1 files 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
22be a position (an integer), but accept a marker as a substitute, 22be a position (an integer), but accept a marker as a substitute,
23normally ignore which buffer the marker points into; they convert the 23normally ignore which buffer the marker points into; they convert the
24marker to an integer, and use that integer, exactly as if you had 24marker to an integer, and use that integer, exactly as if you had
25passed the integer as the argument. Markers used this way usually 25passed the integer as the argument, even if the marker points to the
26point to a position in the buffer that the function will operate on, 26``wrong'' buffer. A marker that points nowhere cannot convert to an
27but if not, they are converted to integers anyway. @xref{Markers}. 27integer; using it instead of an integer causes an error.
28@xref{Markers}.
28 29
29 See also the ``field'' feature (@pxref{Fields}), which provides 30 See also the ``field'' feature (@pxref{Fields}), which provides
30functions that are used by many cursor-motion commands. 31functions that are used by many cursor-motion commands.