Re: Add configuration options for some commonly used command-line options

From: Duy Nguyen <pclouds@gmail.com>
Date: Mar 20, 2017, 10:42 UTC
Message-ID: <CACsJy8CxX_C8rOb3mZXHum-5w+aev=QR-r3DZ5Ad=zg8j2XxnQ@mail.gmail.com>
In-Reply-To: <20170319131845.tl6o3t2nwicj2rug@genre.crustytoothpaste.net>

On Sun, Mar 19, 2017 at 8:18 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 9 quoted lines

>> 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