From: No Wayman <iarchivedmywholelife@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50842@debbugs.gnu.org
Subject: bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph
Date: Wed, 29 Sep 2021 10:48:00 -0400 [thread overview]
Message-ID: <871r572xj3.fsf@gmail.com> (raw)
In-Reply-To: <87lf3fdium.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> No Wayman <iarchivedmywholelife@gmail.com> writes:
>
>> The basic idea is to provide macros which make declaring a
>> reproduction case easier.
>
> It's an interesting idea, but I think it's unlikely that we'd
> get many
> people to submit bug reports using something as complicated as
> this,
> really.
I agree that elisp novices probably wouldn't author many reports
themselves.
However, there's benefit beyond that.
We use a similar macro for diagnosing bugs with straight.el and
there are users who know enough elisp
to write reports.
The first thing I do when I get a bug report is encode it via that
macro and have the user who reported it run it/share results. That
confirms that there is actually a bug and we're on the same page
about what is expected/happening. It reduces the time wasted on
"Oh yeah, I forgot to mention a step" or "Oh yeah, I forgot to do
that step", etc. It's even more beneficial when you have multiple
users effected by the same bug. IME, It's a lot more efficient to
ask someone "please paste this in your *scratch* buffer, eval, and
copy back the results".
Once the bug is closed, the body of the macro is often still
useful as a regression test, too.
Again, just food for thought.
next prev parent reply other threads:[~2021-09-29 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zgrw9067.fsf@gmail.com>
2021-09-27 10:51 ` bug#50842: 28.0.50; problem with fill-paragraph Peter Münster
2021-09-28 5:59 ` Lars Ingebrigtsen
2021-09-28 6:17 ` Peter Münster
2021-09-28 6:21 ` Lars Ingebrigtsen
2021-09-28 7:03 ` Peter Münster
2021-09-28 7:06 ` Lars Ingebrigtsen
2021-09-28 7:11 ` Eli Zaretskii
2021-09-28 7:12 ` Lars Ingebrigtsen
2021-09-28 7:24 ` Eli Zaretskii
2021-09-28 7:27 ` Lars Ingebrigtsen
2021-09-28 16:19 ` bug#50842: Fwd: " No Wayman
2021-09-29 5:57 ` Lars Ingebrigtsen
2021-09-29 14:48 ` No Wayman [this message]
2021-09-29 16:16 ` Eli Zaretskii
2021-09-29 16:44 ` 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=871r572xj3.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=50842@debbugs.gnu.org \
--cc=larsi@gnus.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 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.