From: Gelonida N <gelonida@gmail.com>
To: git@vger.kernel.org
Subject: Re: git alias and --help
Date: Fri, 28 Oct 2011 11:17:52 +0200 [thread overview]
Message-ID: <j8ds01$fc7$1@dough.gmane.org> (raw)
In-Reply-To: <7vvcr9wyje.fsf@alter.siamese.dyndns.org>
On 10/28/2011 06:05 AM, Junio C Hamano wrote:
> Miles Bader <miles@gnu.org> writes:
>
>> Of course, that would be the wrong thing for somebody that just wants
>> to be reminded what an alias expands too, but my intuition is that
>> this is a very tiny minority compared to people that want to examine
>> the options for the underlying command...
>
> And it is doubly wrong if help backend is configured to be anything but
> manpages, no?
Well. Then it is already doubly wrong today, isnt it?
The output of 'git help b'
is not a man page I assume.
In my opinion chaning it to a short message + the output of a man page
is not really worse than today's behaviour.
>
> As I said, you should be able to come up with a patch that detects and
> special cases the no frills case (replacement to single token) to get what
> you want.
That's perhaps the most comfortable one, though occasionally I am even
interested in the help text of a git command if I had an alias like
l = log --name-status
to see what other switches I could add
(Thus an alternative suggestion to display both or to have a special
syntax allowing to force displaying of a man page)
Another small detail:
Let's assume I have following alias:
log = log --name-status
In this case I directly get the help text for git log
if I typed 'git log --help' (or 'git help log').
I don't even see, that my log is in reality aliased.
next prev parent reply other threads:[~2011-10-28 9:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 22:20 git alias and --help Gelonida N
2011-10-27 22:28 ` Junio C Hamano
2011-10-27 22:50 ` Junio C Hamano
2011-10-28 0:24 ` Gelonida N
2011-10-28 1:51 ` Miles Bader
2011-10-28 4:05 ` Junio C Hamano
2011-10-28 9:00 ` Michael J Gruber
2011-10-28 9:17 ` Gelonida N [this message]
2011-10-28 13:27 ` Jakub Narebski
2011-10-28 20:21 ` Gelonida N
2011-10-28 13:26 ` Jakub Narebski
2011-10-28 18:07 ` Junio C Hamano
2011-10-28 18:25 ` Miles Bader
2011-10-28 20:23 ` Gelonida N
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='j8ds01$fc7$1@dough.gmane.org' \
--to=gelonida@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).