[slime-devel] Isolating small behavior changes

[Bill Clementson]

Hi Jonathon,

On 12/19/06, Jonathon McKitrick <jcm at 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