From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 44109@debbugs.gnu.org
Subject: bug#44109: Add gnus-summary-sort-by-domain
Date: Wed, 21 Oct 2020 06:35:10 +0800 [thread overview]
Message-ID: <87sga84jc1.5.fsf@jidanni.org> (raw)
gnus-summary-sort-by-author is great, but what we really also need is
gnus-summary-sort-by-domain!
That way one could group mails from
nerdsworth@google.com
snitford@google.com
without having
nibblesome@micorsoft.com
butt in!
It would even be "Real name resistant", not fearing if they were called
Harry Nerdsworth, etc.!
As to if fartsworth@accounting.micorsoft.com should sort differently
than fartsworth@micorsoft.com, well we are sorting by domains, not
subdomains...
Gnus v5.13
GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.20)
of 2020-05-17, modified by Debian
next reply other threads:[~2020-10-20 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 22:35 積丹尼 Dan Jacobson [this message]
2020-10-22 12:56 ` bug#44109: Add gnus-summary-sort-by-domain Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sga84jc1.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=44109@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).