From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH]: Re: Early backtrace.
Date: Tue, 01 Feb 2022 22:36:39 -0500 [thread overview]
Message-ID: <jwv35l2hri4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <YfmGqaGOfIPqSJ8t@ACM> (Alan Mackenzie's message of "Tue, 1 Feb 2022 19:14:49 +0000")
>> Could we make `debug-early` the default/initial value of `debugger` in
>> the C code, so that reloading `debug-early.el` can be done safely?
>
> I'm not sure what you're asking here. Do you mean set Vdebugger to
> debug-early in syms_of_eval?
Yes.
> How would that make reloading debug-early.el safe?
Because then `debug-early.el` wouldn't have a `setq` at top-level so you
could reload it in a normal Emacs session without having the unfortunate
side-effect of setting `debugger` back to `debug-early`.
IOW it would make `debug-early.el` better follow the convention that
loading an ELisp file should have "no" effect.
Stefan
next prev parent reply other threads:[~2022-02-02 3:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 20:34 Early backtrace Alan Mackenzie
2022-01-10 21:54 ` Stefan Monnier
2022-01-11 11:36 ` Alan Mackenzie
2022-01-11 14:47 ` Stefan Monnier
2022-01-30 11:07 ` [PATCH]: " Alan Mackenzie
2022-01-30 16:31 ` Stefan Monnier
2022-01-31 14:04 ` Stefan Monnier
2022-02-01 19:14 ` Alan Mackenzie
2022-02-02 3:36 ` Stefan Monnier [this message]
2022-02-02 20:38 ` Alan Mackenzie
2022-02-02 20:59 ` Stefan Monnier
2022-02-03 8:38 ` Eli Zaretskii
2022-02-03 21:35 ` Alan Mackenzie
2022-02-04 7:24 ` Eli Zaretskii
2022-02-04 21:01 ` Alan Mackenzie
2022-02-05 7:12 ` Eli Zaretskii
2022-02-05 10:48 ` Alan Mackenzie
2022-02-04 13:31 ` Stefan Monnier
2022-02-04 14:02 ` Eli Zaretskii
2022-01-31 9:30 ` Philipp Stephani
2022-01-31 12:42 ` Eli Zaretskii
2022-01-31 16:54 ` Alan Mackenzie
2022-01-31 17:24 ` Alan Mackenzie
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=jwv35l2hri4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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).