In one of the last iterations of slime I lost the capability to interactively resolve conflicting symbols.
This is on sbcl 1.0.34 and slime a few days old.
Is that something broken (I would welcome pointers on how to chase it down), or some switch that I need to set.
Thanks,
Mirko
On Tue, Feb 9, 2010 at 11:49 PM, Mirko Vukovic mirko.vukovic@gmail.com wrote:
In one of the last iterations of slime I lost the capability to interactively resolve conflicting symbols.
This is on sbcl 1.0.34 and slime a few days old.
Is that something broken (I would welcome pointers on how to chase it down), or some switch that I need to set.
That's caused by a bug in sbcl, https://bugs.launchpad.net/sbcl/+bug/511072
Mirko Vukovic mirko.vukovic@gmail.com writes:
In one of the last iterations of slime I lost the capability to interactively resolve conflicting symbols.
This is on sbcl 1.0.34 and slime a few days old.
Is that something broken (I would welcome pointers on how to chase it down), or some switch that I need to set.
Thanks,
Mirko
Besides the issue that Stas reported, it's also that COMPILE-FILE catches and muffles errors happening in compile-time-too evaluation during EVAL-WHEN since 1.0.34. This means that until that's fixed, you have to use C-M-x instead of C-c C-c to get into the debugger an error happening in EVAL-WHEN.
-T.