From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: "Antoine Beaupré" <anarcat@debian.org>
Subject: Re: WIP fixes for rfc822/attachement display
Date: Tue, 06 Jul 2021 12:49:23 -0300 [thread overview]
Message-ID: <87pmvv5toc.fsf@tethera.net> (raw)
In-Reply-To: <20210704131639.3400795-1-david@tethera.net>
David Bremner <david@tethera.net> writes:
> This is not finished/correct yet, but maybe it will save someone else
> some debugging.
>
> [PATCH 2/3] emacs: don't inline message/rfc822 parts without content
>
I have confirmed that thanks to larsi's quick fix, patch 2/3 alone makes
things copacetic in emacs master. I have marked the other two patches as
obsolete, although if people thing this case is important enough, we
could try to work around the issues with pre-28 emacs in a more
careful way.
Antoine, is this a common annoyance for you, or a rare issue?
d
next prev parent reply other threads:[~2021-07-06 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 20:11 [PATCH 1/2] test/crypto: test message with rfc822 attachment David Bremner
2021-07-03 20:11 ` [PATCH 2/2] test: known broken test for emacs display of message/rfc822 parts David Bremner
2021-07-04 9:24 ` Tomi Ollila
2021-07-04 13:32 ` David Bremner
2021-08-30 23:32 ` David Bremner
2021-07-04 13:16 ` WIP fixes for rfc822/attachement display David Bremner
2021-07-04 13:16 ` [PATCH 1/3] emacs: forcibly set notmuch-show-mode after delegating inlining David Bremner
2021-07-04 13:16 ` [PATCH 2/3] emacs: don't inline message/rfc822 parts without content David Bremner
2021-08-30 23:37 ` David Bremner
2021-07-04 13:16 ` [PATCH 3/3] emacs: dynamically bind gnus-newsgroup-charset David Bremner
2021-07-06 15:49 ` David Bremner [this message]
2021-07-09 0:35 ` WIP fixes for rfc822/attachement display Antoine Beaupré
2021-07-09 10:23 ` David Bremner
2021-07-09 23:36 ` Antoine Beaupré
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmvv5toc.fsf@tethera.net \
--to=david@tethera.net \
--cc=anarcat@debian.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).