Gnus development mailing list
 help / color / mirror / Atom feed
* gnus-parameters limitations
@ 2004-10-31 13:00 Jochen Küpper
  2004-10-31 20:31 ` Reiner Steib
  0 siblings, 1 reply; 3+ messages in thread
From: Jochen Küpper @ 2004-10-31 13:00 UTC (permalink / raw)


I am wondering about some limitations of gnus-parameters, using GNU
Emacs 21.3.1 and No Gnus v0.3.


The manual states (correctly) that some settings cannot be performed
through the gnus-parameters variable:
,----[ (info "(gnus)Group Parameters") ]
|    Group parameters can be set via the `gnus-parameters' variable too.
| But some variables, such as `visible', have no effect.  For example:
`----
Why is that?

I am sharing my .emacs and .gnus files between computers (using cvs),
so it would be great to put everything into these files. Having to use
Group Parameters (stored in .newsrc.eld) is fairly uncomfortable. But
also generally it would be nice to have everything stored in one
place.

What would be necessary to improve on that?



Apparently the parsing of gnus-parameters is performed so that the
first matching entry is used. Wouldn't it be nice to allow for
hierarchical settings as with posting styles, where all matching
entries are used and later settings overwrite earlier ones?

Assume the following setting
,----
|      (setq gnus-parameters
|            '(("mail\\..*"
|               (gnus-show-threads nil)
|               (gnus-use-scoring nil)
|               (gcc-self . t)
|               (display . all))
|              ("mail\\.some\\.group"
|               (gnus-use-scoring  t)
|               (to-group . "\\1"))
`----
I would expect to have the following apply to mail.some.group:
,----
|               (gnus-show-threads nil)
|               (gcc-self . t)
|               (display . all))
|               (gnus-use-scoring  t)
|               (to-group . "\\1"))
`----


Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        Sex, drugs and rock-n-roll




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: gnus-parameters limitations
  2004-10-31 13:00 gnus-parameters limitations Jochen Küpper
@ 2004-10-31 20:31 ` Reiner Steib
       [not found]   ` <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Reiner Steib @ 2004-10-31 20:31 UTC (permalink / raw)


On Sun, Oct 31 2004, Jochen Küpper wrote:

> Apparently the parsing of gnus-parameters is performed so that the
> first matching entry is used. Wouldn't it be nice to allow for
> hierarchical settings as with posting styles, where all matching
> entries are used and later settings overwrite earlier ones?
>
> Assume the following setting
> ,----
> |      (setq gnus-parameters
> |            '(("mail\\..*"
> |               (gnus-show-threads nil)
> |               (gnus-use-scoring nil)
> |               (gcc-self . t)
> |               (display . all))
> |              ("mail\\.some\\.group"
> |               (gnus-use-scoring  t)
> |               (to-group . "\\1"))
> `----
> I would expect to have the following apply to mail.some.group:
> ,----
> |               (gnus-show-threads nil)
> |               (gcc-self . t)
> |               (display . all))
> |               (gnus-use-scoring  t)
> |               (to-group . "\\1"))
> `----

Are you sure that it doesn't work?  When I test it with...

(setq
 gnus-parameters
 '(("gnus"
    (gnus-use-scoring nil)
    (rs-gnus-temp-1 1))
   ("gmane.emacs.gnus.general"
    (gnus-use-scoring t)
    (rs-gnus-temp-1 2)
    (rs-gnus-temp-2 2))))

... and enter gmane.emacs.gnus.general, I get:

  gnus-use-scoring t
  rs-gnus-temp-1 2
  rs-gnus-temp-2 2
  rs-gnus-temp-3 3

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: gnus-parameters limitations
       [not found]   ` <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
@ 2005-01-03 17:44     ` Jochen Küpper
  0 siblings, 0 replies; 3+ messages in thread
From: Jochen Küpper @ 2005-01-03 17:44 UTC (permalink / raw)


Sorry for the late response, somehow got out of sight. The followup
might be useful for someone looking through the archives.

Reiner Steib <reinersteib+gmane-ZTO5kqT2PaM@public.gmane.org> writes:

> On Sun, Oct 31 2004, Jochen Küpper wrote:
>
>> Apparently the parsing of gnus-parameters is performed so that the
>> first matching entry is used. Wouldn't it be nice to allow for
>> hierarchical settings as with posting styles, where all matching
>> entries are used and later settings overwrite earlier ones?

[...]

> Are you sure that it doesn't work?

[...Shows working example...]

Ok, it just works!

My problem was that I put postings-styles into gnus-parameters
,----
| (setq gnus-parameters '(("some/group$"
|                          (posting-style
|                           (eval (jk/ispell-dutch))))
|                         ("some"
|                          (posting-style
|                           (body "Hoi,\n\n\nGroeten,\nJochen")))))
`----
and expected "hierarchical evaluation" of these... I can see the logic
behind this *not* working and reverted to the use of
gnus-posting-styles, so I get what I want.

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-01-03 17:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-10-31 13:00 gnus-parameters limitations Jochen Küpper
2004-10-31 20:31 ` Reiner Steib
     [not found]   ` <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
2005-01-03 17:44     ` Jochen Küpper

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).