Lars Ingebrigtsen writes: >> I think the best thing to do in this case would be to introduce a >> `dead' state for xwidgets, not unlike killed buffers and dead frames, >> which an xwidget is set to after being killed. >> >> Then, performing any sort of operation on a killed xwidget can either >> throw an error, or do nothing. > Sounds good to me.