Does Mail-Followup-To generation?

Does Mail-Followup-To generation?

[Nevin Kapur]

Following the directions in the manual, I've set the group parameter
of my ding group as

 (to-address . "Ding <ding@gnus.org>")
 (to-list . "Ding <ding@gnus.org>")
 (subscribed . t)

I tried this with another list that I am subscribed to and the
Mail-Followup-To header was not generated.

(If this message has the correct Mail-Followup-To, then I'm an idiot,
otherwise consider this a plea for help.)

Any reason why the subscribed group parameter does not appear in `G c'?

-- 
Nevin

Re: Does Mail-Followup-To generation?

[Lars Magne Ingebrigtsen]

prj@po.cwru.edu (Paul Jarc) writes:

> WIBNI all docstrings had links to the corresponding info nodes
> automatically added, like how server parameters have a note appended
> to theirs?  The right info nodes could be found automatically via the
> index (I think); this would also make it easy to catch variables and
> functions that are missing index entries.

And Custom already makes all the user-visible variables group, so
you'd just need a mapping from group->info file.  (And then use the
variable index to find the thing you're looking for.)

Sounds like a nice addition to Custom.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Does Mail-Followup-To generation?

[Christoph Conrad]

    > WIBNI all docstrings had links to the corresponding info nodes
    > automatically added, like how server parameters have a note

OH YES!

Re: Does Mail-Followup-To generation?

[Christoph Conrad]

    > WIBNI all docstrings had links to the corresponding info nodes
    > automatically added, like how server parameters have a note

OH YES!

Re: Does Mail-Followup-To generation?

[Kai Großjohann]

prj@po.cwru.edu (Paul Jarc) writes:

> Either the Group Parameters node of the Gnus manual or the docstring
> for gnus-find-subscribed-addresses probably ought to link to the
> Mailing Lists node of the Message manual.  (I'd do it if I knew how.)

How about adding a link from the explanation of the "subscribed"
group parameter to gnus-find-subscribed-addresses and/or
message-subscribed-address-functions?  Then people who do "G c" on a
group will see what they need to do.

kai
-- 
Silence is foo!

Re: Does Mail-Followup-To generation?

[Kai Großjohann]

prj@po.cwru.edu (Paul Jarc) writes:

> Either the Group Parameters node of the Gnus manual or the docstring
> for gnus-find-subscribed-addresses probably ought to link to the
> Mailing Lists node of the Message manual.  (I'd do it if I knew how.)

How about adding a link from the explanation of the "subscribed"
group parameter to gnus-find-subscribed-addresses and/or
message-subscribed-address-functions?  Then people who do "G c" on a
group will see what they need to do.

kai
-- 
Silence is foo!

Re: Does Mail-Followup-To generation?

[Paul Jarc]

Nevin Kapur <nevin@jhu.edu> wrote:
> Following the directions in the manual, I've set the group parameter
> of my ding group as
>
>  (to-address . "Ding <ding@gnus.org>")
>  (to-list . "Ding <ding@gnus.org>")
>  (subscribed . t)

You also need this:
(setq message-subscribed-address-functions '(gnus-find-subscribed-addresses))

Either the Group Parameters node of the Gnus manual or the docstring
for gnus-find-subscribed-addresses probably ought to link to the
Mailing Lists node of the Message manual.  (I'd do it if I knew how.)

WIBNI all docstrings had links to the corresponding info nodes
automatically added, like how server parameters have a note appended
to theirs?  The right info nodes could be found automatically via the
index (I think); this would also make it easy to catch variables and
functions that are missing index entries.

> Any reason why the subscribed group parameter does not appear in `G c'?

Maybe because no one had thought of that yet, I guess.


paul

Re: Does Mail-Followup-To generation?

[Paul Jarc]

Nevin Kapur <nevin@jhu.edu> wrote:
> Following the directions in the manual, I've set the group parameter
> of my ding group as
>
>  (to-address . "Ding <ding@gnus.org>")
>  (to-list . "Ding <ding@gnus.org>")
>  (subscribed . t)

