Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: guns-parameters dynamic updates (was: Why do I get *.ADAPT files for nnml groups?)
Date: Mon, 01 Mar 2004 15:48:15 -0500	[thread overview]
Message-ID: <4nhdx8mgz4.fsf_-_@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m23c8sc2y5.fsf@Neocortex.local> (Jonas Steverud's message of "Mon, 01 Mar 2004 10:49:06 +0100")

On Mon, 01 Mar 2004, tvrud@bredband.net wrote:

> (setq
>  gnus-parameters (list
> 		  '("nnfolder:" (gnus-use-scoring nil))
> 		  '("nndraft:" (gnus-use-scoring nil))
> 		  )
> )

This made me wonder, why not have functionality in Gnus that
"gathers" all the group/topic parameters into the gnus-parameters
variable, and then the opposite functionality, that would take
gnus-parameters and apply its values to all the known groups,
whenever they apply?

Would this be useful to anyone?  I would love it, because then I would
set group/topic parameters individually with `G p', and then one
command would gather all my customizations into gnus-parameters.

Ted



  reply	other threads:[~2004-03-01 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  9:07 Why do I get *.ADAPT files for nnml groups? Kai Grossjohann
2004-03-01  9:13 ` Kai Grossjohann
2004-03-01  9:49   ` Jonas Steverud
2004-03-01 20:48     ` Ted Zlatanov [this message]
2004-03-05  6:27       ` guns-parameters dynamic updates Kai Grossjohann
2004-03-05 17:39         ` Ted Zlatanov
2004-03-09  9:19           ` Kai Grossjohann
2004-03-01 10:14   ` Why do I get *.ADAPT files for nnml groups? Yair Friedman
2004-03-02  7:16     ` Kai Grossjohann
2004-03-01 11:27   ` Reiner Steib
2004-03-01 22:38     ` Miles Bader
2004-03-01 23:23       ` Reiner Steib
2004-03-02  0:24         ` Miles Bader
2004-03-02  7:15         ` Kai Grossjohann
2004-03-02  9:08           ` Reiner Steib
2004-03-02  7:17     ` Kai Grossjohann

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=4nhdx8mgz4.fsf_-_@collins.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /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).