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

Re: [PATCHv2] Makefile: implement help target

From
Jeff King <peff@peff.net>
Date
Sep 29, 2010, 07:34 UTC
Message-ID
<20100929073400.GA28010@sigill.intra.peff.net>
In-Reply-To
<4CA2E4C7.305@drmicha.warpmail.net>
On Wed, Sep 29, 2010 at 09:03:35AM +0200, Michael J Gruber wrote:
Show 9 quoted lines
> > Surely this is why we have perl?
> 
> I don't speak perl.
> 
> Honestly, this is slowly going on my nerves. Maybe it's because I'm
> reading too many "can't we do it this way" responses in one go and
> without being coffeinated, and without seeing how "different" is better.
> [I've been heeding all advise on portability and readability, as you can
> see.]

I should have been more clear about my motivations. It was mainly "I wonder how short I can make this in perl?" The alternate sorting was something that happened incidentally, though it did make more sense to me.

So you can just ignore me if you like. :)
Show 7 quoted lines
> > 	  -e 'for (sort keys(%h)) {' \
> > 	  -e '  print "$$_:\n";' \
> > 	  -e '  printf("    %-20s%s\n", @$$_) for (@{$$h{$$_}});' \
> > 	  -e '}' Makefile
> > 
> 
> How portable are the regexps and the array/dictionary push?

AFAIK, it should work with any perl5. I don't have any ancient versions handy to test these days, though.

Show 8 quoted lines
> > Note that mine will actually print the targets in a heading in the order
> > in which they appear in the Makefile, which I consider slightly more
> > useful (especially in that we can tweak the order easily).
> 
> I don't think Makefile order would be useful. If you know exactly what
> you're looking for you need no sorting, you can just search for that
> term. (I would do a 'grep -A20 "^target:" Makefile' or hit "/^target" in
> my vim but I'm sure there's a different way of doing it in perl...)

What I was trying to say was more that alphabetical is not necessarily the most useful order to present things in the help screen. Probably there is some hand-selected order that presents the entries in the least confusing way. And one way of representing that is to have the topics in that order in the Makefile, which in theory probably makes reading the Makefile itself simpler.

But yeah, this is way over-thinking the issue. It's a fricking list of Makefile targets. I am happy with your original patch.

-Peff
Previous: Michael J GruberNext: Junio C Hamano
Message 19 of 24 in “Makefile: Add help target”
  1. Makefile: Add help targetStephen Boyd, Sep 28, 2010
  2. Junio C HamanoSep 28, 2010
  3. Sverre RabbelierSep 28, 2010
  4. Andreas EricssonSep 28, 2010
  5. Makefile: implement help targetMichael J Gruber, Sep 28, 2010
  6. Sverre RabbelierSep 28, 2010
  7. Zbyszek SzmekSep 28, 2010
  8. Ævar Arnfjörð BjarmasonSep 28, 2010
  9. Junio C HamanoSep 28, 2010
  10. Michael J GruberSep 28, 2010
  11. Ævar Arnfjörð BjarmasonSep 28, 2010
  12. [PATCHv2] Makefile: implement help targetMichael J Gruber, Sep 28, 2010
  13. Sverre RabbelierSep 28, 2010
  14. Jakub NarebskiSep 28, 2010
  15. Brandon CaseySep 28, 2010
  16. Michael J GruberSep 29, 2010
  17. Jeff KingSep 29, 2010
  18. Michael J GruberSep 29, 2010
  19. Jeff KingSep 29, 2010
  20. Junio C HamanoSep 29, 2010
  21. [PATCHv3] Makefile: implement help targetMichael J Gruber, Sep 29, 2010
  22. Junio C HamanoSep 29, 2010
  23. Michael J GruberSep 30, 2010
  24. yj2133011Sep 29, 2010

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.