pmprintf & pmconfirm

[fche@xxxxxxxxxx (Frank Ch. Eigler)]

Hi -

On IRC, nathans & scox were talking about recent pmatop/pmcollectl
changes now causing pmconfirm dialogs popping up, hanging qa.

I took a glance at related code and got wondering.  What led to the
creation of pmprintf() / pmflush(), and the desire to turn some error
conditions detected in the library into a suspension of the program
(and interruption of the user) for some interactive dialogs?  (I'm not
aware of any other general purpose library that does this.)

pcpintro makes the PCP_STDERR=DISPLAY setting sound like it's for
startup errors only (related to how pure X/desktop apps may lack a
usable stderr), but pmprintf/pmflush() are used in non-startup
contexts too.  By the way, why is __pmNotifyErr disconnected from
pmprintf()?


- FChE