From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA, doc RFA] Add gdb.add_command_alias
Date: Tue, 13 Sep 2011 17:47:00 -0000 [thread overview]
Message-ID: <201109131839.49816.pedro@codesourcery.com> (raw)
In-Reply-To: <CADPb22QTt1XcLd0JvsyPxE-O_njbP6H6UgfkSVoDu__y+rZKZA@mail.gmail.com>
On Tuesday 13 September 2011 18:20:16, Doug Evans wrote:
> On Fri, Sep 9, 2011 at 2:13 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Fri, 9 Sep 2011 11:36:36 -0700 (PDT)
> >> From: dje@google.com (Doug Evans)
> >>
> >> Per discussion on IRC, here is a patch to add support for adding
> >> command aliases.
> >
> > I wish people would discuss such issues here, not on IRC. These
> > discussions should be recorded, for one thing.
>
> Whatever additional discussion one wants to have we can have here.
> No worries.
>
> > Me, I don't understand the need for this feature, especially not why
> > it should be a Python-only feature. Moreover, why do we need to have
> > this, when one can easily write a command that just calls an existing
> > one, to have the same effect.
IMO, since this is really about aliasing new CLI spellings for
existing CLI commands, it'd make sense to have a way to alias commands
in the CLI, without python. E.g.,
(gdb) alias isl info shared library
(gdb) isl
<list shared libraries>
Python could then of course just do gdb.execute("alias ...").
--
Pedro Alves
next prev parent reply other threads:[~2011-09-13 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 19:25 Doug Evans
2011-09-09 21:15 ` Eli Zaretskii
2011-09-13 17:40 ` Doug Evans
2011-09-13 17:47 ` Pedro Alves [this message]
2011-09-13 19:15 ` Doug Evans
2011-09-13 19:32 ` Pedro Alves
2011-09-13 21:42 ` Doug Evans
2011-09-21 21:46 ` Doug Evans
2011-09-22 14:08 ` Pedro Alves
2011-09-22 17:45 ` Doug Evans
2011-09-22 18:13 ` Eli Zaretskii
2011-09-22 21:48 ` Doug Evans
2011-09-23 11:40 ` Eli Zaretskii
2011-09-13 18:49 ` Pedro Alves
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=201109131839.49816.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox