unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: disable debug-on-error in emacs -Q?
Date: Tue, 1 Dec 2015 13:10:55 -0500	[thread overview]
Message-ID: <CAM-tV--J163TC-C2azU0f5A9csdY3Roi91TXizVyvZ=SG9VBeQ@mail.gmail.com> (raw)
In-Reply-To: <864mg2rtx1.fsf@stephe-leake.org>

On Tue, Dec 1, 2015 at 11:54 AM, Stephen Leake
<stephen_leake@stephe-leake.org> wrote:
> I'm testing with:
>
> (+ "foo" 2)
>
> evaluated in the scratch buffer with C-j. Same result evaluating via M-:.

Both of those methods use eval-expression-debug-on-error rather than
debug-on-error, try

(defun foo ()
  (interactive)
  (+ "foo" 2))

And then M-x foo, instead.

>> Emacs doesn't behave differently with -Q in this respect.
>
> It does for me.

Presumable you have set eval-expression-debug-on-error to nil in your init file.

> I found a workaround; eval the expression once to get *Backtraces*.
> Then eval it again without quiting the debugger; that gives the error
> message.

Hitting c (debugger-continue) from *Backtraces* should also work.



  parent reply	other threads:[~2015-12-01 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  6:47 disable debug-on-error in emacs -Q? Stephen Leake
2015-12-01  8:10 ` Andreas Schwab
2015-12-01 16:54   ` Stephen Leake
2015-12-01 18:08     ` Michael Heerdegen
2015-12-01 18:37       ` Stephen Leake
2015-12-01 18:45         ` Michael Heerdegen
2015-12-01 18:46         ` Stephen Leake
2015-12-01 18:10     ` Andreas Schwab
2015-12-01 18:39       ` Stephen Leake
2015-12-01 18:10     ` Noam Postavsky [this message]
2015-12-01 18:46       ` Stephen Leake
2015-12-01 20:59         ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM-tV--J163TC-C2azU0f5A9csdY3Roi91TXizVyvZ=SG9VBeQ@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.org \
    --cc=stephen_leake@stephe-leake.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).