Thus said Marc Baaden on Fri, 09 Dec 2022 08:28:23 +0100:
> For some messages, when I reply to the sender quoted, I get an
> unreadable quote in base64, although the initial message contained
> plain text. I have not a complete view under which precise conditions
> this happens, but t
Thank you for your feedback.
My EXMH version is 2.8.0.
I am not sure I understand how you reply, and what shortcut
corresponds to (I don't seem to have it on my version). Do you first
choose a plain reply to sender, then in the editor for the reply use
this shortcut? It may correspond to the
>For some messages, when I reply to the sender quoted, I get an
>unreadable quote in base64, although the initial message contained
>plain text. I have not a complete view under which precise conditions
>this happens, but the latest example was a multi-part message with
>one text/plain and one te
Thus said Marc Baaden on Fri, 09 Dec 2022 17:06:07 +0100:
> My EXMH version is 2.8.0.
I'm still using 2.7.2. Not sure if perhaps a bug exists in later
versions.
> I am not sure I understand how you reply, and what shortcut
> corresponds to (I don't seem to have it on my versi
Thus said Ken Hornstein on Fri, 09 Dec 2022 11:06:59 -0500:
> I'm a LITTLE puzzled by Andy's response ... Andy, are you using sedit?
Yes, I primarily use sedit for composing and responding to messages.
Occasionally when I need more control over the message I will use
More->Alternate Ed
> NB: in general if readers on this list have customized variants of
> scripts/commands for replying/quoting, and are willing to share, I'd
> be most interested.
Getting good quoted replies in NMH is unfortunately a complex art
(that NMH makes more difficult than necessary for reasons). You can
> The reason I supply the extra two arguments is that NMH makes life
>difficult for us here. The ideal situation would be that your formatproc
>is invoked in exactly the same way as your showproc, so that if you have
>a custom showproc that does things you like, you can directly reuse it.
>Unfortun