unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
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 18:11:04 +0800	[thread overview]
Message-ID: <87sfoeno3r.fsf@yahoo.com> (raw)
In-Reply-To: <877d5qetfm.fsf@dick> (dick r. chiang's message of "Wed, 08 Jun 2022 17:28:29 -0400")

dick.r.chiang@gmail.com writes:

> Subject: [PATCH] Avoid the hanging chad of "*Backtrace*"

Most people do not use paper punches anymore, and are likely to think of
the urban slang meaning of "chad" instead.  Mysterious commit messages
do not belong in our source code.

> * lisp/emacs-lisp/debug.el (debugger-buffer-name): DRY.
> (debug): Don't just erase the *Backtrace*; kill it.
> * test/lisp/abbrev-tests.el (copy-abbrev-table-test):
> We have `ignore-errors` for this purpose.
> (abbrev-tests-backtrace-bury): Test it.
> ---
>  lisp/emacs-lisp/debug.el  | 113 ++++++++++++++++++--------------------
>  test/lisp/abbrev-tests.el |  20 +++++--

So exactly what is the problem, and where is the fix?  And why is
`abbrev-tests.el' related?

>  2 files changed, 68 insertions(+), 65 deletions(-)
>
> diff --git a/lisp/emacs-lisp/debug.el b/lisp/emacs-lisp/debug.el
> index 6c172d6c31d..c1c977ce66e 100644
> --- a/lisp/emacs-lisp/debug.el
> +++ b/lisp/emacs-lisp/debug.el
> @@ -95,6 +95,8 @@ debug-allow-recursive-debug
>    :type 'boolean
>    :version "29.1")
>  
> +(defconst debugger-buffer-name "*Backtrace*")

No doc string.





  parent reply	other threads:[~2022-06-09 10:11 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
2022-06-09 10:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87sfoeno3r.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55863@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=luangruo@yahoo.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).