From: dick <dick.r.chiang@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49001@debbugs.gnu.org
Subject: bug#49001: 28.0.50; MML grinds on empty url tags
Date: Sun, 13 Jun 2021 08:55:48 -0400 [thread overview]
Message-ID: <8735tlgbzf.fsf@dick> (raw)
In-Reply-To: <87tum22axp.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 13 Jun 2021 14:42:10 +0200")
LI> Your test case doesn't seem to call
LI> `mml-expand-html-into-multipart-related'
I couldn't for the life of me figure out how to go from MML to shr-rendered
html. MML and MIME are both gibberish to this pattern matching monkey.
next prev parent reply other threads:[~2021-06-13 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 12:27 bug#49001: 28.0.50; MML grinds on empty url tags dick
2021-06-13 12:42 ` Lars Ingebrigtsen
2021-06-13 12:55 ` dick [this message]
2021-06-13 13:00 ` Lars Ingebrigtsen
2021-06-13 13:23 ` dick.r.chiang
2021-06-13 13:35 ` Lars Ingebrigtsen
2021-06-13 13:58 ` dick.r.chiang
2021-06-14 12:40 ` 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=8735tlgbzf.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=49001@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 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).