Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Problem with gnus-parameters
Date: Sat, 07 Jan 2012 00:37:13 +0100	[thread overview]
Message-ID: <871urcqu6u.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m3r4zc77be.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 07 Jan 2012 00:13:57 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Please type slower; I'm not getting what you're saying.  :-)

We can play that game for hours.  Oh, I've overlooked the (gcc-self) in
the "emacs" clause.  Anyway, the following setting will result in the
same effects.  Look, I've even lined it up for you! :-)

 '(("gmane"      (foo "lala") (bar "zot") (gcc-self . t))
   ("emacs"      (foo "emacs")                          ))

>    gmane.foo:   foo=lala,    bar=zot,    gcc-self
>    gmane.emacs: foo=emacs,   bar=zot,    no gcc-self

Now, let's inspect the effects:

  - the (bar "zot") entry is only set in the "gmane" clause, yet we have
    its value also in gmane.emacs

  - the "lala" foo value gets overridden in the gmane.emacs group,
    because that defines its own foo setting

  - the gcc-self (which is a group parameter and not a group local
    variable like foo and bar) is *not* propagated to gmane.emacs, as
    one would expect because of bar

To me, that inconsistency between group local variables and group
parameters is far from obvious.  I'd prefer, if in gmane.emacs gcc-self
was active, too, i.e., I'd expect these effects:

     gmane.foo:   foo=lala,    bar=zot,    gcc-self
     gmane.emacs: foo=emacs,   bar=zot,    gcc-self

Then, we had full consistency in how group local variables and group
parameters defined in `gnus-parameters' work, and the behavior would
also be consistent with how `gnus-posting-styles' are applied.

Got it, now?  I really can't be more precise.

That said, although it's inconsistent, I can easily live with it.  If
you decide the current way is how the great spaghetti monster wants it
to be, that's fine.  But it needs a precise documentation then.

Bye,
Tassilo



  reply	other threads:[~2012-01-06 23:37 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
2012-01-06 23:13                       ` Lars Magne Ingebrigtsen
2012-01-06 23:37                         ` Tassilo Horn [this message]
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=871urcqu6u.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.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).