Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: No Followup-To header defaults
Date: Thu, 25 Aug 2005 07:47:38 +0900	[thread overview]
Message-ID: <b4mpss3q7ed.fsf@jpl.org> (raw)
In-Reply-To: <877jebi6n2.fsf@teufel.hartford-hwp.com>

>>>>> In <877jebi6n2.fsf@teufel.hartford-hwp.com> Haines Brown wrote:

> When I moved to a set up on a new machine, my gnus (still emacs
> version 21.4.2) acts differently. I should add that I moved all
> statements related to gnus from my ~/.emacs file to a ~/.gnus file,
> but none seem relevant to the issue.

> When I reply to a message that was originally sent to multiple groups,
> I get: 

>   Followups to (default: no Followup-To header)

> When I Enter, I get:

>   Really use these possible unknown groups: ... (y or n)?

I think the reason that Gnus issues such a message is that the
groups the original article was posted to include groups which
you don't subscribe to.

> When I say "y", the message does go out to the groups. How do I
> recover a default display of the list of groups?

So, it seems to solve by subscribing to all those groups.
Another solution is to set the `gnus-read-active-file' variable
to t, though it might slow down Gnus.


      parent reply	other threads:[~2005-08-24 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 17:31 Haines Brown
2005-08-24 18:00 ` Bernard Adrian
2005-08-24 22:52   ` Haines Brown
2005-08-25 10:15   ` Reiner Steib
2005-08-25 15:25     ` Bernard Adrian
2005-08-25 17:47     ` Haines Brown
2005-08-28 17:28       ` Reiner Steib
2005-08-29  1:10         ` Haines Brown
2005-09-03 16:16           ` Reiner Steib
2005-08-24 22:47 ` Katsumi Yamaoka [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=b4mpss3q7ed.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    /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).