git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bring parse_options to the shell

From
Pierre Habouzit <madcoder@debian.org>
Date
Nov 2, 2007, 16:09 UTC
Message-ID
<20071102160925.GC27505@artemis.corp>
In-Reply-To
<alpine.LFD.0.999.0711020844310.3342@woody.linux-foundation.org>
On Fri, Nov 02, 2007 at 03:51:13PM +0000, Linus Torvalds wrote:
Show 15 quoted lines
> 
> 
> On Fri, 2 Nov 2007, Pierre Habouzit wrote:
> 
> > On Fri, Nov 02, 2007 at 03:09:18PM +0000, Pierre Habouzit wrote:
> > > This is also something that itches me, so here is a proposal for a
> > > git-parseopt helper that can be used in shell scripts as an option
> > > normalizer like getopt(1) does.
> > > 
> > > I migrated the discussed git-clean.sh to use it as a proof of concept.
> > 
> >   Needless to say, this is fetchable from
> > git://git.madism.org/git.git#ph/parseopt
> 
> Hmm. Any reason why you didn't just extend on "git rev-parse"?

Because I wasn't aware of the fact it was used to massage arguments of a function :) Though looking at the code git-rev-parse looks quite complicated and does not works the proper way:

It show()s the arguments along the way, whereas you definitely need to parse them first if you end up spitting out the usage. I could of course plumb it as a new "mode" of git-rev-parse, but it sounds awkward.

> That command was written exactly to parse a command line. This is really 
> cheesy, and doesn't really work right (it splits up numbers too), but you 
> get the idea..
  I get the idea, though parse-options is not incremental at all, this
could probably be done, but would complicate the API (we would need to
allocate a state object e.g.). And parseoptions checks that options
getting an argument have one, checks that options exists and so on. It
looks like to me that it's not easy to plumb into rev-parse without
being a brand new independant mode.
  We can do that, if we don't want yet-another-git-builtin/command, but
in the spirit it'll remain a brand new "thing".
  Though I'd be glad to hear about what others think about it.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Linus TorvaldsNext: Johannes Schindelin
Message 6 of 8 in “Bring parse_options to the shell”
  1. Pierre HabouzitNov 2, 2007
  2. Add git-parseopt(1) to bring parse-options to shell scripts.Pierre Habouzit, Nov 2, 2007
  3. Update git-sh-setup(1) to allow transparent use of git-parseopt(1)Pierre Habouzit, Nov 2, 2007
  4. Pierre HabouzitNov 2, 2007
  5. Linus TorvaldsNov 2, 2007
  6. Pierre HabouzitNov 2, 2007
  7. Johannes SchindelinNov 2, 2007
  8. Pierre HabouzitNov 2, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.