Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Sat, 14 Apr 2018 00:42:36 +0200	[thread overview]
Message-ID: <87vacuaftv.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87muy691ru.fsf@mat.ucm.es>

Uwe writes:

>>>> "Lars" == Lars Ingebrigtsen <larsi@gnus.org> writes:

>> But the question is: If you're not listed in To/Cc in a mail, and
>> you do a wide reply, should Gnus warn you about what you're doing?
>> I don't think so: It's a very common situation, especially with
>> mailing lists.
>
> On a second thought if  in such a situation I will use
>
> gnus-summary-reply-with-original
>
> I will be asked
>
> Really reply by mail to article author? (y or n) y

That's something you've configured yourself, right?

I know I have an advice adding exactly that.

> Couldn't we have (with a setting of a variable say) the same for followup?
>
> Really followup by mail to article authors (including  the CC) ? (y or n) y

So regardless of whether you reply or follow up, you want to be asked if
that's really what you want to do?

I think your fingers will quickly learn to press 'y' automatically.


  Best regards,

    Adam

-- 
 "Ja, det lyder jo som radioen vender på hovedet!"            Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2018-04-13 22:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 12:06 Uwe Brauer
2018-04-11 19:52 ` Lars Ingebrigtsen
2018-04-11 21:25   ` Dan Christensen
2018-04-13 18:44   ` Uwe Brauer
2018-04-13 20:29   ` Uwe Brauer
2018-04-13 20:38     ` Lars Ingebrigtsen
2018-04-13 20:59       ` Uwe Brauer
2018-04-13 21:15         ` Lars Ingebrigtsen
2018-04-13 22:23           ` Uwe Brauer
2018-04-13 22:28             ` Lars Ingebrigtsen
2018-04-14  7:15               ` Uwe Brauer
2018-04-14  9:54                 ` Adam Sjøgren
2018-04-14 10:12                   ` Uwe Brauer
2018-04-14 10:38                     ` Adam Sjøgren
2018-04-14 17:05               ` Uwe Brauer
2018-04-14 17:58                 ` Lars Ingebrigtsen
2018-04-19 11:58                   ` [Partial solution: how to warn about a possible BCC field] (was: warn about a BCC field) Uwe Brauer
2018-04-13 22:31           ` warn about a BCC field Uwe Brauer
2018-04-13 22:42             ` Adam Sjøgren [this message]
2018-04-14  7:09               ` Uwe Brauer

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=87vacuaftv.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.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).