From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 9463@debbugs.gnu.org
Subject: bug#9463: 24.0.50; Errors should not be continuable
Date: Mon, 19 Sep 2011 17:17:00 -0400 [thread overview]
Message-ID: <jwvaaa0jn71.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2ty8kgsmt.fsf@gmail.com> (Helmut Eller's message of "Sat, 10 Sep 2011 20:27:22 +0200")
> Incidentally, C-M-c does pretty much the same as what c does currently.
It does something similar but not identical and hence re-introduces some
of the problems that the change you don't like aimed to solve.
It's important to have a "c" that can "keep going (as much as possible)
as if nothing happened".
As you've shown, you can actually get your old behavior with something like
(defadvice debugger-continue (before dont-continue-after-error activate)
(if (eq (car debugger-args) 'error)
(error "Can't continue from an error")))
> So, no new command to get the current behavior would be needed.
Indeed. I've installed a change to catch the most common cases where
debugger-return-value doesn't make sense.
Stefan
next prev parent reply other threads:[~2011-09-19 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 12:01 bug#9463: 24.0.50; Errors should not be continuable Helmut Eller
2011-09-08 13:31 ` Stefan Monnier
2011-09-08 18:13 ` Helmut Eller
2011-09-09 2:23 ` Stefan Monnier
2011-09-09 6:53 ` Helmut Eller
2011-09-09 14:07 ` Stefan Monnier
2011-09-09 16:37 ` Helmut Eller
2011-09-09 21:44 ` Stefan Monnier
2011-09-10 18:27 ` Helmut Eller
2011-09-19 21:17 ` Stefan Monnier [this message]
2011-09-20 6:49 ` Helmut Eller
2011-09-20 21:53 ` Stefan Monnier
2011-09-21 8:05 ` Helmut Eller
2011-09-21 19:09 ` Stefan Monnier
2011-09-21 19:53 ` Helmut Eller
2012-02-22 2:20 ` Glenn Morris
2011-09-09 7:10 ` Eli Zaretskii
2011-09-09 7:36 ` Helmut Eller
2011-09-09 7:59 ` Eli Zaretskii
2011-09-09 8:22 ` Helmut Eller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvaaa0jn71.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9463@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.