Gnus development mailing list
 help / color / mirror / Atom feed
From: Igor Sosa Mayor <joseleopoldo1792@gmail.com>
To: ding@gnus.org
Subject: Re: sort search output by date
Date: Thu, 23 Oct 2014 08:09:33 +0200	[thread overview]
Message-ID: <87h9yvgvvm.fsf@pedroche.home> (raw)
In-Reply-To: <87y4s7cpta.fsf@pierrot.dokosmarshall.org>

Nick Dokos <ndokos@gmail.com> writes:

> Nick Dokos <ndokos@gmail.com> writes:
>
>> When I do a gmane nnir search with G G, the resulting nnir group is in
>> some random(?) order.
>>
>> An imap search returned an almost sorted buffer: a sorted bunch at the
>> beginning, a sorted bunch at the end, but a couple of messages between
>> the two that were out of order - that was a single example though: I
>> don't know how general this behavior is.
>>
>> How do I get the nnir summary buffer sorted by date?
>>
>
> I didn't find a hook or option to do that, so in the end I added
> gnus-summary-sort-by-date as an :after advice to
> gnus-group-make-nnir-group.

I have something like this...

--8<---------------cut here---------------start------------->8---
(add-hook
 'gnus-summary-mode-hook
 (lambda ()
   (when (string-match "^gwene.*" gnus-newsgroup-name)
     (make-local-variable 'gnus-show-threads)
     (make-local-variable 'gnus-use-adaptive-scoring)
     (make-local-variable 'gnus-use-scoring)
     (make-local-variable 'gnus-score-find-score-files-function)
     (setq gnus-show-threads nil
	   gnus-use-adaptive-scoring nil)
;	   gnus-use-scoring nil)
     (gnus-summary-sort-by-date))))

--8<---------------cut here---------------end--------------->8---

maybe you can adapt it...
-- 
:: Igor Sosa Mayor     :: joseleopoldo1792@gmail.com ::
:: GnuPG: 0x1C1E2890   :: http://www.gnupg.org/      ::
:: jabberid: rogorido  ::                            ::




      reply	other threads:[~2014-10-23  6:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  3:23 Nick Dokos
2014-10-23  5:34 ` Nick Dokos
2014-10-23  6:09   ` Igor Sosa Mayor [this message]

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=87h9yvgvvm.fsf@pedroche.home \
    --to=joseleopoldo1792@gmail.com \
    --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).