Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!haven!adm!smoke!brl.mil!moss
From: moss@brl.mil (Gary S. Moss (VLD/VMB) <moss>)
Newsgroups: comp.windows.x
Subject: XSetErrorHandler and access to _XPrintDefaultError routine.
Keywords: XSetErrorHandler, _XPrintDefaultError
Message-ID: <15079@smoke.brl.mil>
Date: 5 Feb 91 16:27:23 GMT
Sender: news@smoke.brl.mil
Reply-To: moss@brl.mil
Organization: Ballistic Research Laboratory
Lines: 17


Ok, here's one,

	I had a need to set up an error handler via XSetErrorHandler to
trap Xerrors so that my application (actually Rob Pike's sam editor that
I'm porting to color X servers) could kill the parent process before
exiting; otherwise the parent process would hang around indefinitely.  I
really wanted to duplicate the error diagnostic reported by
mit/lib/X/XlibInt.c/_XPrintDefaultError(), but as far as I know it is
unadvertised, therefore unsupported.  For now, I am using it with compiler
flags configurable in the makefile ready to punt if it becomes unavailable.

	Can someone at MIT advise me on this, or consider promoting it to
a documented Xlib entry point in R5?

Thanks,
-Gary