Recommended repository viewer?

[Simon King]

On Fri, Dec 12, 2014 at 3:59 PM, Angel Ezquerra
<angel.ezquerra at gmail.com> wrote:
>
> El 12/12/2014 16:47, "Chris Angelico" <rosuav at gmail.com> escribió:
>
>
>>
>> Greetings!
>>
>> I'm quite possibly asking this question in completely the wrong way,
>> but is there a recommended equivalent to gitk for Mercurial? There's
>> "hg view"/hgk, but apparently it's not something that gets
>> development:
>> http://mercurial.selenic.com/wiki/HgkExtension
>>
>> Is this because there's a better graphical viewer, or do Mercurial
>> people eschew such things altogether?
>>
>> What I'm looking to put together is a script which pulls the latest
>> changes from upstream, then shows me what those changes are -
>> preferably interactively. I could write a script to "hg pull -u" and
>> then do everything manually, but I'd much prefer to use something that
>> already exists. For reference, my equivalent git script looks like
>> this:
>>
>> cur=`git rev-parse HEAD`
>> git pull "$@"
>> gitk --select-commit=$cur
>>
>> On the python.org peps repository, it's usually not a problem to just
>> manually "hg pull -u", look how many new changesets were added, open
>> up "hg view", and hit the down-arrow key as many times as the number
>> of pulled changes; but on the cpython repo, where branch merges are
>> common, it gets messier and I'd really like to script it.
>>
>> The immediate problem with using "hg view" for this is simply that it
>> doesn't support the --select-commit parameter that gitk does, and is
>> unlikely to grow it, given that the extension is "unloved" (d'awwww).
>> Hence my hope that there's an alternative to hg view, one that the
>> devs would recommend actually be used.
>>
>> Am I barking up the wrong tree here?
>>
>> Chris Angelico
>
> You should check TortoiseHg (http://tortoisehg.bitbucket.org ), which is a
> mercurial GUI with a very good (IMHO) repository viewer.
>
> Cheers,
>
> Angel
>

It's a shame that "thg log" doesn't support a "-r" switch to specify
the revisions that you want to view. If it did, the equivalent of
Chris' git script would be something like:

  cur=`hg log -r tip --template "{rev}"`
  hg pull -u "$@"
  thg log -r "$cur:"

I know you can already enter revsets in the thg workbench, so it would
"simply" need to take the command line parameter and pre-fill the
revset search field...

Simon