summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2016-08-11 23:01:53 +0300
committerEli Zaretskii <eliz@gnu.org>2016-08-11 23:01:53 +0300
commit98b01dd1ef004b79de4998691a84bed6ea1ca0ba (patch)
treef630f4cde4c284798afcce0325cb70d66da308cb /doc
parent75f1882479cc62f8795bb652a0853a3f395420a2 (diff)
Clarify when 'cursor' property is in effect
* doc/lispref/text.texi (Special Properties): Minor copyedits. (Bug#24179)
Diffstat (limited to 'doc')
-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 8b4810f4a6..0445d68ef9 100644
--- a/doc/lispref/text.texi
+++ b/doc/lispref/text.texi
@@ -3362,12 +3362,14 @@ the beginning of the @code{display} property or at
@cindex cursor position for @code{display} properties and overlays
When the buffer has many overlay strings (e.g., @pxref{Overlay
-Properties, before-string}) or @code{display} properties that are
-strings, it is a good idea to use the @code{cursor} property on these
-strings to cue the Emacs display about the places where to put the
-cursor while traversing these strings. This directly communicates to
-the display engine where the Lisp program wants to put the cursor, or
-where the user would expect the cursor.
+Properties, before-string}) that conceal some of the buffer text or
+@code{display} properties that are strings, it is a good idea to use
+the @code{cursor} property on these strings to cue the Emacs display
+about the places where to put the cursor while traversing these
+strings. This directly communicates to the display engine where the
+Lisp program wants to put the cursor, or where the user would expect
+the cursor, when point is located on some buffer position that is
+``covered'' by the display or overlay string.
@item pointer
@kindex pointer @r{(text property)}