Re: [PATCH 1/6] gitopt: a new command-line option parser for git

From: Junio C Hamano <junkio@cox.net>
Date: May 9, 2006, 12:58 UTC
Message-ID: <7v8xpb73sq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060509120809.4d9494b9.tihirvon@gmail.com>

Timo Hirvonen <tihirvon@gmail.com> writes:

Show 7 quoted lines

> Eric Wong <normalperson@yhbt.net> wrote:
>
>>  * unbundling of short options: -uC20n20z => -u -C20 -n20 -z
>
> Does anyone ever use this?  I think this makes sense only for flags that
> don't have parameters but that would create an ugly special case. Is it
> too hard to type "-u -C=20 -n=20 -z"?

I can already hear in my head that people would start talking about "git understands insane abbeviations of options". It might be unambiguous, but that does not change it is a bit on the insane side. People would probably expect -nuz can be split into -n -u -z, and the current handcrafted mess (although it is more obvious and easy to work with when reading and maintaining the existing code) is not abbreviation friendly, which we would want to do something about. But I think squashing options with parameters together is going a bit too far.

> --with-r => --patch-with-raw works great

I personally think this also is too much.