From: Jonathan Nieder <jrnieder@gmail.com>
Date: Thu, 08 Dec 2011 17:59:14 GMT
Subject: Re: [PATCH 2/2] bundle: rewrite builtin to use parse-options
Message-ID: <20111208175913.GK2394@elie.hsd1.il.comcast.net>
In-Reply-To: <CALkWK0m89D02aku8J0OXbpyrovHCOpsYS4Qpx2jH-pFG4rOG2A@mail.gmail.com>

Ramkumar Ramachandra wrote:
> Jonathan Nieder wrote:

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

What's the desired behavior?  Then we can talk about how to implement it.

If the goal is "use parse-options for a command that has subcommands",
see builtin/notes.c.