Subject: Re: bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer

From: Stefan Kangas <[email-masked]>
Date: Mon, 11 Nov 2019 04:00:14 +0100

tags 28527 + notabug
close 28527
thanks

Eli Zaretskii <[email-masked]> writes:

>> When the argument for char-after is a marker, the function gets bytepos from the buffer the marker is pointing
>> to by calling marker_byte_position. But then pos_byte is compared to BEGV_BYTE and ZV_BYTE that use the
>> current buffer. At the end of the function, pos_byte is passed to FETCH_CHAR, which also operates on the
>> current buffer.
>
> This is according to the documentation, which explicitly says the
> position is looked up in the current buffer.  So this sounds like an
> intentional and documented behavior.

With the above explanation and no other comments within 2 years, I'm
closing this as notabug.

Best regards,
Stefan Kangas