You also need this:
(setq message-subscribed-address-functions '(gnus-find-subscribed-addresses))

Either the Group Parameters node of the Gnus manual or the docstring
for gnus-find-subscribed-addresses probably ought to link to the
Mailing Lists node of the Message manual.  (I'd do it if I knew how.)

WIBNI all docstrings had links to the corresponding info nodes
automatically added, like how server parameters have a note appended
to theirs?  The right info nodes could be found automatically via the
index (I think); this would also make it easy to catch variables and
functions that are missing index entries.

> Any reason why the subscribed group parameter does not appear in `G c'?

Maybe because no one had thought of that yet, I guess.


paul

Re: Does Mail-Followup-To generation?

[Nevin Kapur]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Nevin Kapur <nevin@jhu.edu> writes:
>
>>  (to-address . "Ding <ding@gnus.org>")
>>  (to-list . "Ding <ding@gnus.org>")
>>  (subscribed . t)
>
> I think you should set either to-address, or to-list, but not both.
> I think if you set the subscribed parameter (but see also the
> variable message-subscribed-addresses), then you don't need to set
> to-list or to-address.

But the manual gives the impression that setting the subscribed
parameter to t will ensure that the to-list and to-address will be
considered in the generation of MFT.  My cursory examination of the
code indicates that this is not the case.

One needs to set message-subscribed-address-functions to '(gnus-

> (Hm, maybe to-list is useful for the `a' key.)

That's precisely why I have it in there.

-- 
Nevin

Re: Does Mail-Followup-To generation?

[Nevin Kapur]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Nevin Kapur <nevin@jhu.edu> writes:
>
>>  (to-address . "Ding <ding@gnus.org>")
>>  (to-list . "Ding <ding@gnus.org>")
>>  (subscribed . t)
>
> I think you should set either to-address, or to-list, but not both.
> I think if you set the subscribed parameter (but see also the
> variable message-subscribed-addresses), then you don't need to set
> to-list or to-address.

But the manual gives the impression that setting the subscribed
parameter to t will ensure that the to-list and to-address will be
considered in the generation of MFT.  My cursory examination of the
code indicates that this is not the case.

One needs to set message-subscribed-address-functions to '(gnus-

> (Hm, maybe to-list is useful for the `a' key.)

That's precisely why I have it in there.

-- 
Nevin

Re: Does Mail-Followup-To generation?

[Kai Großjohann]

Nevin Kapur <nevin@jhu.edu> writes:

>  (to-address . "Ding <ding@gnus.org>")
>  (to-list . "Ding <ding@gnus.org>")
>  (subscribed . t)

I think you should set either to-address, or to-list, but not both.
I think if you set the subscribed parameter (but see also the
variable message-subscribed-addresses), then you don't need to set
to-list or to-address.

(Hm, maybe to-list is useful for the `a' key.)

kai
-- 
Silence is foo!

Re: Does Mail-Followup-To generation?

[Kai Großjohann]

Nevin Kapur <nevin@jhu.edu> writes:

>  (to-address . "Ding <ding@gnus.org>")
>  (to-list . "Ding <ding@gnus.org>")
>  (subscribed . t)

I think you should set either to-address, or to-list, but not both.
I think if you set the subscribed parameter (but see also the
variable message-subscribed-addresses), then you don't need to set
to-list or to-address.

(Hm, maybe to-list is useful for the `a' key.)

kai
-- 
Silence is foo!

Does Mail-Followup-To generation?

[Nevin Kapur]

Following the directions in the manual, I've set the group parameter
of my ding group as

 (to-address . "Ding <ding@gnus.org>")
 (to-list . "Ding <ding@gnus.org>")
 (subscribed . t)

I tried this with another list that I am subscribed to and the
Mail-Followup-To header was not generated.

(If this message has the correct Mail-Followup-To, then I'm an idiot,
otherwise consider this a plea for help.)

Any reason why the subscribed group parameter does not appear in `G c'?

-- 
Nevin