From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Problem with gnus-parameters
Date: Tue, 29 Nov 2011 13:47:48 +0900 [thread overview]
Message-ID: <b4mty5n8rgr.fsf@jpl.org> (raw)
In-Reply-To: <878vn0c9as.fsf@thinkpad.tsdh.de>
Tassilo Horn wrote:
> This suggests that the `gnus-parameters' are applied with the same
> semantics as `gnus-posting-styles':
> ,----[ (info "(gnus)Posting Styles") ]
>| Each style will be applicable if the first element "matches", in some
>| form or other.
No, as for `gnus-parameters' the last match is applied now:
2010-09-26 Lars Magne Ingebrigtsen <larsi@gnus.org>
* gnus.el (gnus-group-fast-parameter): Return the last matching
parameter instead of the first matching parameter.
In addition, the value of any parameter for a `gnus-parameters'
element that doesn't have that parameter is treated as nil. So,
> (setq gnus-parameters
> `((,(rx "nnimap+")
> (gnus-use-scoring nil)
> (gcc-self . t))
> ;; Where to expire
> (,(rx "nnimap+Uni:")
> (expiry-target . "nnimap+Uni:Trash"))
> (,(rx "nnimap+Fastmail:")
> (expiry-target . "nnimap+Fastmail:INBOX.Trash"))
> (,(rx "nnimap+Gmail:")
> (expiry-target . "nnimap+Gmail:[Google Mail]/Trash"))
> ;; Mailing List exceptions
> (,(rx "nnimap+Uni:ml/")
> (gcc-self . "nnimap+Uni:Sent"))
> (,(rx "nnimap+Fastmail:INBOX.mailinglists.")
> (gcc-self . "nnimap+Fastmail:INBOX.Sent Items")
> (gnus-use-scoring t))))
for the "nnimap+Gmail:foo" group for example, there are two matching
element; one sets gcc-self to t but the last one resets it to nil.
Maybe the solution is to add (gcc-self . t) to every element having
no gcc-self. I verified it with this form:
(let ((gnus-parameters YOUR-SETTING))
(with-temp-buffer
(gnus-inews-insert-gcc "nnimap+Gmail:foo")
(buffer-string)))
next prev parent reply other threads:[~2011-11-29 4:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 19:54 Tassilo Horn
2011-11-29 4:47 ` Katsumi Yamaoka [this message]
2011-11-29 8:37 ` Tassilo Horn
2012-01-03 21:15 ` Lars Magne Ingebrigtsen
2012-01-04 7:33 ` Tassilo Horn
2012-01-04 20:03 ` Lars Magne Ingebrigtsen
2012-01-05 10:00 ` Tassilo Horn
2012-01-06 20:41 ` Lars Magne Ingebrigtsen
2012-01-06 20:43 ` Lars Magne Ingebrigtsen
2012-01-06 22:27 ` Tassilo Horn
2012-01-06 22:44 ` Lars Magne Ingebrigtsen
2012-01-06 22:52 ` Tassilo Horn
2012-01-06 23:13 ` Lars Magne Ingebrigtsen
2012-01-06 23:37 ` Tassilo Horn
2012-01-07 0:36 ` Lars Magne Ingebrigtsen
2012-01-07 8:08 ` Tassilo Horn
2012-01-06 22:20 ` Tassilo Horn
2012-01-06 22:31 ` Lars Magne Ingebrigtsen
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=b4mty5n8rgr.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).