On Thu, Dec 10, 2009 at 4:13 AM, Tobias C. Rittweiler
<tcr@freebits.de> wrote:
> Hi, I've been using slime casually for some time now and something
> always annoyed me, when the debug window pop up, it changes the size of
> the second window if there's one.
I cannot seem to reproduce this. Could you provide all steps beginning
with M-x slime, then your window changing commands etc, please?
in a source code file buffer
C-x 2
M-7 C-x ^
C-x o
M-x slime
C-x o
eval some wrong code
press zero to close the debug window
the second window size is back to where it was before shrinking it
Maybe that's not a usual way to work for more experienced slimers. It also happen with elisp evaluation by the way. When the mini-buffer auto-completion window pop-up, it sometimes resize the second window, if it's too small I think, but restores window configuration afterward. I find this much less annoying. I didn't thought about looking at how it's made for auto-completion, just remembered that detail today.
> I've searched for a ways to fix this behavior many times, but never
> found any simple solution. So today I've got myself into the code and
> made some changes. It works but the code is not really correct, one
> problem is that if you dig farther than the first cause and then use
> abort, it will hide the remaining debug buffers by restoring windows
> to their prior state. Can someone help me improve that code or show me
> a better way to achieve this?
I don't know what our current policy regarding window configuration is
because we tried so many, and everytime we annoyed someone.
Slime is quite a beast, it must not be easy to maintain with lispers of all kind as users! While I'm still using just a fraction of it's power, I already think it's the best development environment ever.
I thought we were going to _get rid of_ automatically restoring
configuration, and instead wanted to point people to `winner-mode'.