From: Pedro Alves <pedro@palves.net>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Marco Barisione <mbarisione@undo.io>
Cc: gdb-patches@sourceware.org
Subject: Re: Add a way to invoke redefined (overridden) GDB commands
Date: Tue, 20 Oct 2020 16:15:32 +0100 [thread overview]
Message-ID: <14991975-c08a-fde6-f00d-e60723d96cc8@palves.net> (raw)
In-Reply-To: <553d9751c944c660dad4a204cf4609c660baa106.camel@skynet.be>
On 10/19/20 7:47 PM, Philippe Waroquiers wrote:
> On Mon, 2020-10-19 at 19:05 +0100, Pedro Alves wrote:
> For what concerns the rename, alias uses = to separate
> the 2 commands:
> (gdb) h alias
> Define a new command that is an alias of an existing command.
> Usage: alias [-a] [--] ALIAS = COMMAND [DEFAULT-ARGS...]
> ...
> So, maybe better/more consistent to use = similarly for rename.
In the "alias" case, the "=" makes sense since we're
setting up an equivalence.
With renaming, isn't "=" a little weird?
(gdb) rename oldname = newname
I guess I'd get used to it.
prev parent reply other threads:[~2020-10-20 15:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:39 Marco Barisione
2020-09-14 9:39 ` [PATCH 1/2] Move the code to execute a cmd_list_element out from execute_command Marco Barisione
2020-10-05 9:08 ` Andrew Burgess
2020-10-05 9:40 ` Marco Barisione
2020-10-05 17:49 ` Andrew Burgess
2020-09-14 9:39 ` [PATCH 2/2] Add a way to preserve redefined GDB commands for later invocation Marco Barisione
2020-09-14 16:18 ` Eli Zaretskii
2020-09-14 16:51 ` Marco Barisione
2020-10-05 10:24 ` Andrew Burgess
2020-10-05 11:44 ` Marco Barisione
2020-10-05 18:11 ` Andrew Burgess
2020-10-06 7:18 ` Marco Barisione
2020-09-28 7:54 ` [PING] Add a way to invoke redefined (overridden) GDB commands Marco Barisione
2020-10-05 7:42 ` Marco Barisione
2020-10-12 11:50 ` Pedro Alves
2020-10-19 17:41 ` Marco Barisione
2020-10-19 18:05 ` Pedro Alves
2020-10-19 18:47 ` Philippe Waroquiers
2020-10-19 19:28 ` Marco Barisione
2020-10-20 15:06 ` Pedro Alves
2020-10-20 18:19 ` Marco Barisione
2020-10-20 18:32 ` Pedro Alves
2020-10-20 15:15 ` Pedro Alves [this message]
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=14991975-c08a-fde6-f00d-e60723d96cc8@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=mbarisione@undo.io \
--cc=philippe.waroquiers@skynet.be \
/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.
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).