Hi Helmut,
ChangeLog tells that *TRAP-LOAD-TIME-WARNINGS* was added by you way back then in 2004. What puzzles me is that
a) its value is NIL by default which means that load-time warnings are not trapped by default. To what purpose?
b) Why is it only used in C-c C-c, but not in C-c C-k?
Hopefully you can remember the details of your motivation behind that change set,
-T.
* Tobias C. Rittweiler [2009-10-12 18:45+0200] writes:
Hi Helmut,
ChangeLog tells that *TRAP-LOAD-TIME-WARNINGS* was added by you way back then in 2004. What puzzles me is that
a) its value is NIL by default which means that load-time warnings are not trapped by default. To what purpose?
b) Why is it only used in C-c C-c, but not in C-c C-k?
Hopefully you can remember the details of your motivation behind that change set,
I think it had something to do with SBCL's infamous redefinition warnings which are generated at load time and are particularly distracting with C-c C-c. The goal of C-c C-c is usually to redefine a function and getting a warning that the goal was met is unnecessary.
Maybe SBCL has now a cleaner way to adjust the policy in regard to those warnings.
Helmut
On Mon, 2009-10-12 at 19:11 +0200, Helmut Eller wrote:
- Tobias C. Rittweiler [2009-10-12 18:45+0200] writes:
Hi Helmut,
ChangeLog tells that *TRAP-LOAD-TIME-WARNINGS* was added by you way back then in 2004. What puzzles me is that
a) its value is NIL by default which means that load-time warnings are not trapped by default. To what purpose?
b) Why is it only used in C-c C-c, but not in C-c C-k?
Hopefully you can remember the details of your motivation behind that change set,
I think it had something to do with SBCL's infamous redefinition warnings which are generated at load time and are particularly distracting with C-c C-c. The goal of C-c C-c is usually to redefine a function and getting a warning that the goal was met is unnecessary.
Maybe SBCL has now a cleaner way to adjust the policy in regard to those warnings.
You can muffle sb-kernel:redefinition-warning