James it's been a while since I set this up :( My own ~/.hgrc file has: $ cat ~/.hgrc [extensions] hgk = /usr/lib/python2.4/vendor-packages/hgext/hgk.py
[hgk] path = /usr/lib/python2.4/vendor-packages/hgext/hgk I assume even if hgk is part of the mercurial delivered with nevada, you will still need to setup the above extension. This is something we could easily do from the mercurial plugin as we already need to do write to the users .hgrc file to setup some global property settings, such as [ui] username. JR James Falkner wrote: > OK I got it to work by adding this to ~/.hgrc: > > [extensions] > hgext.hgk=/usr/lib/python2.4/vendor-packages/hgext/hgk.py > > Predumably that won't be needed if this functionality is added > to base Nevada. > > -jhf- > > Darren J Moffat wrote: > >> James Falkner wrote: >> >>> I keep getting 'Error reading commits: hg: unknown command >>> 'debug-rev-list'. >>> >>> Apparently hgk tries to run 'hg debug-rev-list' which is not a valid >>> hg command, at least in 0.9.3. Googling is no help. Anyone have a >>> clue what >>> my problem is? >>> >> I saw that as well. >> >> The first error I saw was about not finding .hg (it apparently can't >> work out to use `hg root` to find it) until I went to `hg root`. >> >> > _______________________________________________ > tools-discuss mailing list > tools-discuss@opensolaris.org > _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
