Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Mail-{Followup,Reply}-To
Date: 03 Nov 2000 12:12:50 -0500	[thread overview]
Message-ID: <m3vgu5q8rb.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Toby Speight's message of "03 Nov 2000 15:42:40 +0000"

Toby Speight <streapadair@gmx.net> writes:
> Paul> message-use-mail-followup-to
> Paul>   nil  always ignore MFT
> Paul>   use  always use MFT
> Paul>   ask  always ask
> Paul>   t    use MFT if it matches To+Cc (not To+Cc+From), otherwise ask
> Paul> Sound good?  I think the default should be t.
> 
> I think that t should mean "always use" - that's the intuitive meaning.

I was just trying to be parallel with message-use-followup-to, which
uses t (actually, any non-nil value other than the ones with other
meanings explicitly assigned to them) to mean 'conditionally ask'.  I
haven't written this code yet, but it'd probably also not explicitly
compare to t - any unrecognized value would be interpreted this way.
So the real question is: what value do we *document* as producing this
behavior?  In case more values are given meanings in the future,
perhaps with one of the new interpretations grabbing unrecognized
values, what value should we guarantee will retain this meaning?  t is
probably not a good choice for that.  I think I'll go with
ask-unless-trivial.


paul



      reply	other threads:[~2000-11-03 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-23 20:54 Mail-{Followup,Reply}-To Paul Jarc
2000-10-24  9:52 ` Mail-{Followup,Reply}-To Kai Großjohann
2000-10-24 12:45   ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-24 13:52     ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-24 17:42       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-24 22:48     ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-25  9:16       ` Mail-{Followup,Reply}-To Kai Großjohann
2000-10-25 12:27       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-27 15:30   ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-27 16:00     ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-28 10:06       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-11-03 15:42       ` Mail-{Followup,Reply}-To Toby Speight
2000-11-03 17:12         ` Paul Jarc [this message]

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=m3vgu5q8rb.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).