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: 62858@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#62858: 30.0.50; Typo in gdb-mi.el
Date: Sat, 15 Apr 2023 20:19:12 +0200 [thread overview]
Message-ID: <878retuhy7.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <838retcjvs.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Apr 2023 17:14:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
[...]
> Stefan, any comments?
>
> diff --git a/lisp/progmodes/gdb-mi.el b/lisp/progmodes/gdb-mi.el
> index 8db1672..27f04e0 100644
> --- a/lisp/progmodes/gdb-mi.el
> +++ b/lisp/progmodes/gdb-mi.el
> @@ -2406,7 +2406,7 @@ gdbmi-bnf-result-state-configs
> ("+" . ())
> ("=" . (("thread-created" . (gdb-thread-created . atomic))
> ("thread-selected" . (gdb-thread-selected . atomic))
> - ("thread-existed" . (gdb-ignored-notification . atomic))
> + ("thread-exited" . (gdb-thread-exited . atomic))
> ('default . (gdb-ignored-notification . atomic)))))
> "Alist of alists, mapping the type and class of message to a handler function.
> Handler functions are all flagged as either `progressive' or `atomic'.
I had the same patch. FWIW, I did not see any change while using 'M-x
gdb'
--
Manuel Giraud
next prev parent reply other threads:[~2023-04-15 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 13:14 bug#62858: 30.0.50; Typo in gdb-mi.el Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15 14:14 ` Eli Zaretskii
2023-04-15 18:19 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-15 18:35 ` Eli Zaretskii
2023-04-15 19:42 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-18 11:37 ` Eli Zaretskii
2023-09-05 23:54 ` 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=878retuhy7.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=62858@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
--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 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.