Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Subject: Re: Help - specialities entering a group
Date: 22 Dec 1998 06:10:51 -0500	[thread overview]
Message-ID: <oqzp8gwhxg.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: François Pinard's message of "22 Dec 1998 08:53:30 -0500"

François Pinard <pinard@iro.umontreal.ca> écrit:

> I usually read my mailgroups threaded.  I would like that, when entering the
> `i18n.incoming' mailgroup, and only that one, threading be automatically
> suspended, and the equivalent of `C-u C-c C-s C-d' done, so messages be
> sorted most recent first.

Thanks to those who took the time to help.  Here is my current solution,
which is acceptable to me, and installed in my `.gnus' file:


;; Sorting of articles in the summary.
(setq gnus-article-sort-functions
      '((lambda (t1 t2) (not (gnus-article-sort-by-number t1 t2))))
      gnus-thread-sort-functions
      '((lambda (t1 t2) (not (gnus-thread-sort-by-number t1 t2)))))
(defun fp-gnus-select-group-routine ()
  (let ((name gnus-newsgroup-name))
    (setq gnus-show-threads (and (not (string= name "i18n.all"))
				 (not (string= name "i18n.incoming"))))))
(add-hook 'gnus-select-group-hook 'fp-gnus-select-group-routine)


It is based on the fact that I discovered that I like seeing last messages
first, so I activated it everywhere.  Threading works nicely using
this, as the sort is reverse among threads, but forward within threads.
I preferred to not use `G p', even if it is nicer, because my `.gnus'
gets remotely synchronised between systems (including splitting rules),
while `.newsrc.eld' just may not be.

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard


  reply	other threads:[~1998-12-22 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-22 13:53 François Pinard
1998-12-22 11:10 ` François Pinard [this message]
1998-12-22 17:18 ` Jason L Tibbitts III
1998-12-22 17:40 ` David S. Goldberg
1998-12-22 20:29 ` Jack Vinson

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=oqzp8gwhxg.fsf@icule.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    /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).