* bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger
@ 2009-04-12 2:01 Daniel Clemente
2011-09-16 20:24 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Clemente @ 2009-04-12 2:01 UTC (permalink / raw)
To: emacs-pretest-bug
Eval anything with (debug) on it, like:
(let* ((x 3) (y 1))
(debug)
(dotimes (a x) (setq y (* y x)))
y
)
When the debugger appears, press e to evaluate some symbol. You can type x RET to see the value of x. But now try a symbol which doesn't exist, for instance z. You get:
Debugger entered--Lisp error: (void-variable z)
eval(z)
eval-expression(z)
debugger-eval-expression(z)
call-interactively(debugger-eval-expression nil nil)
recursive-edit()
And at this point, your debugger session is (apparently) lost and you can't continue debugging your program: e.g. "c" doesn't work and it only says (error "Cannot return from the debugger in an error")
It is very annoying that Emacs makes you restart debugging just because you did a typing error in a very infortunate moment. Even if there is some way to get out of this „error inside the evaluated expression“, the default behaviour is shocking.
Can't errors like void-variable / void-function be ignored by default in debugger-mode?
-- Daniel
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger
2009-04-12 2:01 bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger Daniel Clemente
@ 2011-09-16 20:24 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Magne Ingebrigtsen @ 2011-09-16 20:24 UTC (permalink / raw)
To: dcl441-bugs; +Cc: 2966
Daniel Clemente <dcl441-bugs@yahoo.com> writes:
> Eval anything with (debug) on it, like:
>
> (let* ((x 3) (y 1))
> (debug)
> (dotimes (a x) (setq y (* y x)))
> y
> )
>
> When the debugger appears, press e to evaluate some symbol. You can
> type x RET to see the value of x. But now try a symbol which doesn't
> exist, for instance z. You get:
>
> Debugger entered--Lisp error: (void-variable z)
> eval(z)
> eval-expression(z)
> debugger-eval-expression(z)
> call-interactively(debugger-eval-expression nil nil)
> recursive-edit()
>
> And at this point, your debugger session is (apparently) lost and
> you can't continue debugging your program: e.g. "c" doesn't work and
> it only says (error "Cannot return from the debugger in an error")
This was marked as notabug wontfix, but it's apparently been fixed
anyway. :-)
You now get a further bug and your environment isn't lost:
Debugger entered--Lisp error: (void-variable z)
eval(z nil)
eval-expression(z nil)
call-interactively(eval-expression nil nil)
recursive-edit()
debug()
eval((debug) nil)
eval-expression((debug) nil)
call-interactively(eval-expression nil nil)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-09-16 20:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-12 2:01 bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger Daniel Clemente
2011-09-16 20:24 ` Lars Magne Ingebrigtsen
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.