Purpose: to discuss the EMACS editing environment.
An Oustervote in 2001 concluded that emacs [L1 ] remains the single most widely-used programming editor among Tcl practitioners, although all vi variants together appear to sum to a larger total.
[Where does one go to find Emacs? What about Emacs on MacOS or Windows?] Is there more than one program that is emacs?
Where to get Emacs:
MacOS and Windows:
Quite a bit of available elisp implements functionality useful to Tcl coders, including syntax highlighting, ...
Just drop elisp specific items into the elisp page, mentioned above.
Ok, I'm not really in tune with wiki writing style, so I'll just dump stuff here (davidw):
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. For example, I'm not that happy with the standard highlight regexp's. I use instead Donal Fellows highlighting code from http://www.cs.man.ac.uk/~fellowsd/tcl/#fontlock . And there are other, mostly minor problems.
That said, the tcl-mode has some very nice features, that really ease your work, if you are an emacs addicted, like me. Do you ever have debugged a tk application? It's very easy to start the hole script from inside emacs (with the tcl mode command tcl-send-buffer, by default bound to C-c M-a). Now you click throu your GUI, filling in data here and there. 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. 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. Normally, this means exit your application, edit the code, restart your application, click throu the GUI again, fill in the necessary data here and there and then you reach the point of interest again.
Not so, if you have started your applicatiom from emacs tcl mode. Don't exit your application, after you have encountered the error. 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. Now - without restarting the application and clicking throu again - just retry the malicious GUI action, that has triggered the error before and see the outcome. (Of course, this is only possible due to the dynamic nature of tcl, and is not special to the emacs tcl mode. Emacs tcl mode only makes it very easy to use this tcl feature.) de.