Theodor Thornhill referenced this ticket in commit a11b92d.

Theodor Thornhill referenced this ticket in commit a11b92d.

Theodor Thornhill referenced this ticket in commit d257076.

Yeah! I've seen that as well!

On 22 December 2021 21:41:08 CET, ~larsi outgoing@sr.ht wrote:

The mail is from the sr.ht server:

Received: from mail-b.sr.ht ([173.195.146.151]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from outgoing@sr.ht) id 1n08MH-0003SA-0e for larsi@gnus.org; Wed, 22 Dec 2021 21:37:11 +0100

So you've sent the mail to sr.ht, and it has apparently mangled it before sending it on to me?

Apparently. In notmuch, I press R, then type, then C-c C-c. (this one is sent from K9 on android)

What specifically is mangled, so that I know we are talking about the same things? Also would help me pass it on to the devs.

Wasn't the message I was looking at in the URL sent from/via Sourcehut? The Received header seems to say so?

Your messages on emacs-devel look fine, but they haven't been via Sourcehut.

No, The only messages I've sent from the web forms are the ones from the ~emacs user. Strange. But to me it looks mostly like a line-wrapping thing? Or is it something else you are thinking of?

~larsi outgoing@sr.ht writes:

The emails I'm getting in response to this thread also look extraordinarily ugly: https://quimby.gnus.org/s/hut.jpg

It looks like the HTML has been rendered into text/plain with a very odd folding algorithm (when just sending them out as HTML might have been better).

That is strange. For me it looks exactly the same as emacs-devel. This could be a config issue on my end, though I use a pretty vanilla message-mode buffer initiated from notmuch. Do messages sent from me to emacs-devel look better?

~larsi outgoing@sr.ht writes:

I don't think we can expect people to do Markdown just to appease the bug tracker.

It's not like it's difficult to auto-detect diffs in a mail, so it's a bit odd that they haven't implemented that for a forge.

-- View on the web: https://todo.sr.ht/~emacs/emacs/1#event-109230

<ddevault> todo is markdown first, email second
<ddevault> this might change at some point but for now that's how it's
           designed

~larsi outgoing@sr.ht writes:

I don't think we can expect people to do Markdown just to appease the bug tracker.

It's not like it's difficult to auto-detect diffs in a mail, so it's a bit odd that they haven't implemented that for a forge.

not so sure, people are used to it from github etc. But that could be an issue as well. I'll ask them.

diff --git a/slime.el b/slime.el
index 8436b332..216b6ad0 100644
--- a/slime.el
+++ b/slime.el
@@ -60,7 +60,6 @@
 ;;;; Dependencies and setup
 (eval-and-compile
   (require 'cl-lib nil t)
-  ;; For emacs 23, look for bundled version
   (require 'cl-lib "lib/cl-lib"))
 
 (eval-and-compile

-- View on the web: https://todo.sr.ht/~emacs/emacs/1#event-109230

~lyefrat that might be smart