* bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer
@ 2017-09-20 13:29 Fritz Stelzer
2017-09-20 15:51 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Fritz Stelzer @ 2017-09-20 13:29 UTC (permalink / raw)
To: 28527
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 384 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer
2017-09-20 13:29 bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer Fritz Stelzer
@ 2017-09-20 15:51 ` Eli Zaretskii
2019-11-11 3:00 ` Stefan Kangas
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2017-09-20 15:51 UTC (permalink / raw)
To: Fritz Stelzer; +Cc: 28527
> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
> HTML_MESSAGE,RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=disabled version=3.3.2
> Resent-From: Fritz Stelzer <brotzeitmacher@gmail.com>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs@gnu.org
> Resent-Sender: help-debbugs@gnu.org
> From: Fritz Stelzer <brotzeitmacher@gmail.com>
> Date: Wed, 20 Sep 2017 15:29:07 +0200
>
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer
2017-09-20 15:51 ` Eli Zaretskii
@ 2019-11-11 3:00 ` Stefan Kangas
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Kangas @ 2019-11-11 3:00 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: Fritz Stelzer, 28527
tags 28527 + notabug
close 28527
thanks
Eli Zaretskii <eliz@gnu.org> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-11-11 3:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-20 13:29 bug#28527: unexpected behaviour of char-after if argument is marker that don't point to the current buffer Fritz Stelzer
2017-09-20 15:51 ` Eli Zaretskii
2019-11-11 3:00 ` Stefan Kangas
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).