From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: new Mail-Followup-To patch...please take a look...
Date: Wed, 24 Oct 2001 19:38:04 +0200 [thread overview]
Message-ID: <rjzo6hvszn.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <m3pu7deym5.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 24 Oct 2001 13:28:12 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Per Abrahamsen <abraham@dina.kvl.dk> wrote:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>>> +(defvar message-subscribed-address-functions '(ignore)
>>
>> Why put "ignore" in the list?
>
> So Gnus can differentiate between the default value and the user's
> explicit nil setting. Gnus automatically adds its function only if
> the user hasn't provided a setting.
Ah, I missed that. That makes sense.
> I think it's defvar because someone thought defcustom couldn't handle
> a list of functions, or the '(ignore) default. I have next to no
> knowledge of customize, so I don't know if this is true.
defcustom can handle anything, you don't even need supply a ":type"
argument (it defaults to "sexp"). Og a :group argument, but not doing
that is kind of rude.
It does require a value and a doc string, but if these are provided
defcustom can always where defvar can be used.
>> Why would we ever want MFT in the messsage buffer? To test it?
>>
>> I thought it was supposed to be inserted automatically when the user
>> send the message.
>
> It's inserted automatically only if the user didn't supply one
> manually. It can be used manually just like Followup-To, to direct
> the thread toward a subset of the lists, etc.
That makes sense too.
next prev parent reply other threads:[~2001-10-24 17:38 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 15:24 Josh Huber
2001-10-23 15:42 ` Josh Huber
2001-10-23 16:32 ` Paul Jarc
2001-10-23 16:54 ` Josh Huber
2001-10-23 17:45 ` Paul Jarc
2001-10-23 18:54 ` Matt Armstrong
2001-10-23 19:53 ` Paul Jarc
2001-10-24 0:34 ` Josh Huber
2001-10-24 11:35 ` Per Abrahamsen
2001-10-24 12:48 ` Josh Huber
2001-10-24 16:31 ` Paul Jarc
2001-10-24 17:08 ` Per Abrahamsen
2001-10-24 17:18 ` Paul Jarc
2001-10-26 6:24 ` Kai Großjohann
2001-10-27 23:23 ` Florian Weimer
2001-10-23 16:56 ` Josh Huber
2001-10-23 17:32 ` Per Abrahamsen
2001-10-23 23:53 ` Josh Huber
2001-10-23 22:40 ` Davide G. M. Salvetti
2001-10-24 1:40 ` Paul Jarc
2001-10-24 12:45 ` Davide G. M. Salvetti
2001-10-24 13:44 ` Samuel Padgett
2001-10-24 15:23 ` Paul Jarc
2001-10-24 15:42 ` Per Abrahamsen
2001-10-24 15:51 ` Samuel Padgett
2001-10-26 6:28 ` Kai Großjohann
2001-10-27 1:19 ` Barry Fishman
2001-10-29 14:49 ` Kai Großjohann
2001-10-27 22:27 ` Florian Weimer
2001-10-24 1:59 ` Josh Huber
2001-10-24 15:02 ` Per Abrahamsen
2001-10-24 16:48 ` Paul Jarc
2001-10-24 17:13 ` Per Abrahamsen
2001-10-25 1:52 ` Josh Huber
2001-10-24 16:13 ` Paul Jarc
2001-10-24 17:19 ` Per Abrahamsen
2001-10-24 17:28 ` Paul Jarc
2001-10-24 17:38 ` Per Abrahamsen [this message]
2001-10-25 1:45 ` Josh Huber
2001-10-25 18:48 ` Josh Huber
2001-10-29 21:58 ` Matt Armstrong
2001-10-29 22:19 ` Josh Huber
2001-10-29 22:31 ` Paul Jarc
2001-10-30 2:47 ` Josh Huber
2001-10-30 3:11 ` Paul Jarc
2001-10-30 3:49 ` Matt Armstrong
2001-10-30 12:55 ` Per Abrahamsen
2001-10-30 15:31 ` Josh Huber
2001-10-31 13:44 ` ShengHuo ZHU
2001-10-31 17:28 ` Matt Armstrong
2001-10-31 17:51 ` Josh Huber
2001-10-31 18:22 ` ShengHuo ZHU
2001-10-26 6:34 ` Kai Großjohann
2001-10-26 9:07 ` Per Abrahamsen
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=rjzo6hvszn.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).