Re: Dynamically prevent slime debugger

Christopher Laux <[email protected]>
Newsgroups gmane.lisp.slime.devel
Message-ID <CAD6+Ykb+c37jy_6TiY3-w9F2s+PhNg_RbSiXCbQCjJrW_XfPtQ@mail.gmail.com>
Thanks for the input, I've got it working now, albeit in a hackish way. But
I think this is an idea for a feature in slime, other people must have this
problem too: you have a lot of threads running and suddenly they all pop up
the same error you can't sensibly interact with emacs any more...

Chris


On Thu, Mar 6, 2014 at 2:21 AM, Xiaofeng Yang <[email protected]>wrote:

> You could change the *debugger-hook* variable to handle the conditions as
> what you want, e.g.
>
> (defvar *use-slime-debugger* t)
> (setq *debugger-hook*
>                (let* ((slime-debugger-hook *debugger-hook*)
>                       (new-debugger-hook  (lambda (&rest
> args)
>                                             (if *use-slime-debugger*
>                                                 (apply slime-debugger-hook
> args)
>                                                 ; do what you want
>                                                 ))))
>                  new-debugger-hook))
>
>
> But be aware, there might be additional problems you could meet.
>
>
>      Best regards,
> Xiaofeng Yang
>
>
> 2014-03-06 7:19 GMT+08:00 Christopher Laux <[email protected]>:
>
> Hi,
>>
>> is there a good way to prevent slime (or rather swank) from dropping into
>> the slime debugger depending on the value of a variable? Specifically I
>> want to limit the number of open debugger windows to 1 and simply log all
>> further simultaneous errors. Any help appreciated,
>>
>> Chris
>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.