* [RFC] Default options
@ 2007-05-09 22:15 Dana How
2007-05-09 23:07 ` Johannes Schindelin
0 siblings, 1 reply; 3+ messages in thread
From: Dana How @ 2007-05-09 22:15 UTC (permalink / raw)
To: Git Mailing List, Junio C Hamano, danahow
Reading the exchange about new options to e.g.
git gc and git pack-objects over the last few days,
a pattern seemed to emerge. A new option would be
proposed, but then we didn't always want to type it,
so a corresponding config variable would be added as well.
I notice git supports "alias.*" config variables.
Would it be useful to also support "options.*" variables?
When you type
git gc <args>
this is interpreted as
git gc $(git config options.gc) <args>
so anything in options.gc could be overridden
by later appearing on the command line.
The names might have dashes:
pack-objects would use options.pack-objects .
If a command is recognized using alias.*,
options.* would not be consulted (to keep things simple).
In other words, options.* only work for built-ins.
options.* would interpret quoting etc in its
value the same way alias.* does.
Thus, you can add a new --option to a program,
and get a corresponding config variable automatically,
and without cluttering up the documentation.
I've not yet looked at the git driver code.
Is there any interest in this feature?
Thanks,
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [RFC] Default options
2007-05-09 22:15 [RFC] Default options Dana How
@ 2007-05-09 23:07 ` Johannes Schindelin
2007-05-09 23:14 ` Matthieu Moy
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Schindelin @ 2007-05-09 23:07 UTC (permalink / raw)
To: Dana How; +Cc: Git Mailing List, Junio C Hamano
Hi,
On Wed, 9 May 2007, Dana How wrote:
> I notice git supports "alias.*" config variables.
> Would it be useful to also support "options.*" variables?
I would not do it, for the same reason we do not allow to override
builtins via aliases: it breaks scripts.
Ciao,
Dscho
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] Default options
2007-05-09 23:07 ` Johannes Schindelin
@ 2007-05-09 23:14 ` Matthieu Moy
0 siblings, 0 replies; 3+ messages in thread
From: Matthieu Moy @ 2007-05-09 23:14 UTC (permalink / raw)
To: git
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Wed, 9 May 2007, Dana How wrote:
>
>> I notice git supports "alias.*" config variables.
>> Would it be useful to also support "options.*" variables?
>
> I would not do it, for the same reason we do not allow to override
> builtins via aliases: it breaks scripts.
In any case, I find it a bit redundant with the alias section.
If I want to be able to quickly type "git-cmd --some --option", I'll
just alias it to something shorter.
--
Matthieu
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-05-09 23:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-09 22:15 [RFC] Default options Dana How
2007-05-09 23:07 ` Johannes Schindelin
2007-05-09 23:14 ` Matthieu Moy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox