Yes, this bugs me so much I routinely disable wdinfo_z_ -which is what produces the message.
wdinfo_z_=: empty But other things use wdinfo, so it's a good idea to alter it to show the message in the Term window. Put this in your startup file: wdinfo_z_=: smoutput_z_ I use a more nuanced version, which flags the message as coming via wdinfo: wdinfo_z_=: 3 : 0 NB. intercept wdinfo to prevent UI lockout if handler fails echo=. 0 0 $ 1!:2&2 echo '>>> wdinfo_z_ intercepted; y==' echo y ) On Sat, 21 Dec 2019 at 18:11, Michal Wallace <michal.wall...@gmail.com> wrote: > Here's a little jqt program with a bug in it. > > When I accidentally run something like this, I get a modal dialog with an > error message. > > Closing the message box triggers the error again. > > Once that happens, the only way I know to recover is kill my whole J > session. > > Is there a better way? If not, could we maybe add a button to these > messages that would destroy the offending window? > > wd 'pc win0 closeok; pn "debug me"' > wd 'cc img isigraph' > wd 'pshow' > win0_img_paint =: verb define > this is a bug > ) > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
