1mtclx_errorHandler 4m22mmessage0m
The  1mtclx_errorHandler  22mcommand  doesn't  exist  as  built-in  part  of  TclX.
Instead, individual applications or  users  can  define   a  1mtclx_errorHandler0m
command (e.g. as a Tcl procedure) if they wish to handle uncaught errors.  The
procedure will be passed a single argument of the error 4mmessage24m,  with  1merror-0m
1mCode 22mand 1merrorInfo 22mhaving values reflecting the error that occurred.

The  1mtclx_errorHandler  22mcommand  is  called  when  an error that is not caught
returns to the top level command evaluation in the TclX shell or  1mwishx22m.   The
difference  between 1mtclx_errorHandler 22mand 1mbgerror 22mis that 1mtclx_errorHandler 22mis
called during the synchronous execution of a script while 1mbgerror 22mis called as
a  result  of  an uncaught error in an event handler.  In a non-event oriented
Tcl script 1mtclx_errorHandler 22mwill be called on all errors that are not  caught
and  1mbgerror 22mis not used.  In a 1mwishx 22mscript or event oriented script executed
with the TclX shell, 1mtclx_errorHandler 22mwill be called on uncaught errors  dur-
ing  the  execution of the main script that set up the event oriented program.
Once the event loop is entered, 1mbgerror 22mwill be called on uncaught errors.

This procedure is not called in response to commands entered via  an  interac-
tive  command loop, only from the evaluation of scripts or Tcl commands passed
via the command line.  If the procedure returns  normally,  the  program  will
just  exit  without any error being issued by the shell.  Generally the proce-
dure should exit with a non-zero exit code once the error has been  processed.
It is not possible to continue executing the code in which the error occurred.
