Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Lars-Johan Liman <info-gnus-english@cafax.se>
To: info-gnus-english@gnu.org
Subject: Sorting threads ... again.
Date: Fri, 25 Nov 2016 16:46:54 +0100	[thread overview]
Message-ID: <22ziknpno1.fsf@limac.netnod.se> (raw)

Hi!

New to the list, but not to GNUS (close to 15 years), and certainly not
to Emacs (30+ years - TOPS-20, anyone? ;-).

Sorry if this is a FAQ. I often solve most of my problems by Googling,
but I've revisited the following one several times over several years,
but I still haven't solved it. Call me stupid, I've been called worse
things ... ;-)

Sorting threads.

I'd like to have my summary buffer sorted such that:

*) An entire thread is viewed as "one unit".

   The sorting key for the entire thread unit is the "tail" of the
   thread - the highest article number in the thread.

*) The sorting key for a "loose article" (which is not part of a thread)
   is its article number.

*) Thread units and loose articles are seen equal, and sorted in
   increasing order (highest article number last), something like this
   (exaggerated example):


!  1113: [The Boss            ] Announcement
!  1114: [My Friend           ] Thanks for ...
!A 1103: [Foo Bar             ] Issue 1
   1104:     <Baz Bump           > 
   1115:         [Mubbe Mupp       ]      <--- sorting key
   1116: [Customer            ] Invitation to ...
!A 1101: [Foo Bar             ] Issue 2
   1102:     <Baz Bump           > 
   1117:         [Mubbe Mupp       ]      <--- sorting key


I thought I'd be able to use something like

(setq gnus-thread-sort-functions
      '((not gnus-thread-sort-by-most-recent-number)))

... but it doesn't work. Nor does any other combination of the sorting
functions that I've tried.

Any ideas?

Also note that my groups are sometimes very large. My most frequented
group ("inbox-2016") sits at highest index = ~33000, with 12000+ of them
being "not deleted", so if there are any size limitations (besides
processing time) I need to know about, mentioning them would be welcome.
;-) Trying to read the source code, I see mixed recursion limitations of
5000, but I take them to be "size of ONE thread", not "size of group".
Me being wrong on that would explain some behaviour I've seen during my
attempts, though ...

				Best regards,
				  /Liman
#-------------------------------------------------------------------------
# Lars-Johan Liman, M.Sc.		 ! E-mail: info-gnus-english@cafax.se
# Cafax AB				 ! HTTP  : //www.cafax.se/
# Computer Consultants, Sweden		 ! Voice : +46 8 - 564 702 30
#-------------------------------------------------------------------------


                 reply	other threads:[~2016-11-25 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=22ziknpno1.fsf@limac.netnod.se \
    --to=info-gnus-english@cafax.se \
    --cc=info-gnus-english@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.
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 NNTP newsgroup(s).