slime + clisp + emacs: server disconnects

Stuart Little achirvasub at gmail.com
Tue Jul 23 15:37:34 UTC 2019


On Tue, Jul 23, 2019 at 06:07:10PM +0300, A.C. wrote:
> I'll try that when I get some time and get back to this list if / when there's anything to report.
> 

Done!

Here's the report from git-bisect (it's somewhere between v2.20 and v2.21):

--- cut ---

2e7f94633acebd5cf4074ce9601b021624ad8233 is the first bad commit
commit 2e7f94633acebd5cf4074ce9601b021624ad8233
Author: Stas Boukarev <stassats at gmail.com>
Date:   Thu Jan 11 15:29:00 2018 +0300

    More energy efficient auto-flush-loop.
    
    Don't spin until there's something to flush.

 contrib/swank-repl.lisp |  8 +++++---
 swank.lisp              |  4 +++-
 swank/gray.lisp         | 21 +++++++++++++++++----
 3 files changed, 25 insertions(+), 8 deletions(-)

--- cut ---

> On July 23, 2019 5:59:38 PM GMT+03:00, "Luís Oliveira" <luismbo at gmail.com> wrote:
> >On Tue, Jul 23, 2019 at 3:51 PM Stuart Little <achirvasub at gmail.com>
> >wrote:
> >> I understand that :), but the purpose was to gain some insight into
> >how or why it's happening.
> >
> >Could you try and use git bisect to find what's upsetting your clisp?
> >
> >Luís
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.



More information about the slime-devel mailing list