From: Tassilo Horn <tassilo@member.fsf.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, ding@gnus.org
Subject: Re: Problem with gnus-parameters
Date: Fri, 06 Jan 2012 23:52:02 +0100 [thread overview]
Message-ID: <8762goqwa5.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m3r4zc8n9r.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 06 Jan 2012 23:44:00 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Is gcc-self active in this group matching both gmane and emacs? For me,
>> its not. And is bar set here? Yes, for me it is.
>
> If I use the following:
>
> (setq gnus-parameters
> '(("gmane" (foo "lala") (bar "zot") (gcc-self . t))
> ("emacs" (foo "emacs") (gcc-self))))
>
> and then enter a non-Emacs Gmane group, I get gcc-self. In the Emacs
> groups, I don't. So this seems to work for me.
Lars, you don't get me. That's exactly what I complain about:
gmane.foo: foo=lala, bar=zot, gcc-self
gmane.emacs: foo=emacs, bar=zot, no gcc-self
While the bar-setting in the "gmane" clause also accounts for its value
in gmane.emacs, the gcc-self setting doesn't. This difference between
group parameters vs. group local variables is my concern.
Bye,
Tassilo
next prev parent reply other threads:[~2012-01-06 22:52 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
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 [this message]
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=8762goqwa5.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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).