From: Dan Callaghan <djc@djc.id.au>
To: list@supmua.dev <list@supmua.dev>,
supmua@googlegroups.com <supmua@googlegroups.com>
Subject: [sup] release 1.4
Date: Tue, 21 Apr 2026 19:50:35 +1000 [thread overview]
Message-ID: <1776764185-sup-7292@honeycomb.djc.id.au> (raw)
Message-ID: <20260421095035.9YveqWem4zwDIoDmBs3o_0knduSasnYEkvZUdot6EWs@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
I've just released Sup 1.4. It includes some fixes for long-standing
bugs, as well as a change in preparation for Xapian 2.0 compatibility.
The new release is available from Rubygems, Github, and:
https://supmua.dev/releases/
== 1.4 / 2026-04-21
* #343: Draft messages containing non-ASCII characters are now displayed
correctly in thread view.
* #533, #524: Sup now refuses to start if config.yaml is missing a default
account, or no sendmail command is configured.
* Improved the lazy-loading behaviour when scrolling down in thread list views.
* Sup now gracefully handles RFC2047-encoded words which contain incomplete
UTF-8 sequences after decoding, instead of crashing with ArgumentError.
* #516: Sup can now load sources.yaml produced by very old versions of Sup,
which left a syntactically invalid YAML tag for the SentLoader class.
* Fixed error handling behaviour for various scenarios where a draft message is
modified outside Sup.
* Sup no longer uses deprecated Xapian APIs, for compatibility with Xapian 2.0.
* Sup is now tested on Ruby 4.0.
* Sup's web site and git repos have moved to: https://supmua.dev/
--
Dan Callaghan <djc@djc.id.au>
--
You received this message because you are subscribed to the Google Groups "The Sup email client" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supmua+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/supmua/1776764185-sup-7292%40honeycomb.djc.id.au.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-04-21 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 9:50 Dan Callaghan [this message]
2026-04-21 9:50 ` Dan Callaghan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1776764185-sup-7292@honeycomb.djc.id.au \
--to=djc@djc.id.au \
--cc=list@supmua.dev \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox