unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Antoine Beaupré" <anarcat@debian.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: WIP fixes for rfc822/attachement display
Date: Fri, 09 Jul 2021 19:36:39 -0400	[thread overview]
Message-ID: <87bl7bnjp4.fsf@angela.anarc.at> (raw)
In-Reply-To: <87h7h34wg4.fsf@tethera.net>

On 2021-07-09 07:23:55, David Bremner wrote:
> Antoine Beaupré <anarcat@debian.org> writes:
>
>> On 2021-07-06 12:49:23, David Bremner wrote:
>>> 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?
>>
>> I actually fumble upon similar errors somewhat frequently, but it's the
>> first time it's reproducible. Typically, it happens under other, more
>> neboulous circumstances and the fix then is to restart emacs (!).
>>
>> Are you saying the fix is to upgrade to emacs 28?
>
> Pretty much. Along with a patch to notmuch, if you care about the
> display of !!! error messages. Of course, Emacs 28 is unreleased
> software, so may have other uncomfortable aspects.

I'm not at a place in my life where I compile my own Emacs. Once a upon
a time, that was a thing, before I found out about binary
distributions. But those days are (fortunately) over. ;)

a.

-- 
A developed country is not a place where the poor have cars. It's
where the rich use public transportation.
                        - Gustavo Petro 

      reply	other threads:[~2021-07-09 23:36 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     ` WIP fixes for rfc822/attachement display David Bremner
2021-07-09  0:35       ` Antoine Beaupré
2021-07-09 10:23         ` David Bremner
2021-07-09 23:36           ` Antoine Beaupré [this message]

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=87bl7bnjp4.fsf@angela.anarc.at \
    --to=anarcat@debian.org \
    --cc=david@tethera.net \
    --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).