Unnamed repository; edit this file 'description' to name the repository.
 help / color / mirror / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Rafi Khan <rafi@rafikhan.io>
Cc: asjo@koldfront.dk, info-gnus-english@gnu.org
Subject: Re: ‘Reply’ vs ‘followup’ (was: Test email)
Date: Fri, 10 Jul 2020 16:18:31 +0300
Message-ID: <o8ontsns.dag@gnui.org> (raw)
In-Reply-To: <87blkoz0n3.fsf@rafikhan.io> (Rafi Khan's message of "Thu, 09 Jul 2020 20:14:56 -0400")


[-- Attachment #1.1: Type: text/plain, Size: 2427 bytes --]

Rafi Khan <rafi@rafikhan.io> wrote:
> Alberto Luaces <aluaces@udc.es> writes:
> 1. I am using Gmail as the backend and received Dmitry Alexandrov's reply in my inbox, but for some reason your reply wasn't there.

He have not addressed you for some reason, cf. ‘To’ and (absent) ‘Cc’ headers in his mail.  While they are merely informational, they are usually true.


> 2. What is the difference between replying and forwarding in mailing lists?
>
> Should I be doing "F" or "R".

‘r’ and ‘R’¹ are above-mentioned ‘reply to sender only’ commands.  Indeed, docstring (<f1> k r) is unclear:

| (gnus-summary-reply &optional YANK WIDE VERY-WIDE)
|
| Start composing a mail reply to the current message.
| If prefix argument YANK is non-nil, the original article is yanked
| automatically.
| If WIDE, make a wide reply.
| If VERY-WIDE, make a very wide reply.

Manual entry (<f1> K r) is fine, though:

| ‘S r’
| ‘r’
|      Mail a reply to the author of the current article
|      (‘gnus-summary-reply’).

In other words, these are rarely needed commands.  The need to drop extra recipients from reply is rare, and even in these cases itʼs often easier just to purge ‘Cc’ line.


As for ‘f’ and ‘F’, they do _not_ stay for ‘forwarding’, but for ‘following-up’.  Contrary to what @asjo@koldfront.dk have said [0], they are _not_ for posting to [news]group only, but are supposed to be ‘do what I mean’ commands for replying: in Usenet — post to group (S n), in mail — reply to all (S w).

‘DWIM’ breaks, though, when you are reading mail gatewayed to Usenet or an isolated NNTP server such as Gmane.

Then you have to mark newsgroups that are really mailing lists first.  You can do that on one by one basis by setting ‘to-list’ parameter on them — Iʼve already explained how to do that [1], but really you want to mark all mail-to-news groups at once:

	(setq gnus-mailing-list-groups
	      (rx bol (opt "nntp" (1+ nonl) ":") (or "gmane."
	                                             "linux."
	                                             "mozilla.")))

Now you can use ‘f’ / ‘F’ instead of ‘S w’ / ‘S W’ just as intended.

[0] <875zaverel.fsf@tullinup.koldfront.dk>
[1] <eepkuhaa.dag@gnui.org>

-
¹ FWIW, I suggest you to use lower-case variants, followed by C-c C-y if you need quotation.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2020-07-10 13:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  5:15 Test email Rafi Khan
2020-07-09  7:31 ` Alberto Luaces
2020-07-10  0:14   ` Rafi Khan
2020-07-10  7:54     ` Adam Sjøgren via info-gnus-english
2020-07-10 23:47       ` Rafi Khan
2020-07-10 13:18     ` Dmitry Alexandrov [this message]
2020-07-10 14:14       ` ‘Reply’ vs ‘followup’ Alberto Luaces
2020-07-10 15:28       ` Adam Sjøgren via info-gnus-english
2020-07-10 23:51       ` Rafi Khan
2020-07-09  8:17 ` Test email Dmitry Alexandrov
     [not found]   ` <87imewz0ui.fsf@rafikhan.io>
2020-07-10  4:26     ` Get list address for Gmane group (was: Test email) Dmitry Alexandrov
2020-08-06 12:53 ` Test email 황병희
2020-08-07  4:01   ` Rafi Khan
2020-08-08  2:31     ` 황병희
2020-08-08 15:39       ` Emanuel Berg via info-gnus-english

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=o8ontsns.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.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

Unnamed repository; edit this file 'description' to name the repository.

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/info-gnus-english

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 info-gnus-english info-gnus-english/ http://inbox.vuxu.org/info-gnus-english \
		info-gnus-english@inbox.vuxu.org
	public-inbox-index info-gnus-english

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.emacs.gnus.user


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git