Re: Edebug corrupting point in buffers.

[Stefan Monnier]

>> Really?  My reading of the code:
>
>>            /* As documented in Fcurrent_window_configuration, don't
>>               restore the location of point in the buffer which was
>>               current when the window configuration was recorded.  */
>>            if (!EQ (p->buffer, new_current_buffer)
>>                && XBUFFER (p->buffer) == current_buffer)
>>              Fgoto_char (w->pointm);
>
>> is that it's done only for the current buffer and only if it's different
>> from the "to be current buffer".
>
>> Am I missing something?
>
> Hmm.  I spent a great deal of yesterday asserting false things, then
> apologising for them.  The above was the last such false thing, for which
> I also apologise.

If we had to apologize every time we misread/misunderstood code, we'd
never get anywhere :-)

> There's clearly been a lot of confusion about window/buffer point over
> the decades which shows in the number of places such changes in buffer
> point occur, and the bugs which have sometimes resulted, like the one
> you cite above.

This is arguably one of the most subtle/delicate/complex aspect of
ELisp's semantics, indeed.


        Stefan