From: Jeff King <peff@peff.net>
To: hIpPy <hippy2981@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git alias for options
Date: Sat, 18 Feb 2017 01:33:45 -0500 [thread overview]
Message-ID: <20170218063345.3owwc2pwptdv2zu6@sigill.intra.peff.net> (raw)
In-Reply-To: <CAM_JFCzoouREM5-6aq9wb0ouT34GKCoJ_pcsww5TYKAdztR9sA@mail.gmail.com>
On Fri, Feb 17, 2017 at 02:34:15PM -0800, hIpPy wrote:
> I think the conversation has drifted away from what I am asking / hoping for.
Yeah, the usual answer to "can we have custom options" is "use a custom
alias". But I agree they are not quite the same thing.
> Say I want an alias for option --name-status as -s, so I can type:
> $ git log -s
>
> But there is already a -s option and that wins so the built-in option
> alias wins.
>
> However, I think I should be able alias it as --ns.
> $ git log --ns
To be honest, I am not that enthused about the idea, but I don't have an
real objection beyond "meh, that looks like an unnecessary
complication".
If anybody wants to pursue it, the simplest way would probably be to
teach parse-options to take a callback for an unknown option, which
could then do a config lookup to transmute the argument into another
option-name.
Though many of the options (notably the revision-walker and diff ones)
are not handled by parse-options. So that might present a challenge.
-Peff
prev parent reply other threads:[~2017-02-18 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 8:23 git alias for options hIpPy
2017-02-17 13:15 ` Michael J Gruber
2017-02-17 13:50 ` Ævar Arnfjörð Bjarmason
2017-02-17 20:42 ` Jeff King
2017-02-17 22:10 ` Ævar Arnfjörð Bjarmason
2017-02-17 22:13 ` Jeff King
2017-02-17 22:31 ` Junio C Hamano
2017-02-17 22:34 ` hIpPy
2017-02-18 6:33 ` Jeff King [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=20170218063345.3owwc2pwptdv2zu6@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hippy2981@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;
as well as URLs for NNTP newsgroup(s).