From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/79485 Path: news.gmane.org!not-for-mail From: lee Newsgroups: gmane.emacs.gnus.general Subject: Re: Where are group parameters stored? Date: Thu, 14 Jul 2011 21:18:10 +0200 Organization: my virtual residence Message-ID: <87r55sd631.fsf@yun.yagibdah.de> References: <8762ncnb5a.fsf@member.fsf.org> <87r55v1hks.fsf@member.fsf.org> <871uxvrody.fsf@yun.yagibdah.de> <87fwma7ivx.fsf@member.fsf.org> <87liw22bfi.fsf@yun.yagibdah.de> <87vcv5crkv.fsf@member.fsf.org> <877h7kesnt.fsf@yun.yagibdah.de> <87mxggra6c.fsf@member.fsf.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1310671100 29100 80.91.229.12 (14 Jul 2011 19:18:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 14 Jul 2011 19:18:20 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M27781@lists.math.uh.edu Thu Jul 14 21:18:16 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QhRQO-0001LI-CV for ding-account@gmane.org; Thu, 14 Jul 2011 21:18:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1QhRQM-00072u-Ip; Thu, 14 Jul 2011 14:18:14 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1QhRQL-00072b-AY for ding@lists.math.uh.edu; Thu, 14 Jul 2011 14:18:13 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QhRQK-0004ra-89 for ding@lists.math.uh.edu; Thu, 14 Jul 2011 14:18:13 -0500 Original-Received: from static.103.179.46.78.clients.your-server.de ([78.46.179.103] helo=static.73.179.46.78.clients.your-server.de) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1QhRQI-0007F1-NL for ding@gnus.org; Thu, 14 Jul 2011 21:18:10 +0200 Original-Received: from lee by yun.yagibdah.de with local (Exim 4.76) (envelope-from ) id 1QhRQI-0000DF-3x for ding@gnus.org; Thu, 14 Jul 2011 21:18:10 +0200 Mail-Followup-To: ding@gnus.org In-Reply-To: <87mxggra6c.fsf@member.fsf.org> (Tassilo Horn's message of "Thu, 14 Jul 2011 20:26:03 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Spam-Score: 0.1 (/) X-Spam-Report: SpamAssassin (3.3.1 2010-03-16) analysis follows Bayesian score: 0.0000 Ham tokens: 0.000-1693--6931h-0s--0d--H*UA:Emacs, 0.000-1524--6241h-0s--0d--H*u:Emacs, 0.000-1406--5758h-0s--0d--H*UA:Gnus, 0.000-1406--5757h-0s--0d--H*u:Gnus, 0.000-1347--5516h-0s--0d--H*u:linux Spam tokens: 0.987-1--0h-1s--0d--H*r:sk:clients, 0.967-5946--1386h-54022s--0d--H*r:quimby.gnus.org, 0.909-976--1206h-16076s--1d--played, 0.908-183--227h-3015s--0d--H*r:sk:static., 0.908-3277--4090h-54281s--0d--HX-Spam-Relays-External:quimby.gnus.org Autolearn status: no -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 2.0 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:79485 Archived-At: Tassilo Horn writes: > lee writes: > >> generic entry. I was wondering whether the order in which the entries >> appear in the list matters or not and if there was any influence to a >> particular group from all the matches or not. > > Yes, the parameters are applied from first to last, so you can use later > entries to override former entries. And using the `rx' macro makes it even easier to create regexps :) >> Then there are little glitches to make things more difficult to figure >> out, like (gcc-self . "some.group") being ignored when the group has a >> posting style that sets headers. > > You set the Gcc: header using posting styles? Or is gcc-self not > applied whenever the posting styles set some other header? The latter > would be a bug, IMHO. The latter, it seems. Not that I played around with it much, I only found that gcc-self was ignored in the particular posting style which is the only one I have so far that sets headers other than Gcc:. I can try it out and eventually send a bug report. On a side note, it seems that `gnus-message-archive-group' is ignored when group parameters use gcc-self, but since I can't get archiving to work yet without messing everything up, I don't really know ...