Just edit the according proc (and fill some debugging puts in it, if you feel the needs, you will see the output in a special emacs buffer) and send the changed proc with tcl-send-buffer (per default bound to C-c M-a) to the running interpreter. Don't exit your application, after you have encountered the error. Not so, if you have started your applicatiom from emacs tcl mode. Normally, this means exit your application, edit the code, restart your application, click through the GUI again, fill in the necessary data here and there and then you reach the point of interest again. Tk's error message may give you the reason, what's going wrong or at least an idea what debugging 'puts' to insert, to get more insight. Then you click, let's say, a button, and you have to realize, that there is an error in the command bound to that button. Now you click through your GUI, filling in data here and there. Have you ever have debugged a tk application? It's very easy to start the whole script from inside emacs (with the tcl mode command tcl-send-buffer, by default bound to C-c M-a). That said, the tcl-mode has some very nice features, that really ease your work, if you are an emacs addict, like me. And there are other, mostly minor problems. I use instead Donal Fellows highlighting code from. For example, I'm not that happy with the standard highlight regexp's. It is true, that some details of the standard tcl-mode of emacs (I'm talking about GNU emacs, don't know much about Xemacs) could profit of a little bit work by an elisp guru.
0 Comments
Leave a Reply. |