Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: Changes in Group/customize
Date: 02 Apr 1998 17:53:27 -0500	[thread overview]
Message-ID: <glmemzfbztk.fsf@caffeine.mitre.org> (raw)
In-Reply-To: Harry Putnam's message of "02 Apr 1998 09:00:18 -0800"

Harry Putnam <reader@newsguy.com> writes:

> Have there been changes in the functions of 'R' and 'F' in mail groups,
> in recent releases? 

Not that I know of.

> Using the Group Customize to arrange what comes up in an 'a'
> initiated message,

You haven't mentioned any of the actual parameters that you modified.
I will assume that you mean 'to-address'.

> 'r' initiated message is not working for all replys in my recently
> established 'ding' mail group.

'r' should always address mail to the author of the post, not to a
mailing list.  It should be unaffected by 'to-address'.

> Doing a reply 'R' turns up the posters address instead of the groups
> address, even though I have set the first two items in customize to the
> address of the group.

This is as it should be.  

> Only way I can get the group address into the posting is with 'F' and I
> only like to use 'wide-reply' very selectively.

Why don't you?  Is there a reason?

If you set the 'to-address' parameter to the mailing list's address,
'f' or 'F' will address your followup to the list only, and not to the
author unless you add it explicitly or with 'C-c C-t'.

> I have set the 'broken reply-to both ways with no change in behavior
> after a restart.

I think that you expect 'broken-reply-to' to behave in the opposite
manner that it does.  Or at least a very different way than it does.

Some mailing lists are set up so that all mail sent through them ends
up with a Reply-To header pointing to the list.  This is broken
behavior.  Setting 'broken-reply-to' will instruct Gnus to ignore the
Reply-To header so that replies go to the author of the message
instead of the list.

> Going back to 5.6.2 shows the same behavior, checking further here I see
> this is true in all my mail groups.

Yes.  There is no reason why this behavior would be changed in the
manner that you seem to expect.

The commands run when you press the 'r' and 'R' keys should always
send mail to only the author of the message.  Similarly, the 'f' and
'F' keys should send a message to all of the people that received the
original to which you are replying.  This is how is has always been.

> I don't believe this was always the way it worked so either I have
> mucked up something recently or have been sending alot of wide replies
> unknowingly.  Of course there is a the third possibility that I have
> been too dead headed to notice it was always like that.

I think that you are just very confused. (choice #3)

-- 
Justin Sheehy

In a cloud bones of steel.
  




  reply	other threads:[~1998-04-02 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-02 17:00 Harry Putnam
1998-04-02 22:53 ` Justin Sheehy [this message]
1998-04-03  0:18   ` Harry Putnam
1998-04-03  3:54     ` Aaron M. Ucko
1998-04-03 16:47     ` Justin Sheehy

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=glmemzfbztk.fsf@caffeine.mitre.org \
    --to=justin@linus.mitre.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).