bug#33662: 26.1; Elisp manual, index entry `invisible/intangible text, and point' and target

[Stefan Monnier <monnier@IRO.UMontreal.CA>]

> This index entry seems a bit wrong, or perhaps the targeted text is a
> bit wrong - in this sense: There is no occurrence of "tangible" or
> "intangible" in that node.  Using that index entry and arriving at that
> node, a user can wonder what happened - why there is nothing there that
> is explicitly about "intangible text".  Perhaps the node should make
> some mention of intangibility.

The section is about text that is intangible in the sense that that
point is automatically moved away from such text.

> The text of that node did mention intangible originally, but Stefan
> removed that as part of fixing bug#10222.  I'll let Stefan explain why
> he thought that was a good idea.

I removed mention of the `intangible` property since AFAICT the
corresponding code does not look at the `intangible` property (which is
not handled "After Commands" but directly during execution of the
various point motion Elisp functions).

In my understanding "invisible/intangible" here refers to the concepts
rather to the specific text-properties.

How 'bout the patch below?


        Stefan


diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 427379bc79..b6749d0a0c 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1012,7 +1012,8 @@ Adjusting Point
 sequence of text that has the @code{display} or @code{composition}
 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.
+command loop normally moves point to the edge of the sequence, making this
+sequence effectively intangible.
 
   A command can inhibit this feature by setting the variable
 @code{disable-point-adjustment}: