pager and stderr

[Bryan O'Sullivan]

Is it expected that the pager extension captures both stdout and stderr?

I ask because I've added some code that, if Mercurial is sent SIGUSR1, it
prints a traceback to stderr, which is helpful in figuring out what a
long-running command is doing.

Unfortunately, this is clearly going to the pager when it's enabled (i.e.
always), which results in the process blocking until I notice that I need
to hit page-down.

The only references I can find to this behaviour are as follows:

https://bz.mercurial-scm.org/show_bug.cgi?id=2541
https://selenic.com/repo/hg/rev/994510694b1d

It seems highly undesirable to me to have stderr go through the pager. Am I
alone?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20151120/74fdedf9/attachment.html>