Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Sat, 14 Apr 2018 09:09:41 +0200	[thread overview]
Message-ID: <87in8ul0wa.fsf@mat.ucm.es> (raw)
In-Reply-To: <87vacuaftv.fsf@tullinup.koldfront.dk>


   > Uwe writes:


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

   > I know I have an advice adding exactly that.


   > 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.

Sigh, might be true (for example I have an advice asking me to encrypt or
decrypt. Since most recipients don't use encryption I say n, even
sometimes to people I do want to encrypt).......

   >   Best regards,

   >     Adam




      reply	other threads:[~2018-04-14  7:09 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
2018-04-14  7:09               ` Uwe Brauer [this message]

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=87in8ul0wa.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).