aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/lispref/text.texi14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/lispref/text.texi b/doc/lispref/text.texi
index 8b4810f4a60..0445d68ef9e 100644
--- a/doc/lispref/text.texi
+++ b/doc/lispref/text.texi
@@ -3362,12 +3362,14 @@ the beginning of the @code{display} property or at
3362 3362
3363@cindex cursor position for @code{display} properties and overlays 3363@cindex cursor position for @code{display} properties and overlays
3364When the buffer has many overlay strings (e.g., @pxref{Overlay 3364When the buffer has many overlay strings (e.g., @pxref{Overlay
3365Properties, before-string}) or @code{display} properties that are 3365Properties, before-string}) that conceal some of the buffer text or
3366strings, it is a good idea to use the @code{cursor} property on these 3366@code{display} properties that are strings, it is a good idea to use
3367strings to cue the Emacs display about the places where to put the 3367the @code{cursor} property on these strings to cue the Emacs display
3368cursor while traversing these strings. This directly communicates to 3368about the places where to put the cursor while traversing these
3369the display engine where the Lisp program wants to put the cursor, or 3369strings. This directly communicates to the display engine where the
3370where the user would expect the cursor. 3370Lisp program wants to put the cursor, or where the user would expect
3371the cursor, when point is located on some buffer position that is
3372``covered'' by the display or overlay string.
3371 3373
3372@item pointer 3374@item pointer
3373@kindex pointer @r{(text property)} 3375@kindex pointer @r{(text property)}