GNU bug report logs - #28527
unexpected behaviour of char-after if argument is marker that don't point to the current buffer

Previous Next

Full log

Message #8 received at 28527 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Fritz Stelzer <brotzeitmacher <at> gmail.com>
Cc: 28527 <at> debbugs.gnu.org
Subject: Re: bug#28527: unexpected behaviour of char-after if argument is
 marker that don't point to the current buffer
Date: Wed, 20 Sep 2017 18:51:27 +0300

> 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 <at> gmail.com>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs <at> gnu.org
> Resent-Sender: help-debbugs <at> gnu.org
> From: Fritz Stelzer <brotzeitmacher <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.