@paniash @oantolin I’ve been using #emacs #gnus for decades and contributed code to it. It’s a great experience and will work with gmail for instance. It has a ridiculous amount of features.
Sending e-mail takes seconds so it’s not particularly annoying that it happens in the main thread.
People have been talking about using the Emacs threads for parallelizing the article fetch, threading, scoring, and sorting for years but no one has done the work. That first time delay (a few seconds for larger groups, can be a minute or more for huge groups) may annoy you if you value performance very highly but I don’t think it’s particularly bad. It’s worth trying,
@oantolin I use both manual and adaptive scoring to manage large email volumes very effectively. The defaults for adaptive scoring are usually okay, at least to start with. Give it a shot. It doesn't affect the actual emails at all [*], only the order in which they are presented.
[*] Edit: not quite true as you need to be careful with your settings for expiring articles in case a low score leads to an article being expired.
Completing-read on all URLs from existing post including article link?
Gnus does this via `w` (gnus-summary-browse-url) in article buffer.
Does elfeed show more details for a feed? (i mean metadata)
One thing I shifted to gnus (with feedbase) was unified look for feeds and email and more info on `t` (gnus-summary-toggle-header)
IIRC @publicvoit published something about following feeds using Gnus. I used to do that. The sticking point is that Emacs will hang while Gnus waits for a feed that may or may not connect or provide its data. elfeed was better about that, but I missed Gnus' adaptive scoring. I'd written an elfeed adaptive scoring package, but was never thrilled about using a separate package for feeds. So I'm giving Gnus and nnrss and nnatom another try.
Browsing URLs from Gnus Summary buffer https://davemq.github.io/emacs/gnus/url/2026/04/29/visiting-urls-from-gnus-summary.html
Gnus tips for Lantern
In case you are trying out my NNTP-based blog engine [Lantern](https://koldfront.dk/git/lantern/about/) with Gnus, here are some useful parameters to set on your Lantern topic/groups:((message-syntax-checks
'((long-lines . disabled) (quoting-style . disabled)))
(posting-style (eval (auto-fill-mode -1)))
(message-shoot-gnksa-feet '(cancel-messages canlock-verify)))
I also have a hook to change the Content-Type: to text/markdown in the Lantern groups when writing:
(defun asjo-lantern-markdown-hook ()
"Insert default Content-Type in lantern groups"
(let ((group (or gnus-newsgroup-name "")))
(when (string-match "nntp.inav:lantern" group) ; Adjust this!
(message-add-header "Content-Type: text/markdown"))))
(add-hook 'message-setup-hook 'asjo-lantern-markdown-hook)
Another thing that makes it work a little smoother is switching to markdown-mode when the Content-Type of an article is text/markdown, so adding this to your ~/.gnus:
; Display text/markdown:
(require 'markdown-mode)
(defun mm-display-markdown (handle)
(mm-display-inline-fontify handle 'markdown-mode))
(add-to-list 'mm-inline-media-tests '("text/markdown" mm-display-markdown identity))
Have fun!