From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add aliases "i ty" and "i so".
Date: Sun, 04 Jan 2015 03:38:00 -0000 [thread overview]
Message-ID: <838uhj9pw1.fsf@gnu.org> (raw)
In-Reply-To: <m34ms7pm02.fsf@seba.sebabeach.org>
> From: Doug Evans <xdje42@gmail.com>
> Date: Sat, 03 Jan 2015 13:55:41 -0800
>
> I'd gotten tired enough of fully typing out "info types" and "info source"
> (which otherwise collide with "info type-printers" and "info sources")
> that I have this in my .gdbinit:
>
> alias i ty = info types
> alias i so = info source
>
> Does anyone want a more generally available solution?
> Another way to go is to put the "alias" solution in a more public
> place (the faq or some such).
> I don't have a strong preference, just in a "spring cleaning" kind of
> mood. :-)
>
> I thought of maybe "i t" for "info types" but I can't think of a reason
> to prefer "t" for "types" or "threads", so I'm going with "ty" which
> I think is pretty safe.
>
> "s" is taken ("info stack", which is fine by me), so I went with "so"
> for "source".
OK for the documentation parts.
Thanks.
prev parent reply other threads:[~2015-01-04 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 21:56 Doug Evans
2015-01-04 3:38 ` Eli Zaretskii [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=838uhj9pw1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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