Re: moving point over invisible and intangible text

[Richard Stallman]

    Buffer starting at line1, no trailing whitespace.  With line2
    including trailing newline invisible or invisible-intangible, both
    implementations disallow positions 8-13 inclusive.  Both move point
    from 7 to 14 going forward and from 14 to 7 backward.

Ok, I guess they really are the same.  So I will get rid of the
special invisible-intangible behavior.

I documented the new invisible behavior as I understand it:

      Ordinarily, functions that operate on text or move point do not care
    whether the text is invisible.  The user-level line motion commands
    explicitly ignore invisible newlines if
    @code{line-move-ignore-invisible} is address@hidden, but only because
    they are explicitly programmed to do so.

      However, if a command ends with point inside or immediately after
    invisible text, the main editing loop moves point further forward or
    further backward (in the same direction that the command already moved
    it) until that condition is no longer true.  Thus, if the command
    moved point back into an invisible range, Emacs moves point back to
    the beginning of that range, following the previous visible character.
    If the command moved point forward into an invisible range, Emacs
    moves point forward past the first visible character that follows the
    invisible text.


Stefan, is that entirely correct?  Does that feature pay attention
to stickiness of the invisible property?

What happens when the invisible text is at the end of the buffer?  For
consistent behavior, following the principle of not allowing point on
both sides of the invisible text, it seems we should disallow putting
point after it.  Is that implemented now?