Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Haines Brown <brownh@teufel.hartford-hwp.com>
Subject: Re: No Followup-To header defaults
Date: Mon, 29 Aug 2005 01:10:52 GMT	[thread overview]
Message-ID: <871x4d5yze.fsf@teufel.hartford-hwp.com> (raw)
In-Reply-To: <v9r7ceynqj.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+from-uce@imap.cc> writes:

> On Thu, Aug 25 2005, Haines Brown wrote:
>
>> I've cut out everything in ~/.gnus except for
>>
>>   (setq gnus-select-method '(nntp "..."))
>>
>> and the problem persists. 
>
> Which problem?  The prompt "Really post to these unknown groups: x,
> y?"?  

Yes.

> Gnus doesn't know that groups x and y exist.  Maybe in your previous
> setup, Gnus knew about the groups x and y (IIRC unsubscrkilledibed
> groups are also considered here).

I had assumed that when I followed up to a message, the header of my
reply would read the Newsgroups: line of the message to which I am
responding. Your answer implies that this not so, and the behavior
about which I'm complaining is normal. 

You seem to imply that in my previous setup gnus didn't read the
Newsgroups: line, but would somehow otherwise know of these groups,
even if I had never subscribed to them or killed them. 

For example, I'm involved in a discussion on a newsgroup, but the OP
had distributed his message to several groups, including
uk.politics.misc. When I follow up to up his messages, the
uk.politics.misc group in my old setup would appear automatically in
the "Newsgroups:" line of my outgoing header.

Since you may be suggesting that my old gnus somehow knew of
uk.politis.misc, I searched in ~/News and the ~/.newsrc* files, but
didn't find it.

In my old setup, ~/News contained a set of files corresponding to the
groups to which I subscribed. For example, linux.debian.user.SCORE,
which holds the sole line "(("references"))". My new set up has no
such files. 

In the original setup, In the file for the newsgroup to which I reply
to message with multiple addresses, the entry has sets of lines like
these: 

  (("references"
    ("<871x5lp9ve.fsf@teufel.hartford-hwp.com>[ ]*$" nil 732153 r)
    ("<871x5lp9ve.fsf@teufel.hartford-hwp.com>" nil 732153 s)
  ...


-- 
 
       Haines Brown
       KB1GRM       


  reply	other threads:[~2005-08-29  1:10 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 [this message]
2005-09-03 16:16           ` Reiner Steib
2005-08-24 22:47 ` Katsumi Yamaoka

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=871x4d5yze.fsf@teufel.hartford-hwp.com \
    --to=brownh@teufel.hartford-hwp.com \
    /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).