From: "Matt Armstrong" <matt+dated+1010595772.908bba@lickey.com>
Cc: ding@gnus.org
Subject: Re: "subscribed" has overloaded meaning in gnus?
Date: Fri, 04 Jan 2002 10:02:46 -0700 [thread overview]
Message-ID: <87wuyyaw21.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <wc37kqy2k2a.fsf@eta.cis.ohio-state.edu> (Benjamin Rutt's message of "Fri, 04 Jan 2002 10:49:01 -0500")
Benjamin Rutt <rutt+news@cis.ohio-state.edu> writes:
> I'm using a couple month-old Oort 0.04. I'm a little confused as to
> what 'subscribed' means as a group parameter.
Yes I think it should be documented. There was a recent post to
'ding' that documented the MFT stuff. I don't know if this parameter
was documented there or not.
The group parameter "subscribed" simply means "consider the to-address
or to-list parameter of this group to be that of a mailing list you're
subscribed to." The only place it is currently used in Gnus is in
gnus-find-subscribed-addresses.
Perhaps the parameter should be "mailing-list-subscribed" or
"address-subscribed" or "to-addresses-subscribed" something else?
> (setq gnus-parameters '(("^nnml:mlist-.*" (subscribed . t))))
> (add-hook 'gnus-started-hook
> (lambda ()
> (setq message-subscribed-regexps
> (gnus-find-subscribed-addresses))))
Instead of the hook, I think this ended up being the "preferred" way
of doing it.
(setq message-subscribed-address-functions
'(gnus-find-subscribed-addresses))
Your method is technically wrong since gnus-find-subscribed-addresses
does not return a set of regexps (but it'll mostly work).
--
matt
next prev parent reply other threads:[~2002-01-04 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 15:49 Benjamin Rutt
2002-01-04 17:02 ` Matt Armstrong [this message]
2002-01-04 18:41 ` Benjamin Rutt
2002-01-11 12:44 ` Sriram Karra
2002-01-12 2:14 ` Benjamin Rutt
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=87wuyyaw21.fsf@squeaker.lickey.com \
--to=matt+dated+1010595772.908bba@lickey.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).