[slime-devel] Isolating small behavior changes
Suppose there was a tiny behavior change in SLIME that I did not see documented in ChangeLog. How would I go about tracking down the cause? Specifically, after compiling a system, a window opens showing the compiler messages. This window used to close with just a 'q' keystroke. This no longer works the same way. I'd like to restore the old behavior. Would someone point me in the right direction? Jonathon McKitrick -- My other computer is your Windows box.
Specifically, after compiling a system, a window opens showing the compiler messages. This window used to close with just a 'q' keystroke. This no longer works the same way. I'd like to restore the old behavior.
Would someone point me in the right direction?
this is a bug. temp buffer windows should close unless the window configuration changed since they were opened. if i can reproduce it then i may be able to fix it. could you be please more specific? how do you compile the system? when i (asdf:oos 'asdf:load-op :foo) then no window pops up for me. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)
On Tue, Dec 19, 2006 at 06:01:27PM +0100, Attila Lendvai wrote: : >Specifically, after compiling a system, a window opens showing the compiler : >messages. This window used to close with just a 'q' keystroke. This no : >longer works the same way. I'd like to restore the old behavior. : > : >Would someone point me in the right direction? : : this is a bug. temp buffer windows should close unless the window : configuration changed since they were opened. : : if i can reproduce it then i may be able to fix it. could you be : please more specific? how do you compile the system? when i (asdf:oos : 'asdf:load-op :foo) then no window pops up for me. Perhaps I've mistaken the bug. Starting SLIME now opens a scratch window and buffer, and I don't think it did before. It used to have a full-size window showing all REPL output. But now it splits the window into a scratch window and the REPL. That means the compiler output goes into the scratch window, which will not close with a Q keystroke. If I close the scratch window after slime starts but before loading the system, the problem does not occur. Is the newly opened scratch window a feature I missed? Jonathon McKitrick -- My other computer is your Windows box.
Perhaps I've mistaken the bug. Starting SLIME now opens a scratch window and buffer, and I don't think it did before. It used to have a full-size window showing all REPL output. But now it splits the window into a scratch window and the REPL. That means the compiler output goes into the scratch window, which will not close with a Q keystroke. If I close the scratch window after slime starts but before loading the system, the problem does not occur.
it sounds strange. on linux, XEmacs 21.4 (patch 19), sbcl cvs, some fresh slime i get a full window of the repl buffer. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)
On Tue, Dec 19, 2006 at 06:25:53PM +0100, Attila Lendvai wrote: : >Perhaps I've mistaken the bug. Starting SLIME now opens a scratch window : >and : >buffer, and I don't think it did before. It used to have a full-size : >window : >showing all REPL output. But now it splits the window into a scratch : >window : >and the REPL. That means the compiler output goes into the scratch window, : >which will not close with a Q keystroke. If I close the scratch window : >after slime starts but before loading the system, the problem does not : >occur. : : it sounds strange. on linux, XEmacs 21.4 (patch 19), sbcl cvs, some : fresh slime i get a full window of the repl buffer. I tried my linux system (ubuntu, emacs-gtk-snapshot, sbcl 1.0, cvs slime) and had no problem. My main system, however, is OSX-Intel, aquamacs, sbcl 1.0, cvs slime. Does that raise any red flags? Jonathon McKitrick -- My other computer is your Windows box.
Hi Jonathon, On 12/19/06, Jonathon McKitrick <jcm@freebsd-uk.eu.org> wrote:
On Tue, Dec 19, 2006 at 06:25:53PM +0100, Attila Lendvai wrote: : >Perhaps I've mistaken the bug. Starting SLIME now opens a scratch window : >and : >buffer, and I don't think it did before. It used to have a full-size : >window : >showing all REPL output. But now it splits the window into a scratch : >window : >and the REPL. That means the compiler output goes into the scratch window, : >which will not close with a Q keystroke. If I close the scratch window : >after slime starts but before loading the system, the problem does not : >occur. : : it sounds strange. on linux, XEmacs 21.4 (patch 19), sbcl cvs, some : fresh slime i get a full window of the repl buffer.
I tried my linux system (ubuntu, emacs-gtk-snapshot, sbcl 1.0, cvs slime) and had no problem.
My main system, however, is OSX-Intel, aquamacs, sbcl 1.0, cvs slime. Does that raise any red flags?
My system is OSX-PPC, aquamacs, sbcl 1.0, cvs slime (just did cvs up). I don't get the slime scratch window on startup, just the repl (which is the behaviour that I've always gotten); so, unless this is an Intel-specific problem, it would appear to be something in your emacs/slime config that is causing the behaviour that you're seeing. Is the second window that you're seeing the emacs scratch buffer or the slime scratch buffer and what window was being displayed prior to your starting slime? Perhaps you could create a minimal .emacs that re-creates your problem? - Bill
On Tue, Dec 19, 2006 at 10:13:40AM -0800, Bill Clementson wrote: : My system is OSX-PPC, aquamacs, sbcl 1.0, cvs slime (just did cvs up). : I don't get the slime scratch window on startup, just the repl (which : is the behaviour that I've always gotten); so, unless this is an : Intel-specific problem, it would appear to be something in your : emacs/slime config that is causing the behaviour that you're seeing. : : Is the second window that you're seeing the emacs scratch buffer or : the slime scratch buffer and what window was being displayed prior to : your starting slime? It's the emacs scratch buffer. I can start emacs, type text in the scratch buffer, then M-x slime. The frame splits into 2 windows. The top window is the same scratch buffer that was there at startup, the bottom window is *slime-repl sbcl*. : Perhaps you could create a minimal .emacs that re-creates your problem? I'll work on it, but I'm a bit under the gun right now, so it might be a few days. Jonathon McKitrick -- My other computer is your Windows box.
On 12/19/06, Jonathon McKitrick <jcm@freebsd-uk.eu.org> wrote:
On Tue, Dec 19, 2006 at 10:13:40AM -0800, Bill Clementson wrote: : My system is OSX-PPC, aquamacs, sbcl 1.0, cvs slime (just did cvs up). : I don't get the slime scratch window on startup, just the repl (which : is the behaviour that I've always gotten); so, unless this is an : Intel-specific problem, it would appear to be something in your : emacs/slime config that is causing the behaviour that you're seeing. : : Is the second window that you're seeing the emacs scratch buffer or : the slime scratch buffer and what window was being displayed prior to : your starting slime?
It's the emacs scratch buffer. I can start emacs, type text in the scratch buffer, then M-x slime. The frame splits into 2 windows. The top window is the same scratch buffer that was there at startup, the bottom window is *slime-repl sbcl*.
Ah, ok, that's different then. I thought you were getting a scratch buffer displayed when one hadn't been visible previously. What you are seeing is standard behaviour in Aquamacs. You can see the same behaviour with both slime and shell buffers. A number of people have complained about it in the past, but I think it's been present in aquamacs for at least the last couple of releases. It would be better if you took this issue to the aquamacs developers mailing list if you want it "fixed", as it's not a slime problem. -- Bill Clementson
On 19-Dec-06, at 1:13 PM, Bill Clementson wrote:
My system is OSX-PPC, aquamacs, sbcl 1.0, cvs slime (just did cvs up). I don't get the slime scratch window on startup, just the repl (which is the behaviour that I've always gotten); so, unless this is an Intel-specific problem, it would appear to be something in your emacs/slime config that is causing the behaviour that you're seeing.
I have the same setup, except under OSX-Intel, and I get the same behaviour as Bill. M-x slime starts the REPL but I don't see the Slime scratch buffer unless I do M-x slime-scratch. However, I start Slime when I start Aquamacs, and after Slime starts, the frame in which slime resides has two windows: the Emacs *scratch* buffer and the Slime REPL. I adjusted my setup to have only one window in the frame by making this the last thing in my ~/.emacs: (when (slime) (delete-other-windows)) May not be the most robust approach, but it sounds like it may correct the minor annoyance. -- Geoff
On Tue, Dec 19, 2006 at 02:10:01PM -0500, Geoff Wozniak wrote: : (when (slime) (delete-other-windows)) : : May not be the most robust approach, but it sounds like it may : correct the minor annoyance. Thanks, Geoff, that will do the trick. Jonathon McKitrick -- My other computer is your Windows box.
participants (4)
-
Attila Lendvai -
Bill Clementson -
Geoff Wozniak -
Jonathon McKitrick