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

Re: [PATCH 4/5] Let git-add--interactive read colors from configuration

From
DZDan Zwell <dzwell@gmail.com>
Date
Nov 23, 2007, 05:32 UTC
Message-ID
<474665E0.1010104@zwell.net>
In-Reply-To
<20071122223050.GC3620@sigill.intra.peff.net>
Jeff King wrote:
Show 20 quoted lines
>>  (2) What should be the second parameter in the form to default
>>      to true?  '1'?  'true'?  Any kind of "true" value in Perl
>>      should be accepted?
>>
>>  (3) Same question as (2) but for defaulting to false.  Any kind
>>      of "false"?
> 
> Hmm. I am tempted to say "yes, any true or any false value" in that the
> point of config_* is to convert git config values to native perl
> representations. OTOH, the moral equivalent of
> 
>   config_color('my.key', 'bold red');
> 
> is probably more appropriately
> 
>   config_bool('my.key', 'true');
> 
> so I am fine doing it that way, as well (though I think it makes us
> duplicate the "translate these strings into bools" code into perl).
> 

As you said, config_* converts git values to perl values. However, that conversion needs only be done for strings in .gitconfig. Is there any reason why the caller of the function would need to pass a string "false"? I just don't see the need for conversion of any kind.

Further, I think that we could return the default variable directly, without parsing it at all. It would be much simpler, and there would need to be no special cases for dealing with undef or 'false'. It's a perl function, being called with perl arguments, so a user should not be that surprised when 'false' does what perl says it should do.

Dan
Previous: Jeff KingNext: Jeff King
Message 55 of 86 in “Color support added to git-add--interactive.”
  1. Color support added to git-add--interactive.Dan Zwell, Oct 13, 2007
  2. Jeff KingOct 13, 2007
  3. Frank LichtenheldOct 13, 2007
  4. Johannes SchindelinOct 13, 2007
  5. Wincent ColaiutaOct 13, 2007
  6. Jean-Luc HerrenOct 13, 2007
  7. Wincent ColaiutaOct 13, 2007
  8. Andreas EricssonOct 13, 2007
  9. Johannes SchindelinOct 13, 2007
  10. Jeff KingOct 13, 2007
  11. Jeff KingOct 13, 2007
  12. Dan ZwellOct 13, 2007
  13. Wincent ColaiutaOct 13, 2007
  14. Dan ZOct 13, 2007
  15. Jean-Luc HerrenOct 13, 2007
  16. Jeff KingOct 15, 2007
  17. Dan ZwellOct 17, 2007
  18. Shawn O. PearceOct 17, 2007
  19. Dan ZwellOct 17, 2007
  20. Shawn O. PearceOct 17, 2007
  21. 1/2 Added basic color support to git add --interactiveDan Zwell, Oct 22, 2007
  22. Dan ZwellOct 23, 2007
  23. Let git-add--interactive read "git colors" from git-configDan Zwell, Oct 23, 2007
  24. Jeff KingOct 23, 2007
  25. Shawn O. PearceOct 23, 2007
  26. Jeff KingOct 23, 2007
  27. Wincent ColaiutaOct 23, 2007
  28. Jeff KingOct 23, 2007
  29. Wincent ColaiutaOct 23, 2007
  30. 2/2 Let git-add--interactive read colors from git-configDan Zwell, Oct 22, 2007
  31. Jeff KingOct 23, 2007
  32. Dan ZwellOct 23, 2007
  33. 1/2 Added basic color support to git add --interactiveDan Zwell, Nov 3, 2007
  34. Jeff KingNov 4, 2007
  35. Junio C HamanoNov 4, 2007
  36. Jeff KingNov 4, 2007
  37. 0/3 Adding colors to git-add--interactiveDan Zwell, Nov 11, 2007
  38. Jeff KingNov 11, 2007
  39. Junio C HamanoNov 11, 2007
  40. Dan ZwellNov 11, 2007
  41. 0/5 Colors for git-add--interactiveDan Zwell, Nov 22, 2007
  42. Jeff KingNov 22, 2007
  43. Junio C HamanoNov 22, 2007
  44. 1/5 Added basic color support to git add --interactiveDan Zwell, Nov 22, 2007
  45. 2/5 Don't return 'undef' in case called in a vector context.Dan Zwell, Nov 22, 2007
  46. Jeff KingNov 22, 2007
  47. Junio C HamanoNov 22, 2007
  48. Dan ZwellNov 23, 2007
  49. 3/5 Added config_default($key, $default) to Git.pmDan Zwell, Nov 22, 2007
  50. Jeff KingNov 22, 2007
  51. 4/5 Let git-add--interactive read colors from configurationDan Zwell, Nov 22, 2007
  52. Jeff KingNov 22, 2007
  53. Junio C HamanoNov 22, 2007
  54. Jeff KingNov 22, 2007
  55. Dan ZwellNov 23, 2007
  56. Jeff KingNov 23, 2007
  57. Junio C HamanoNov 23, 2007
  58. 5/5 Added diff hunk coloring to git-add--interactiveDan Zwell, Nov 22, 2007
  59. Jeff KingNov 22, 2007
  60. Junio C HamanoNov 22, 2007
  61. Jeff KingNov 23, 2007
  62. Junio C HamanoNov 22, 2007
  63. 1/3 Added basic color support to git add --interactiveDan Zwell, Nov 11, 2007
  64. 2/3 Let git-add--interactive read colors from .gitconfigDan Zwell, Nov 11, 2007
  65. 3/3 Added diff hunk coloring to git-add--interactiveDan Zwell, Nov 11, 2007
  66. Junio C HamanoNov 11, 2007
  67. 0/3 Adding colors to git-add--interactiveDan Zwell, Nov 11, 2007
  68. Subject: [PATCH 1/3] Added basic color support to git add --interactiveDan Zwell, Nov 11, 2007
  69. Junio C HamanoNov 11, 2007
  70. Subject: [PATCH 2/3] Let git-add--interactive read colors from .gitconfigDan Zwell, Nov 11, 2007
  71. Junio C HamanoNov 11, 2007
  72. Junio C HamanoNov 11, 2007
  73. Dan ZwellNov 13, 2007
  74. Junio C HamanoNov 13, 2007
  75. Dan ZwellNov 13, 2007
  76. Jeff KingNov 13, 2007
  77. Junio C HamanoNov 13, 2007
  78. Dan ZwellNov 13, 2007
  79. Jakub NarebskiNov 13, 2007
  80. 2/2 Let git-add--interactive read colors from .gitconfigDan Zwell, Nov 3, 2007
  81. Junio C HamanoNov 3, 2007
  82. Dan ZwellNov 3, 2007
  83. Junio C HamanoNov 3, 2007
  84. Jeff KingOct 15, 2007
  85. Tom TobinOct 13, 2007
  86. Tom TobinOct 13, 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.