Index: slime/ChangeLog diff -u slime/ChangeLog:1.717 slime/ChangeLog:1.718 --- slime/ChangeLog:1.717 Tue Jun 28 10:40:07 2005 +++ slime/ChangeLog Fri Jul 1 15:52:55 2005 @@ -1,3 +1,8 @@ +2005-07-01 Gabor Melis mega@hotpop.com + + * swank-sbcl.lisp (threaded stuff): make SBCL 0.9.2.9+ work while + retaining support for 0.9.2 + 2005-06-28 Gabor Melis mega@hotpop.com
* swank-sbcl.lisp (threaded stuff): horrible hack to make threaded
hi,
i often have a lot of buffers open which aren't directly tied to files (mainly erc) or or completly unrealted to whatever i'm working on in that moment. it gets really annoying when slime keeps asking we whether i want to save these buffers or not, this is due to use of save-some-buffers in a copule of slime's functions. i plan on changing the calls to save-some-buffers so that they only attempt to save lisp-mode buffers whcih are tied to a file and i want to make sure that noone relies on slime's current functionality in ways i don't expect (in this case it will become a customizable setting instead of the only possible option).
Marco Baringer mb@bese.it writes:
i plan on changing the calls to save-some-buffers so that they only attempt to save lisp-mode buffers whcih are tied to a file and i want to make sure that noone relies on slime's current functionality in ways i don't expect (in this case it will become a customizable setting instead of the only possible option).
Sounds reasonable to me -- `save-some-buffers' is often annoying. I'd suggest keeping the old behaviour as a config option though.