From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Override MFT?
Date: Fri, 05 Apr 2002 14:57:32 -0500 [thread overview]
Message-ID: <m3it75535p.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafwuvmm59l.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 05 Apr 2002 19:20:22 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> Well, err. I tried all them keys, and I got messages to the
> addresses in Reply-to (which were two addresses of A), but B was not
> included. I had expected at least `S V' to include B...
Oh, so MFT included *only* you? Hm. Frobbing
message-use-mail-followup-to seems like the thing to do in that case.
I guess it would be nice to have a key that would set m-u-m-f-t to nil
or 'ask for just the next followup, and set it back to its original
value afterwards. Or something. I'm not sure how to do that, though.
Maybe gnus-summary-very-wide-reply* should always bind m-u-m-f-t, but
that seems intrusive.
Was this MFT automatically generated? If so, the software that did
that should be fixed.
paul
next prev parent reply other threads:[~2002-04-05 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 16:23 Kai Großjohann
2002-04-05 16:29 ` Paul Jarc
2002-04-05 17:20 ` Kai Großjohann
2002-04-05 19:57 ` Paul Jarc [this message]
2002-04-05 21:39 ` Kai Großjohann
2002-04-05 21:43 ` Paul Jarc
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=m3it75535p.fsf@multivac.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).