From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67683@debbugs.gnu.org
Subject: bug#67683: 30.0.50; [PATCH] Fix 'M-.' on Emacs C sources
Date: Thu, 07 Dec 2023 11:32:00 +0100 [thread overview]
Message-ID: <87v89a9ucf.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <838r662tww.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 Dec 2023 12:23:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 07 Dec 2023 10:54:12 +0100
>> From: Manuel Giraud via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I don't know how but for some times now 'M-.' is broken for me on C
>> sources. The attach patch seems reasonable and fixes this issue. I
>> guess that the title of this patch should be reworked but I don't really
>> know how to put it.
>
> Any chance of a reproduction recipe starting from "emacs -Q"? I just
> tried M-. with an arbitrary symbol in the Emacs C sources, and it
> worked. I also don't remember it ever failing for me. So I'm unsure
> why it fails for you and under which circumstances. So something is
> at work here that I don't see, and a recipe might help.
Yes, sorry it also works for me with "emacs -Q" (it even asks if I want
to visit the current directory tags table). I'll try to investigate it.
--
Manuel Giraud
next prev parent reply other threads:[~2023-12-07 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 9:54 bug#67683: 30.0.50; [PATCH] Fix 'M-.' on Emacs C sources Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-07 10:23 ` Eli Zaretskii
2023-12-07 10:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-07 15:27 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-07 17:19 ` Eli Zaretskii
[not found] ` <8734uuwr56.fsf@ledu-giraud.fr>
2024-01-18 16:30 ` Eli Zaretskii
2024-01-18 18:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-18 18:41 ` Eli Zaretskii
2024-01-18 19:10 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-18 20:02 ` Eli Zaretskii
2024-01-18 21:10 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 6:49 ` Eli Zaretskii
2024-01-19 9:18 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 11:48 ` Eli Zaretskii
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=87v89a9ucf.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=67683@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).