D6324: help: register the 'gpg' command category and give it a description

martinvonz (Martin von Zweigbergk) phabricator at mercurial-scm.org
Tue May 7 12:43:13 EDT 2019


martinvonz added a comment.


  In https://phab.mercurial-scm.org/D6324#92372, @Sietse wrote:
  
  > In https://phab.mercurial-scm.org/D6324#92158, @martinvonz wrote:
  >
  > > [registering the `gpg` command category] doesn't actually seem to work for making it appear in `hg help`.
  >
  >
  > Perhaps, instead of doing work to group extension commands by category, the commands should be grouped under the extension. Nearly all my (enabled and disabled) extensions have 5 commands or less; only evolve and mq have more (17 + 7 debug, and 26, respectively). (Almost) None of them use any command categories. Only GPG does, but that uses the same category for all its commands.
  >
  > The only reason that the help pages currently group extension functions by command category is that gendoc.py currently uses the same `commandprinter` function first to print the main command table, and then once per extension to render the extension's commands. I would be willing to separate that functionality so that extensions could have their own rendering function, which ignores categories. Shall I take that on?
  
  
  I think it makes sense for extensions to be able to add commands to existing categories (e.g. evolve's `next`/`prev` commands seem like they should be in the same category as `update`), so I don't want to lose that (as I think you suggested).
  
  > 
  > 
  >> ! In https://phab.mercurial-scm.org/D6324#92354, @rdamazio wrote:
  >>  I need to migrate Google's extension out of the internal version of help (now that I've upstreamed the help changes), I'll definitely need to mess with categories for that, too.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D6324

To: Sietse, #hg-reviewers, martinvonz
Cc: rdamazio, martinvonz, mercurial-devel


More information about the Mercurial-devel mailing list