From: Juri Linkov <juri@linkov.net>
To: dick.r.chiang@gmail.com
Cc: 55863@debbugs.gnu.org
Subject: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Thu, 09 Jun 2022 09:46:25 +0300 [thread overview]
Message-ID: <86y1y6fi66.fsf@mail.linkov.net> (raw)
In-Reply-To: <877d5qetfm.fsf@dick> (dick r. chiang's message of "Wed, 08 Jun 2022 17:28:29 -0400")
> ;; Don't let `inhibit-message' get in our way (especially important if
> ;; `non-interactive-frame' evaluated to a non-nil value.
> - (inhibit-message nil)
> + inhibit-message
> ;; We may be entering the debugger from a context that has
> ;; let-bound `inhibit-read-only', which means that all
> ;; buffers would be read/write while the debugger is running.
> - (inhibit-read-only nil))
> + inhibit-read-only)
Often an explicit nil value is used as an indication that it
overrides the default value. This helps to read source code.
next prev parent reply other threads:[~2022-06-09 6:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 21:28 bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace* dick.r.chiang
2022-06-09 5:45 ` Eli Zaretskii
2022-06-09 6:46 ` Juri Linkov [this message]
2022-06-09 10:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 12:59 ` Lars Ingebrigtsen
2022-06-09 13:51 ` dick
2022-06-09 16:01 ` Lars Ingebrigtsen
2022-06-09 16:58 ` Juri Linkov
2022-06-09 17:34 ` Lars Ingebrigtsen
2022-06-09 17:58 ` Juri Linkov
2022-06-09 18:44 ` Lars Ingebrigtsen
2022-06-09 18:50 ` Drew Adams
2022-06-09 18:57 ` Eli Zaretskii
2022-06-09 19:02 ` Lars Ingebrigtsen
2022-06-09 18:56 ` Eli Zaretskii
2022-06-09 19:17 ` Eric Abrahamsen
2022-06-09 19:34 ` dick
2022-06-09 21:02 ` Eric Abrahamsen
2022-06-10 9:27 ` Lars Ingebrigtsen
2022-06-10 10:03 ` dick
2022-06-10 10:06 ` Lars Ingebrigtsen
2022-06-10 10:24 ` dick
2022-06-10 11:39 ` dick
2022-06-14 12:39 ` 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=86y1y6fi66.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=55863@debbugs.gnu.org \
--cc=dick.r.chiang@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 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).