"inwit" writes:
> Thanks! However, if I understood it correctly, this means sending mail in
> html,
> and I was hoping to forward them in plain text, by stripping html and leaving
> a
> legible txt form (such as the one displayed in notmuch-show).
I guess we could quibble about whether that
David Bremner writes:
> "inwit" writes:
>>
>>
>>> If you can find a sharable message
>>> that is problematic for you, that might help understand the problem
>>> better.
>> Any html-only message is displayed (fw'd?) as an attachment.
>>
>
> In fact any message is forwarded as an attachment,
"inwit" writes:
>
>
>> If you can find a sharable message
>> that is problematic for you, that might help understand the problem
>> better.
> Any html-only message is displayed (fw'd?) as an attachment.
>
In fact any message is forwarded as an attachment, whether html or not.
So I'm wondering
On Sat Dec 4, 2021 at 8:05 PM CET, David Bremner wrote:
> OK. I suspect the messages you are having trouble with are ill-formed (or the
> recipients mail client is not good at MIME). I just tried forwarding an HTML
> only message to myself and the HTML inside is rendered fine (in
> notmuch-emacs).
On Sat Dec 4, 2021 at 8:39 PM CET, martin f krafft wrote:
> I use
> [htmldump](https://git.madduck.net/etc/mutt.git/blob/HEAD:/.config/mutt/htmldump)
> to render HTML mail to markdown, and then mutt's new multipart/alternative
> handling and [this
>
Since set -u is used, without bash or perl, configure would fail.
This has gone unnoticed as (almost) everyone always had both
bash and perl installed (and in $PATH).
Thanks to FreeBSD ports this bug became visible; this change is
verbatim copy of `patch-configure` in FreeBSD ports tree.
---
Rainer Gemulla writes:
> Navigating certain messages (e.g., with many attachments or images)
> may become very slow in notmuch-show-mode. I see this rarely, but when
> it happens, it takes >1s to simply move the point so that the buffer
> is barely usable. The CPU profiler shows that
>
Navigating certain messages (e.g., with many attachments or images) may become
very slow in notmuch-show-mode. I see this rarely, but when it happens, it
takes >1s to simply move the point so that the buffer is barely usable. The CPU
profiler shows that notmuch-show-command-hook calls redisplay
Thomas Schwinge writes:
> Hi!
>
> Regarding the following ideas -- from almost a decade ago ;-) -- is
> anyone aware of any work in that area?
[snip]
> Austin wrote:
>> I think this would be fantastic. I've proposed unconditionally
>> showing the earliest subject before and it seems that
Hi!
Regarding the following ideas -- from almost a decade ago ;-) -- is
anyone aware of any work in that area?
On 2012-09-25T15:31:37-0400, Austin Clements wrote:
> Quoth Olivier Berger on Sep 25 at 6:03 pm:
>> Whenever a participant changes the subject in the middle of a thread,
>> the
10 matches
Mail list logo
