In python-mode (for emacs), hitting Control-C\Control-C will execute the current buffer. However, when execution is finished, the output buffer springs up and splits my editing window in half. This is a complete pain, especially given that there’s generally no output in the buffer anyway!
Is there a way to stop the buffer from appearing? Also, how can I send painful electric shocks to the programmer who thought unexpectedly interrupting my train of thought with an empty buffer was a good idea?
Edit: Apparently, there are uses for this behavior, most notably in seeing the output of a program. That’s fine, but if there’s no output (as in the program with which I’m tinkering), it is really dumb to cut my buffer in half with a blank window.
What python-mode are you using? Unfortunately, there are several.
Type C-h k and then C-c C-c .. what does it say in the modeline? Does it say ‘py-execute-buffer’ or does it say ‘python-send-buffer’, the first kind indicates you’re using Tim Peters’ python-mode, while the second indicates you’re using Dave Love’s python-mode.
I myself prefer Dave Love’s python mode, and it’s the version that ships with Emacs 23 (and maybe earlier too?). Dave Love’s does not pop up the buffer when you run C-c C-c, you have to explicitly switch to the *Python* buffer if you want to see it.
If you’re really intent on sticking with Tim Peters’ version, you could always put something like the following in your .emacs and you’ll never see the output buffer again unless explicitly moved to.