all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Michael Heerdegen'" <michael_heerdegen@web.de>
Cc: 13061@debbugs.gnu.org
Subject: bug#13061: 24.3.50; regressions: 1) Redefining a function should cancel`debug-on-entry',2) doc
Date: Sat, 15 Dec 2012 08:05:22 -0800	[thread overview]
Message-ID: <3DD72472241C4BD08F069A74CEBB02F3@us.oracle.com> (raw)
In-Reply-To: <87fw37o2ba.fsf@web.de>

> > It is so simple to hit C-M-x when debugging and modifiying 
> > a function that has `debug-on-entry'.  Doing that should
> > (obviously) cancel opening the debugger on entry.  This has
> > always been the behavior in Emacs, and it should be a no-brainer.
> 
> Just one comment from another user: I like the opposite (that is, the
> new) behavior.  It always annoyed me that e.g. loading file sources
> canceled any according `debug-on-entry' in effect.  I prefer to use
> `cancel-debug-on-entry' explicitly.
> 
> Maybe the behavior could be made configurable?

+1 - users use Emacs differently.

But the default behavior should be the longstanding behavior.
There is no reason to change that.






  reply	other threads:[~2012-12-15 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 19:47 bug#13061: 24.3.50; regressions: 1) Redefining a function should cancel `debug-on-entry', 2) doc Drew Adams
2012-12-09  4:31 ` bug#13061: 24.3.50; regressions: 1) Redefining a function should cancel `debug-on-entry',2) doc Drew Adams
2012-12-14 23:49   ` bug#13061: 24.3.50; regressions: 1) Redefining a function should cancel`debug-on-entry',2) doc Drew Adams
2012-12-15 13:46     ` Michael Heerdegen
2012-12-15 16:05       ` Drew Adams [this message]
     [not found]       ` <<3DD72472241C4BD08F069A74CEBB02F3@us.oracle.com>
2014-07-02 17:57         ` bug#13061: 24.3.50; regressions: 1) Redefining a function shouldcancel`debug-on-entry',2) doc Drew Adams

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=3DD72472241C4BD08F069A74CEBB02F3@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13061@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.