From: Caleb Chase <chase.caleb@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51382@debbugs.gnu.org, akrl@sdf.org
Subject: bug#51382: 29.0.50; org-offer-links-in-entry is incompatible with native-compile
Date: Tue, 13 Sep 2022 11:27:01 -0500 [thread overview]
Message-ID: <CAKTYAwr0igL8xBjk4osxbL=6ZZWntWfNgi=UEg+V=hvRCo=Jow@mail.gmail.com> (raw)
In-Reply-To: <87illrxns3.fsf@gnus.org>
On Tue, Sep 13, 2022 at 11:05 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Caleb Chase <chase.caleb@gmail.com> writes:
>
> > Here's a trivial reproduction:
> >
> > 1. Create an org file, e.g. /tmp/test.org. See end of this message for
> > an example, but essentially any org file with a heading that contains
> > multiple links somewhere within its contents.
> > 2. Ensure that org.el is natively compiled
> > 3. Run "emacs -Q"
> > 4. "C-x C-f" to open the test file
> > 5. Move point to beginning of the header
> > 6. "C-c C-o 2" to open the second link
> > 7. Bug occurs: first link is opened regardless of choice in the previous step
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> I'm unable to reproduce this problem with the current "master", but I
> only tested on Ubuntu. Do you still see this problem, Caleb?
Hi, sorry about that and thanks for the follow-up. I just tested and
agree that it's fixed.
next prev parent reply other threads:[~2022-09-13 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a6ixzq6h.fsf.ref@yahoo.com>
2021-10-25 4:25 ` bug#51382: 29.0.50; org-offer-links-in-entry is incompatible with native-compile luangruo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 8:48 ` Andrea Corallo
2021-10-27 15:13 ` Caleb Chase
2022-09-13 16:05 ` Lars Ingebrigtsen
2022-09-13 16:27 ` Caleb Chase [this message]
2022-09-13 16:34 ` Lars Ingebrigtsen
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='CAKTYAwr0igL8xBjk4osxbL=6ZZWntWfNgi=UEg+V=hvRCo=Jow@mail.gmail.com' \
--to=chase.caleb@gmail.com \
--cc=51382@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.org \
/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).