Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: nnir - articles order
Date: Mon, 13 Dec 2010 07:24:08 -0500	[thread overview]
Message-ID: <87aak9dfo7.fsf@andy.bu.edu> (raw)
In-Reply-To: <87hbehdgai.fsf@andy.bu.edu>

>>>>> "Andy" == Andrew Cohen <cohen@andy.bu.edu> writes:

>>>>> "Steinar" == Steinar Bang <sb@dod.no> writes:
>>>>> Bruno Tavernier <tavernier.bruno@gmail.com>:
    >>> For instance gnus displays the oldest first and the newest at
    >>> the bottom and nnir does the opposite.

    Steinar> I'm guessing (I haven't checked the code or earlier
    Steinar> postings by Andrew Cohen on the subject) nnir aims to list
    Steinar> by the way the search engine returns the results (which
    Steinar> depends on the search engine, but usually relevance
    Steinar> calculation has something to do with the returned order).

    Andy> That's right (more or less---there are complications when
    Andy> searching more than one group).

    Andy> Although I haven't played with it, you might be able to sort
    Andy> the summary buffer with the usual sorting functions. I'd be
    Andy> curious to know how well this works.


And it seems to work just fine. IMAP searching doesn't in fact assign a
retrieval score, so the resulting article list can be in any
order. Since the gnus `default' is increasing article number, and this
can be munged by the user into any order, I'll change it to conform to
this in my next push.

So it was both a feature and a bug:)




  reply	other threads:[~2010-12-13 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13  9:07 Bruno Tavernier
2010-12-13  9:11 ` Steinar Bang
2010-12-13 12:10   ` Andrew Cohen
2010-12-13 12:24     ` Andrew Cohen [this message]
2010-12-13 15:18       ` Bruno Tavernier

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=87aak9dfo7.fsf@andy.bu.edu \
    --to=cohen@andy.bu.edu \
    --cc=ding@gnus.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).