Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Rafi Khan <rafi@rafikhan.io>
Cc: ding@gnus.org
Subject: Re: on a buffer performance test on GNU EMACS 28
Date: Wed, 19 Aug 2020 20:02:03 -0700	[thread overview]
Message-ID: <87y2ma9g0k.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86364i2gzl.fsf@rafikhan.io> (Rafi Khan's message of "Wed, 19 Aug 2020 22:22:54 -0400")


On 08/19/20 22:22 PM, Rafi Khan wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> To my embarrassment, I don't know how it works, either. I use Gnus as a
>> newsreader, and access these emacs.* groups via nntp. But sometimes I
>> followup using "F", and sometimes I reply with "S W". I'm often not even
>> aware of which I've used. In the latter case, I must be sending email to
>> ding@gnus.org, but it all ends up looking the same to me.
>
> I never really understood the difference between "F" and "S W"... could
> you explain?

Gnus can send messages via two methods: "news" (which is done directly
by an nntp server), and "mail" (which requires separate SMTP
configuration). In the Summary buffer, you've got multiple
semi-redundant commands which do the same thing for either news (called
a "followup") or mail (called a "reply"). Because followup is only ever
sent to a newsgroup (not multiple recipients), it only has two flavors
-- with or without quotation -- on "f" and "F". A mail reply can be
"plain", "wide" or "very wide", and also with or without quotation,
leading to a total of (*counts on fingers*) six bound commands. The full
complement is on the "S" prefix key, but "r" and "R" also do the most
obvious.

Where I'm less certain is what happens when you mail reply in an nntp
newsgroup. In the case of gnus.general, the address "ding@gnus.org" is
always in the cc, so if you do any of the (very) wide reply options,
Gnus apparently knows that your message will also go to the group, and
it lets you send the mail reply (as opposed to the news followup). If
you try a non-wide mail reply (which would not go to the group) it
assumes you're making a dumb mistake and asks for confirmation.

I don't know how much of this is standard nntp stuff, how much
particular to Gnus the newsreader, and how much particular to
gnus.general the newsgroup.

Hope that didn't make things worse!

Eric


  reply	other threads:[~2020-08-20  3:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16  2:07 Wayne Harris
2020-08-16 17:23 ` Eric Abrahamsen
2020-08-17  3:57   ` Wayne Harris
2020-08-19  2:02     ` Wayne Harris
2020-08-19 16:27       ` Eric Abrahamsen
2020-08-20  2:22         ` Rafi Khan
2020-08-20  3:02           ` Eric Abrahamsen [this message]
2020-08-20  3:36             ` Wayne Harris
2020-08-20 14:14               ` Wayne Harris
2020-08-20 18:02                 ` Eric Abrahamsen
2020-08-20 21:55                   ` Jason Tibbitts
2020-08-20 22:44                     ` Eric Abrahamsen
2020-08-21  3:52                       ` Wayne Harris
2020-08-21  2:01                     ` 황병희
2020-08-21  0:12                   ` Wayne Harris
2020-08-20  2:57         ` Wayne Harris

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=87y2ma9g0k.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=rafi@rafikhan.io \
    /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).