From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFA, doc RFA] Add gdb.add_command_alias
Date: Fri, 23 Sep 2011 11:40:00 -0000 [thread overview]
Message-ID: <8339fnsgh4.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22RGqARG7jRT7pvSzfsBGz7kYVZDNht5c_SjXLFsvABZ7Q@mail.gmail.com>
> Date: Thu, 22 Sep 2011 11:22:26 -0700
> From: Doug Evans <dje@google.com>
> Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
>
> >> +The @samp{-f FROM} option specifies the name of an existing command
> >> +that is being aliased.
> >> +
> >> +The @samp{-t TO} option specifies the name of the new alias.
> >
> > Btw, I'm not sure FROM and TO are a good idea; it's not like you are
> > copying something. Â How about COMMAND and ALIAS instead?
>
> Ok, but then I have to wonder about -f and -t.
> -c and -a? [setting aside -a collides with the current -a for abbreviation]
>
> But if you're happy with -f COMMAND -t ALIAS, great.
I'm not happy about that, either, FWIW. Why not use the popular
syntax used by other programs that offer aliases? E.g.,
(gdb) alias ALIAS=COMMAND
But that's just MO, FWIW. If everyone else is happy with these letter
switches, I can live with that.
> >> +Note that if you are defining an alias of a @samp{set} command,
> >> +you also need to define the alias of the corresponding @samp{show}
> >> +command, if desired.
> >
> >
> > "Need" and "if desired" are in contradiction. Â Which is it?
>
> How about if I reword it to:
>
> Note that if you are defining an alias of a @samp{set} command,
> and you want to have an alias for the corresponding @samp{show}
> command, then you need to define the latter separately.
Works for me, thanks.
next prev parent reply other threads:[~2011-09-23 10:27 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
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 [this message]
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=8339fnsgh4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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