Re: [PATCH 2/2] bundle: rewrite builtin to use parse-options
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Dec 8, 2011, 17:38 UTC
- Message-ID
- <CALkWK0m89D02aku8J0OXbpyrovHCOpsYS4Qpx2jH-pFG4rOG2A@mail.gmail.com>
- In-Reply-To
- <20111208170319.GD2394@elie.hsd1.il.comcast.net>
Hi,
Jonathan Nieder wrote:
Show 8 quoted lines
> Ramkumar Ramachandra wrote: > >> Sure, you can't create a >> bundle named "verify", but that's the compromise you'll have to make >> if you don't want to type out "--" with each option, no? > > Having to type "--" or prefix with "./" to escape ordinary filenames > that do not start with "-" would be completely weird.
Hm, do you have any suggestions to work around this? Can we use something like a parse-stopper after the the first subcommand is encountered, and treat the next argument as a non-subcommand (filename or whatever else)?
-- Ram