Re: invisible

[bojohan+news@dd.chalmers.se (Johan Bockgård)]

martin rudalics <rudalics@gmx.at> writes:

>> So why does (interactive) have this effect?
>
> I don't know.  I'd have to gdb set_point_both to find out but doing so
> is awkward here.  Maybe you could give it a try.  I could imagine that
> invisibility and intangibility properties get mixed up.  On the other
> hand it might be simply TRT to do for redisplay after an interactive
> command.  Miles and Stefan used to work on this but I'm afraid they
> won't tell us ...

I haven't been following the thread, but is this what you are talking
about?

    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 `line-move-ignore-invisible'
    is non-`nil' (the default), but only because they are explicitly
    programmed to do so.

    However, if a command ends with point inside or immediately before
    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.

(info "(elisp) Invisible Text")

-- 
Johan Bockgård