From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Eli Zaretskii <eliz@gnu.org>,
69259@debbugs.gnu.org, StrawberryTea <look@strawberrytea.xyz>
Subject: bug#69259: 30.0.50; (get-pos-property 9483 'cursor-intangible) gives args-out-of-range error in folded magit buffer
Date: Thu, 22 Feb 2024 10:30:56 -0500 [thread overview]
Message-ID: <jwv8r3cpll7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87edd4plzh.fsf@bernoul.li> (Jonas Bernoulli's message of "Thu, 22 Feb 2024 16:17:06 +0100")
> That was my guess. The merged commit just forgoes calling that function
> if things aren't as expected. My plan was (and obviously still is) to
> look into instead ensuring that the expected buffer is current, making
> it current if necessary.
As alluded to in my other message, maybe we should consider it a bug
if `post-command-hook` functions get called with (current-buffer)
different from (window-buffer) and similarly I'd consider it a bug if
such a function breaks this invariant.
[ Just putting this out there, hoping to influence who you
blame at the end of your "look into" 🙂 ]
Stefan
next prev parent reply other threads:[~2024-02-22 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 21:08 bug#69259: 30.0.50; (get-pos-property 9483 'cursor-intangible) gives args-out-of-range error in folded magit buffer StrawberryTea
2024-02-19 12:27 ` Eli Zaretskii
2024-02-20 15:42 ` StrawberryTea
2024-02-21 12:31 ` Eli Zaretskii
2024-02-21 14:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 23:29 ` StrawberryTea
2024-02-22 6:42 ` Eli Zaretskii
2024-02-22 15:17 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 15:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-22 17:15 ` StrawberryTea
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8r3cpll7.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=69259@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jonas@bernoul.li \
--cc=look@strawberrytea.xyz \
--cc=monnier@iro.umontreal.ca \
/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 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).