Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: gnus-summary-thread-gathering-function and digests
Date: 17 Dec 1999 17:29:46 +0000	[thread overview]
Message-ID: <uso118ohh.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: Raymond Scholz's message of "16 Dec 1999 19:00:37 +0100"

Raymond> Raymond Scholz <URL:mailto:rscholz@tzi.de>

0> In article <m3ln6urcje.fsf.emacs.gnus@rscholz.dyndns.org>, Raymond
0> wrote:

Raymond> My first thought was to set the threading function in the
Raymond> group parameters.  But digests behave strange (maybe I should
Raymond> say smart), as they generate a new nndoc group for every
Raymond> digest.  This new group doesn't inherit it's fathers group
Raymond> parameter.

Set it in a score file, substituting "all" for the article number you
get in the nndoc group's name.

The easiest way to do this is to create a score file by using the 'I'
or 'L' command, then renaming the resulting file afterwards.




      reply	other threads:[~1999-12-17 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16 18:00 Raymond Scholz
1999-12-17 17:29 ` Toby Speight [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=uso118ohh.fsf@lanber.cam.eu.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /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).