Example: the failure email generated by this build:
libtelnet-reflex/.build.yml #62451: FAILED in 4m52s [ec59ae2](https://git.sr.ht/~jack/libtelnet-reflex/commit/ec59ae2ed0c56624276d4861f3508d50fa24bb2e) — [Jack Kelly](mailto:email@example.com) <pre>Put all deps into update script </pre> https://builds.sr.ht/~jack/job/62451 ✓ nix-caches ✗ ghc843
I know sr.ht focuses on plain-text email, It would be nice to render the text/plain version with links in footnotes or something.
Hm, a bit of a tough problem. We don't have an authoritative non-markdown source for this text. Perhaps we should let the submitter specify a plaintext version and just do best-effort if they don't include one.
I think that unless there's a canonical plain-text renderer for markdown, you might be stuck. Most of markdown looks pretty nice in plain text, and the only thing that really grates is the use of
<pre>tags in the text/plain part.
If you do not rewrap, maybe indenting the commit message using four spaces instead of using
<pre>tags would work better?
Four spaces sounds like a good idea. The links are more difficult to make look nice. Perhaps we could use the alternative markdown link format, like this:
[ec59ae2] - [Jack Kelly] Put all deps into update script : https://git.sr.ht/~jack/libtelnet-reflex/commit/ec59ae2ed0c56624276d4861f3508d50fa24bb2e : mailto:firstname.lastname@example.org
Four spaces is the biggest win. Replacing entities with unicode is a smaller but noticeable win. Rendering links into footnotes (
etc.) is good but the smallest win.
I think what I'm looking for isemails from sr.ht, as a service that sends in.
text/plainonly shouldn't look like they have HTML leaking into them
Well we might as well improve the shit out of it if we're going to improve it at all. The problem isn't reallyemails from sr.ht should not look like HTML, but thatthe email should look good. HTML looks bad, but it's the symptom, not the problem.