Re: [PATCH 1/6] gitopt: a new command-line option parser for git
- From
- Timo Hirvonen <tihirvon@gmail.com>
- Date
- May 9, 2006, 21:08 UTC
- Message-ID
- <20060510000826.1a708c03.tihirvon@gmail.com>
- In-Reply-To
- <7vlktb2ayy.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 12 quoted lines
> Timo Hirvonen <tihirvon@gmail.com> writes: > > > I think optional arguments are still confusing. We could support both > > -C (no args) and -C=20 syntax. > > Actually, optional numeric arguments are the norm not exception. > Think of "diff -u" vs "diff -u20" for example. Also I think it > is conventional not to use = for single-letter single-dash > options, so -C (no args -- use the default number of the > implementation whatever it is) and -C20 (the same behaviour in > principle as -C, but use my number instead of the default) are > sane, while -C=20 _is_ odd.
OK, if we don't support bundling flags at all then -x=y and -xy would do the same thing and pickaxe's -Stext would work too. But we could not make option flag parsing global then (-S=value -> search "=value" or "value"?).
Maybe we should just change -Stext to -S=text or -S text.
Better to support only -x=y or -x y, not both.
> Having said that, I think abbreviating -u20 -n -r to -u20nr > going too far
Yes
> (-nru20 would be palatable perhaps),
No :)
-- http://onion.dynserv.net/~timo/