[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph
From: |
No Wayman |
Subject: |
bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph |
Date: |
Wed, 29 Sep 2021 10:48:00 -0400 |
User-agent: |
mu4e 1.7.0; emacs 28.0.50 |
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.
- bug#50842: 28.0.50; problem with fill-paragraph, (continued)
- bug#50842: 28.0.50; problem with fill-paragraph, Peter Münster, 2021/09/28
- bug#50842: 28.0.50; problem with fill-paragraph, Eli Zaretskii, 2021/09/28
- bug#50842: 28.0.50; problem with fill-paragraph, Lars Ingebrigtsen, 2021/09/28
- bug#50842: 28.0.50; problem with fill-paragraph, Eli Zaretskii, 2021/09/28
- bug#50842: 28.0.50; problem with fill-paragraph, Lars Ingebrigtsen, 2021/09/28
bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph, No Wayman, 2021/09/28
bug#50842: 28.0.50; problem with fill-paragraph, Lars Ingebrigtsen, 2021/09/29