From: Brian Leung <leungbk@mailfence.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49632@debbugs.gnu.org, juri@linkov.net
Subject: bug#49632: [PATCH] Ensure that M-x gdb populates gud-repeat-map
Date: Mon, 19 Jul 2021 16:57:11 +0200 (CEST) [thread overview]
Message-ID: <1533263297.2069981.1626706630967@ichabod.co-bxl> (raw)
In-Reply-To: <835yx678fj.fsf@gnu.org>
> I admit I don't understand the rationale for the patch at all.
> "M-x gdb" already repeats these commands when you type just RET
> into the interaction buffer, so what exactly does this change
> do, and how can I see its effect?
RET can repeat only the last command (afaik). If instead I want to run, in order:
1. continue
2. next
3. next
4. stepi
then without this patch, I would need to press
1. C-x C-a C-r
2. C-x C-a C-n
3. C-x C-a C-n
4. C-x C-a C-i
if using M-x gdb.
With the patch, I can press:
1. C-x C-a C-r
2. n
3. n
4. i
since the new repeat-mode defines the appropriate repeat map.
> ----------------------------------------
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Mon Jul 19 15:13:52 CEST 2021
> To: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: <leungbk@mailfence.com>, <49632@debbugs.gnu.org>, <juri@linkov.net>
> Subject: Re: bug#49632: [PATCH] Ensure that M-x gdb populates gud-repeat-map
>
>
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Date: Mon, 19 Jul 2021 15:06:31 +0200
> > Cc: 49632@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
> >
> > Brian Leung <leungbk@mailfence.com> writes:
> >
> > > * lisp/progmodes/gdb-mi.el (gdb): Populate gud-repeat-map. This is
> > > copied from the gud-gdb command.
> >
> > Instead of copying the code, perhaps it should be separated out into its
> > own function and then called from both places?
> >
> > But I don't quite understand why gud-repeat-map is populated in the
> > normal way -- i.e., in `gud-repeat-map' so that users can
> > redefine/override entries as usual.
>
> I admit I don't understand the rationale for the patch at all.
> "M-x gdb" already repeats these commands when you type just RET
> into the interaction buffer, so what exactly does this change
> do, and how can I see its effect?
--
Sent with https://mailfence.com
Secure and private email
--
Mailfence.com
Private and secure email
next prev parent reply other threads:[~2021-07-19 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 3:37 bug#49632: [PATCH] Ensure that M-x gdb populates gud-repeat-map Brian Leung
2021-07-19 13:06 ` Lars Ingebrigtsen
2021-07-19 13:13 ` Eli Zaretskii
2021-07-19 14:57 ` Brian Leung [this message]
2021-07-19 16:05 ` Eli Zaretskii
2021-07-19 21:53 ` Juri Linkov
2021-07-19 14:51 ` Brian Leung via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-19 15:37 ` Juri Linkov
2021-07-19 15:52 ` Lars Ingebrigtsen
2021-07-24 3:33 ` Brian Leung
2021-07-25 6:26 ` Lars Ingebrigtsen
2021-07-25 20:53 ` Juri Linkov
2021-07-25 21:28 ` Brian Leung
2021-07-26 22:48 ` Juri Linkov
2021-07-27 4:09 ` Brian Leung
2021-07-27 6:46 ` Brian Leung
2021-07-27 21:15 ` Juri Linkov
2021-07-28 11:30 ` Eli Zaretskii
2021-07-28 16:23 ` Juri Linkov
2021-07-28 16:30 ` 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=1533263297.2069981.1626706630967@ichabod.co-bxl \
--to=leungbk@mailfence.com \
--cc=49632@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).