unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: StrawberryTea <look@strawberrytea.xyz>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 69259@debbugs.gnu.org
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 16:17:06 +0100	[thread overview]
Message-ID: <87edd4plzh.fsf@bernoul.li> (raw)
In-Reply-To: <87y1bdmlwa.fsf@strawberrytea.xyz>

StrawberryTea <look@strawberrytea.xyz> writes:

> Thanks for the explanation Stefan and Eli. I ended up making a PR to magit. And
> I think Tarsius is going to merge it. He just asked me to test it after he made
> a small change.

It would have helped me if you had mentioned this discussion there.
I only became aware of this because Eli cced me.  It is useful for
me because it confirms some speculation of mine.  When I merged the
Magit pull-request I mentioned that I am doing so as a quick fix for
the issue, but that I intend to look at it again at a later time.

>>> I think cursor-sensor is written under the assumption that the
>>> selected window’s buffer is also the current buffer, and if so,
>>> magit-post-command-hook should abide by that protocol.  Stefan, am I
>>> right?
>>
>> Not `cursor-sensor.el` in its entirety, but
>> `cursor-sensor-move-to-tangible` presumes that it is called with the
>> current-buffer already set to (window-buffer window).

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.

     Jonas





  parent reply	other threads:[~2024-02-22 15:17 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 [this message]
2024-02-22 15:30             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87edd4plzh.fsf@bernoul.li \
    --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).