From: Eli Zaretskii <eliz@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 08:45:00 +0300 [thread overview]
Message-ID: <83fske4cgz.fsf@gnu.org> (raw)
In-Reply-To: <877d5qetfm.fsf@dick> (dick.r.chiang@gmail.com)
> From: dick.r.chiang@gmail.com
> Date: Wed, 08 Jun 2022 17:28:29 -0400
>
> Subject: [PATCH] Avoid the hanging chad of "*Backtrace*"
^^^^^^^^^^^^^^^^^^^^^^
What does this mean?
> * lisp/emacs-lisp/debug.el (debugger-buffer-name): DRY.
Say what?
> (debug): Don't just erase the *Backtrace*; kill it.
Why?
> lisp/emacs-lisp/debug.el | 113 ++++++++++++++++++--------------------
Where's the meat? Will you ever learn to separate small changes from
large refactoring, so that your patches could be reviewed in
reasonable time and with reasonable effort? Will you ever learn to
respect comments left behind by others and not blindly delete them for
no good reason?
Until you do learn all that, expect most if not all of your
submissions to be turned down. If you want to contribute to a
project, you will need to learn to play by its rules.
next prev parent reply other threads:[~2022-06-09 5:45 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fske4cgz.fsf@gnu.org \
--to=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.