hi,
I often use slime as I used ILISP: have two windows in a frame, split vertically, one containing the lisp source, the other containing the *inferior-lisp*. When slime pops up a buffer, e.g. a debug buffer and I exit it, slime closes the window with my code in it and I am left with just an *inferior-lisp* buffer in the frame.
Although I'm used to typing <restart> C-x 3 C-x b RET (luckily the last "code" buffer is the default) now, it's pretty tedious.
Other than that, I'm very happy with SLIME right now. Great work, guys.
Thanks,
Andreas Fuchs asf@boinkor.net writes:
I often use slime as I used ILISP: have two windows in a frame, split vertically, one containing the lisp source, the other containing the *inferior-lisp*. When slime pops up a buffer, e.g. a debug buffer and I exit it, slime closes the window with my code in it and I am left with just an *inferior-lisp* buffer in the frame.
One command that might help is `C-c M-0' (not a spectacularly convenient binding). SLIME generally saves the previous window configuration when it changes things, and this command restores it.
We should possibly put window configurations in a ring instead, since this only lets you go back one level.
Any suggestions on better window-management would be welcome.
-Luke
Today, Luke Gorrie luke@bluetail.com wrote:
One command that might help is `C-c M-0' (not a spectacularly convenient binding). SLIME generally saves the previous window configuration when it changes things, and this command restores it.
It seems to restore a random old window config, in my case. Specifically, the window config that I had before I opened a new lisp buffer and made the debugger pop up with a form I evaluated there. Hm.
We should possibly put window configurations in a ring instead, since this only lets you go back one level.
Sounds like a plan.
Any suggestions on better window-management would be welcome.
Perhaps just leave the window config stuff alone as much as possible - getting it right is really hard. Only close windows that you opened yourself sounds like a good rule of thumb to me.
Thanks,