From: Eli Zaretskii <eliz@gnu.org>
To: Fritz Stelzer <brotzeitmacher@gmail.com>
Cc: 28527@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <83efr1fjwg.fsf@gnu.org> (raw)
In-Reply-To: <CA+CiP9B0Tenivs3MvzEQkXndTpu_tGogv7gU0CTyKrU=nkU8JQ@mail.gmail.com> (message from Fritz Stelzer on Wed, 20 Sep 2017 15:29:07 +0200)
> 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.
next prev parent reply other threads:[~2017-09-20 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-11-11 3:00 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efr1fjwg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28527@debbugs.gnu.org \
--cc=brotzeitmacher@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.