The debugger window should appear.
Then type either C-x 0 or C-x k RET to get rid the window (or the
buffer).
Do NOT type q.
Then evalute ring-bell-function.
It's nil.
That is because you are still inside the call to `error'.
You have not yet exited from the `let'.
On 12 Jul 2005, at 19:06, Richard M. Stallman wrote:
(defadvice error (around ring-bell (&rest args) activate protect)
(let ((ring-bell-function nil))
(ding)
ad-do-it))
lets ring-bell-function set to nil after (error "xxx") is called.
I can't reproduce that. If I have
(defadvice error (around ring-bell (&rest args) activate protect)
(let ((ring-bell-function nil))
(ding)
ad-do-it))
lets ring-bell-function set to nil after (error "xxx") is called.
I can't reproduce that. If I have set ring-bell-function to a non-nil value
befor
This code
(defadvice error (around ring-bell (&rest args) activate protect)
(let ((ring-bell-function nil))
(ding)
ad-do-it))
lets ring-bell-function set to nil after (error "xxx") is called.
When I change the scope of (let ..) to not include ad-do-it,
everything is fine of course.
