Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Override MFT?
Date: Fri, 05 Apr 2002 23:39:27 +0200	[thread overview]
Message-ID: <vafvgb57rlc.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3it75535p.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Fri, 05 Apr 2002 14:57:32 -0500")

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

> 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?

Yep.

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

I don't feel it's intrusive.  But maybe that's because I don't know
what is the difference between wide reply and very wide reply.

> Was this MFT automatically generated?  If so, the software that did
> that should be fixed.

A, B and me are all using Gnus.  But how that MFT came about, I don't
know.  Hm.

kai
-- 
Silence is foo!



  reply	other threads:[~2002-04-05 21:39 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
2002-04-05 21:39       ` Kai Großjohann [this message]
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=vafvgb57rlc.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).