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

Re: parse-options does not recognize "unspecified" behavior

From
Pranit Bauva <pranit.bauva@gmail.com>
Date
Mar 16, 2016, 21:37 UTC
Message-ID
<CAFZEwPOySiVwLJOw0seRu+c-NTK_vnsdi3Gsvv_tpJt6KY=Chg@mail.gmail.com>
In-Reply-To
<20160316212308.GA4538@sigill.intra.peff.net>
On Thu, Mar 17, 2016 at 2:53 AM, Jeff King <peff@peff.net> wrote:
Show 9 quoted lines
> I don't think that would produce the wrong behavior, but it seems like a
> very complicated solution to a problem that can easily be solved by just
> following the usual conventions (that verbose starts at 0, options make
> it go up or down, and "--no-" resets it to zero).
>
> Perhaps it would make more sense if I understood what your goal was in
> setting verbose to -1 in the first place.
>
> -Peff

I am working on the micro project "configuration for commonly used command line options like "git commit -v". I sent out a final patch without considering the multiple verbosity behavior of `git commit`. To take consideration for that behavior, Junio suggested this approach [1]. I was trying to write code for this when I noticed this behavior. I did a `git grep " unspecified " just to find that using -1 is not that common. I think this problem can also arise in future if some more options are included. The question still remains whether its worth all this effort?

[1] : http://thread.gmane.org/gmane.comp.version-control.git/288820/focus=288909
Previous: Pranit Bauva
Message 18 of 18 in “parse-options does not recognize "unspecified" behavior”
  1. Pranit BauvaMar 16, 2016
  2. Jeff KingMar 16, 2016
  3. Pranit BauvaMar 16, 2016
  4. Jeff KingMar 16, 2016
  5. Eric SunshineMar 16, 2016
  6. Pranit BauvaMar 16, 2016
  7. Jeff KingMar 16, 2016
  8. Stefan BellerMar 16, 2016
  9. Jeff KingMar 16, 2016
  10. Stefan BellerMar 16, 2016
  11. Jeff KingMar 17, 2016
  12. Eric SunshineMar 17, 2016
  13. Jeff KingMar 17, 2016
  14. SZEDER GáborMar 19, 2016
  15. Pranit BauvaMar 19, 2016
  16. SZEDER GáborMar 25, 2016
  17. Pranit BauvaMar 25, 2016
  18. Pranit BauvaMar 16, 2016

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.