emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r106622: * doc/lispref/text.texi (Spe


From: Stefan Monnier
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r106622: * doc/lispref/text.texi (Special Properties): Warn against `intangible' properties.
Date: Mon, 05 Dec 2011 11:50:25 -0500
User-agent: Bazaar (2.3.1)

------------------------------------------------------------
revno: 106622
fixes bug(s): http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10222
committer: Stefan Monnier <address@hidden>
branch nick: trunk
timestamp: Mon 2011-12-05 11:50:25 -0500
message:
  * doc/lispref/text.texi (Special Properties): Warn against `intangible' 
properties.
modified:
  doc/lispref/ChangeLog
  doc/lispref/commands.texi
  doc/lispref/text.texi
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2011-11-26 14:07:22 +0000
+++ b/doc/lispref/ChangeLog     2011-12-05 16:50:25 +0000
@@ -1,3 +1,8 @@
+2011-12-05  Stefan Monnier  <address@hidden>
+
+       * text.texi (Special Properties): Warn against `intangible' properties
+       (bug#10222).
+
 2011-11-26  Eli Zaretskii  <address@hidden>
 
        * display.texi (Truncation):
@@ -23,8 +28,8 @@
 
 2011-11-21  Martin Rudalics  <address@hidden>
 
-       * windows.texi (Windows and Frames, Splitting Windows): Fix
-       typos.
+       * windows.texi (Windows and Frames, Splitting Windows):
+       Fix typos.
 
 2011-11-21  Chong Yidong  <address@hidden>
 
@@ -36,8 +41,8 @@
        (Buffers and Windows): Copyedits.
        (Choosing Window): Document special handling of special-display-*.
        (Choosing Window Options): Fix display-buffer-reuse-frames doc.
-       Don't document even-window-heights, which is going away.  Clarify
-       which options are obeyed by which action functions.
+       Don't document even-window-heights, which is going away.
+       Clarify which options are obeyed by which action functions.
 
 2011-11-20  Stefan Monnier  <address@hidden>
 

=== modified file 'doc/lispref/commands.texi'
--- a/doc/lispref/commands.texi 2011-07-11 17:45:01 +0000
+++ b/doc/lispref/commands.texi 2011-12-05 16:50:25 +0000
@@ -946,10 +946,9 @@
 
   It is not easy to display a value of point in the middle of a
 sequence of text that has the @code{display}, @code{composition} or
address@hidden property, or is invisible.  Therefore, after a
-command finishes and returns to the command loop, if point is within
-such a sequence, the command loop normally moves point to the edge of
-the sequence.
+is invisible.  Therefore, after a command finishes and returns to the
+command loop, if point is within such a sequence, the command loop
+normally moves point to the edge of the sequence.
 
   A command can inhibit this feature by setting the variable
 @code{disable-point-adjustment}:

=== modified file 'doc/lispref/text.texi'
--- a/doc/lispref/text.texi     2011-11-26 14:07:22 +0000
+++ b/doc/lispref/text.texi     2011-12-05 16:50:25 +0000
@@ -3145,6 +3145,12 @@
 When the variable @code{inhibit-point-motion-hooks} is address@hidden,
 the @code{intangible} property is ignored.
 
+Beware: this property operates at a very low level, and affects a lot of code
+in unexpected ways.  So use it with extreme caution.  A common misuse is to put
+an intangible property on invisible text, which is actually unnecessary since
+the command loop will move point outside of the invisible text at the end of
+each command anyway.  @xref{Adjusting Point}.
+
 @item field
 @kindex field @r{(text property)}
 Consecutive characters with the same @code{field} property constitute a


reply via email to

[Prev in Thread] Current Thread [Next in Thread]