From: Duy Nguyen <pclouds@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Duy Nguyen <pclouds@gmail.com>, Jeff King <peff@peff.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Add configuration options for some commonly used command-line options
Date: Mon, 20 Mar 2017 17:42:18 +0700 [thread overview]
Message-ID: <CACsJy8CxX_C8rOb3mZXHum-5w+aev=QR-r3DZ5Ad=zg8j2XxnQ@mail.gmail.com> (raw)
In-Reply-To: <20170319131845.tl6o3t2nwicj2rug@genre.crustytoothpaste.net>
On Sun, Mar 19, 2017 at 8:18 PM, brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>> OTOH, we already have almost "enable such or such option by default"
>> with aliases. People who always run "git am" with "-3" can write
>>
>> [alias]
>> a3 = am -3
>>
>> and just run "git a3".
>
> I tend to agree here.
That's exactly what I'm doing too. But I have an impression that the
stream of new configuration for default cmdline options keeps coming
in. And this, as a gsoc microproject, encourages more to come :-/
There's also another reason I suggested this but I don't know if it
will work out yet. If we start to make parse_options() or similar to
handle some configurations, we probably can gradually move away from
the procedural callback-based config parsing to a more declarative
style like 'struct option'. That opens up new opportunities: spotting
config name typos, listing applicable variables of a command ....
--
Duy
prev parent reply other threads:[~2017-03-20 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 9:57 Add configuration options for some commonly used command-line options (Was: [RFH] GSoC 2015 application) Duy Nguyen
2017-03-19 10:15 ` Add configuration options for some commonly used command-line options Matthieu Moy
2017-03-19 13:18 ` brian m. carlson
2017-03-19 13:43 ` Ævar Arnfjörð Bjarmason
2017-03-20 10:56 ` Duy Nguyen
2017-03-20 17:32 ` Brandon Williams
2017-03-20 18:18 ` Jeff King
2017-03-31 19:44 ` Brandon McCaig
2017-03-20 18:56 ` Junio C Hamano
2017-03-20 19:14 ` Jeff King
2017-03-20 21:57 ` Ævar Arnfjörð Bjarmason
2017-03-24 23:10 ` [PATCH/RFC] parse-options: add facility to make options configurable Ævar Arnfjörð Bjarmason
2017-03-25 16:47 ` Ævar Arnfjörð Bjarmason
2017-03-25 21:31 ` Jeff King
2017-03-25 22:32 ` Ævar Arnfjörð Bjarmason
2017-03-28 5:17 ` Jeff King
2017-03-28 13:13 ` [PATCH/RFC v2] WIP configurable options facility Ævar Arnfjörð Bjarmason
2017-03-25 21:28 ` [PATCH/RFC] parse-options: add facility to make options configurable brian m. carlson
2017-03-20 10:42 ` Duy Nguyen [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8CxX_C8rOb3mZXHum-5w+aev=QR-r3DZ5Ad=zg8j2XxnQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).