From: No Wayman <iarchivedmywholelife@gmail.com>
To: 50842@debbugs.gnu.org
Subject: bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph
Date: Tue, 28 Sep 2021 12:19:05 -0400 [thread overview]
Message-ID: <87v92k8yce.fsf@gmail.com> (raw)
In-Reply-To: <87pmsuz3z8.fsf@a16n.net>
Apologies. I used the "Reply" button on the bug archive page and
didn't realize it would just reply to Lars.
I hope I'm forwarding this to the right address so it can be seen
by all in the thread.
> Ah, that's the missing detail.
Apologies if this is an unwelcome intrusion, but I'm currently
working on a package
to prevent this type of confusion during bug reproduction:
https://www.github.com/progfolio/yodel
The basic idea is to provide macros which make declaring a
reproduction case easier.
It runs the test and provides a formatted report which others can
run and compare results.
The reports can be re-formatted easily after they've been run.
Yodel currently supports github markdown, reddit markdown, Org
syntax, and can easily be extended to support other formats.
As a case study, I wrote a test for this bug.
The yodel-file macro removes the ambiguity of "Copy this into a
buffer, do this with point here, etc".
The yodel macro runs the test locally in a temporary, clean Emacs
environment, and presents the formatted report.
Here's the resultant report in Org syntax:
* YODEL REPORT [2021-09-28 11:12:45]
#+begin_src emacs-lisp :lexical t :results silent
(yodel
:post*
(yodel-file
:point "|"
:with*
"From: xxx
To: xxx
Subject: xxx
You wrote:
> | bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
> bla bla bla bla bla
> bla bla bla bla bla bla bla bla bla bla bla bla bla
> bla bla bla bla bla
> bla bla bla bla bla bla bla bla bla bla bla bla bla
> bla bla bla bla bla "
:then*
(message-mode)
(fill-paragraph)
(print
(buffer-substring-no-properties
(point-min)
(point-max)))))
#+end_src
** STDOUT:
#+begin_src emacs-lisp :lexical t :results silent
"From: xxx
To: xxx
Subject: xxx
--text follows this line--
You wrote:
> bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
> bla
bla bla bla > bla bla bla bla bla bla bla bla bla bla bla bla bla
bla
bla bla bla bla > bla bla bla bla bla bla bla bla bla bla bla bla
bla
bla bla bla bla bla"
#+end_src
** Environment
- =emacs version=: GNU Emacs 28.0.50 (build 1,
x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.4, Xaw3d
scroll bars)
of 2021-09-23
- =system type=: gnu/linux
Just food for thought on how we could better approach reproducing
bugs.
Thanks,
Nick
next prev parent reply other threads:[~2021-09-28 16:19 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 ` No Wayman [this message]
2021-09-29 5:57 ` bug#50842: Fwd: " Lars Ingebrigtsen
2021-09-29 14:48 ` No Wayman
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
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=87v92k8yce.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=50842@debbugs.gnu.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 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).