would anybody have problems with associating the slime-scratch buffer with the file ~/.slime/slime-scratch.lisp? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Luke Gorrie <luke@synap.se> writes:
marco <mb@bese.it> writes:
would anybody have problems with associating the slime-scratch buffer with the file ~/.slime/slime-scratch.lisp?
Good idea IMO.
I think that SLIME's scratch buffer should be for stuff that you don't want to save -- just like Emacs' scratch buffer is. Maybe SLIME's scratch buffer could have a little explanation in it like Emacs' `initial-scratch-message' ?
John Paul Wallington <jpw@gnu.org> writes:
I think that SLIME's scratch buffer should be for stuff that you don't want to save -- just like Emacs' scratch buffer is.
Now that you mention it that's probably right. :-) Here's what I've put in my .emacs to get the scratch-file effect: (set-register ?s '(file . "~/.slime/slime-scratch.lisp")) so that `C-x r j s' opens that file. As that stands it won't use slime-scratch-mode, but I don't use that anyway since `C-j' is hardwired in my brain for newline-and-indent. Cheers, Luke
Luke Gorrie wrote:
John Paul Wallington <jpw@gnu.org> writes:
I think that SLIME's scratch buffer should be for stuff that you don't want to save -- just like Emacs' scratch buffer is.
Now that you mention it that's probably right. :-)
On the other hand, I've used various development environments (Smalltalk-80, MPW, MacScheme) that could maintain a transcript that remembered its contents across sessions, and that can be handy, too. For example, my MPW worksheet evolved into a repository of handy one-liner cliches that used all the time.
participants (4)
-
John Paul Wallington -
Luke Gorrie -
marco -
mikel