What are the best and must-have hg / mercurial extensions?

user_93933 0
Viewed 14027

I've been dabbling with hg / mercurial lately, namely in conjunction with Fogcreek's Kiln, and I'm trying to figure out what the must-have extensions are. Its a little tricky sifting through their extension list because I'm not interested in testing any buggy or impractical extensions, even if their description sounds awesome.

So, which hg extensions do you use?

See Using Extensions

mercurial
5 Answers

My own hit list:

The simple ones you must have:

  1. color: colorize output from commands like diff and status, which makes it easier to assess.
  2. pager: browse long output a page at a time.
  3. fetch: pull, update and merge from another repo in one step.
  4. graphlog: display revision graphs in your shell, incredibly useful for looking at the branches in your log history.
  5. hgk: browse the repository with a graphical interface (see also TortoiseHg and Murky)

If you enable pager, you should configure it to not interfere with certain commands:

[pager]
pager = LESS='FSRX' less
ignore = version, help, update, serve, record

The intermediate extensions I highly recommend (and use frequently):

  1. record: lets you interactively select hunks of files to commit - perfect for when you are in the middle of one set of changes, and you end up fixing something that should have its own commit.
  2. extdiff: configure an external diff tool (such as meld)
  3. share: have multiple clones use the same repo history

The Advanced extensions I would not be without:

  1. mq: manage a stack of patches. Very powerful, allows layering of patches on top of the tree.
  2. notify: send email notifications when a repo is changed.
  3. rebase: reapply local changes on top of a new parent revision.
  4. largefiles: work with large binary files outside the hg store

All the above are bundled with Mercurial, and are stable and well-tested. I highly recommend all of them.

Non-core extensions worth investigating:

  1. shelve: selectively put aside changes (at the granularity of hunks) and restore them.
  2. acl: selectively allow access to different parts of the repository tree

Superseded extensions and migrated to core (info from @durin42):

  • forest was been superseded by the subrepo support introduced in v1.3
  • bookmarks is in core and always enabled
  • transplant is superseded by graft, a core command
  • histedit is in core as of v2.3, but is disabled by default
  • inotify is not recommended, as there is apparently a bug due to a race condition
user_1726420
Related