Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add "inf" alias for "info"
Date: Wed, 08 Jul 2009 13:36:00 -0000	[thread overview]
Message-ID: <200907081436.35386.pedro@codesourcery.com> (raw)
In-Reply-To: <000301c9ffcf$ecec6bc0$c6c54340$@u-strasbg.fr>

On Wednesday 08 July 2009 14:28:05, Pierre Muller wrote:
> > >   The proposed patch add "inf" as an alias
> > > of "info", saving the hassle of retyping "info"
> > > after the message above.
> > 
> > Why not type just "i"?  It is already an alias for "info", and,
> > it's shorter anyway ==> less hassle.
> 
>   No really good reasons but,
> I used "inf " for years and didn't know "i " worked,
> I discovered it while writing the patch!
>   But I am too used to "inf " to be able to switch to "i "
> easily!

I'm sure that you'll now get used to "i" in no time, now
that you know it.

This revealed an interesting issue.  The

 'Ambiguous command "inf reg": inferior, info.'

... message doesn't indicate the aliases of each alternative
command.  Neither does "help info" mention "i".  Maybe it should.

(btw, "i" + "inf" would leave "in" in a weird spot)

-- 
Pedro Alves


  reply	other threads:[~2009-07-08 13:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 13:18 Pierre Muller
2009-07-08 13:23 ` Pedro Alves
2009-07-08 13:25   ` Daniel Jacobowitz
2009-07-08 13:26     ` Pedro Alves
2009-07-08 13:35       ` Daniel Jacobowitz
2009-07-08 13:48         ` Pedro Alves
2009-07-08 14:00           ` Daniel Jacobowitz
2009-07-08 13:28   ` Pierre Muller
2009-07-08 13:36     ` Pedro Alves [this message]
2009-07-08 13:41       ` Pierre Muller
2009-07-08 13:44         ` Pedro Alves
2009-07-08 17:43   ` Michael Snyder
2009-07-08 20:08     ` 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=200907081436.35386.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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