unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: 12068@debbugs.gnu.org
Subject: bug#12068: 24.1; customizing debug-on-error to nil disables --debug-init
Date: Thu, 02 Aug 2012 19:16:54 -0400	[thread overview]
Message-ID: <4qr4rox4t5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2y5m5cn1x.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Fri, 27 Jul 2012 10:10:18 -0400")

Dave Abrahams wrote:

> If you happen to customize debug-on-error to nil and save it, and then
> something goes wrong at startup, running emacs with --debug-init has no
> apparent effect and you're stuck (at least, once the customizations have
> been read in). 

I cannot reproduce this, and there is code in startup.el to handle this.

I tried:

cat ~/.emacs

(error "foo")

(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(debug-on-error nil))
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )


If I use:

emacs --debug-init, I end up in the debugger's backtrace buffer.





  reply	other threads:[~2012-08-02 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 14:10 bug#12068: 24.1; customizing debug-on-error to nil disables --debug-init Dave Abrahams
2012-08-02 23:16 ` Glenn Morris [this message]
2012-08-02 23:28   ` Glenn Morris
2012-08-03  2:56     ` Dave Abrahams
2012-08-03 20:08       ` Glenn Morris
2012-08-03 20:23         ` Dave Abrahams
2014-02-01  8:05         ` Lars Ingebrigtsen

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=4qr4rox4t5.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=12068@debbugs.gnu.org \
    --cc=dave@boostpro.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 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).