Dirk-Jan C. Binnema
Dirk-Jan C. Binnema
Merging this, thanks! @llmII: it looks good for me, but surely we can tweak the details later.
So, good news, I integrated `new/mu4e--read-char-choice` and reworked it a bit; it's predicated on `mu4e-read-option-builtin` (which is the default, current behavior; set to non-nil to get the new behavior. Also...
This seems to work fine with the new composer, closing this. Note: mu4e 1.11.23 has a new composer that is much closer to gnus' one, so various message- settings have...
When I replied to this message with those settings, I got: ``` Friday 17 November 2023 à 01:35, [email protected] a écrit : ``` which seems correct (apart from mixing French...
Thanks for the effort! #2167 has been fixed now in a different way, so closing this.
Good news: `mu` 1.11.20 (and a little before) can now use Xapian's NGRAM support for this; see the new `--support-ngrams` option for `mu init`, and the `test_ngrams` unit test.
mu/mu4e try not to warn about "incorrect" queries, in the same way that Google doesn't give you syntax errors for searches. It's hard to come up with a nice UX...
Closing this, as this is not a bug, but the expected behavior for now.
I've fixed this in `master`; we do a `article-remove-cr` earlier in the rendering and that fixes display for both messages.