Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: SOLVED (was: ignore bcc when followup)
Date: Wed, 22 Feb 2017 19:10:27 +0000	[thread overview]
Message-ID: <87o9xu6nz0.fsf@mat.ucm.es> (raw)
In-Reply-To: <87y3wy8hd0.fsf@mat.ucm.es>

>>> "Uwe" == Uwe Brauer <oub@mat.ucm.es> writes:

   > Hi
   > as longer as I think about it: At least optionally the BCC field should
   > be ignored in the reply even when calling followup.

   > I look into the code, looks difficult to modify. Any ideas?

   > Regards

   > Uwe Brauer 


The following code does this

(add-hook 'gnus-message-setup-hook 'my-check-bcc)
(defun my-check-bcc ()
  "Try to avoid painful situations when using followup, and there is a Bcc field."
  (interactive)
  (cond ((and gnus-article-reply
              (message-with-reply-buffer
                (re-search-forward
                 "^Bcc:\\|BCC:\\|bcc:"
                 nil t)))
         (condition-case nil
             (progn
               (message-remove-header "cc")
               (message-goto-body)
               (message "There is a BCC field, we have deleted it!!!"))
           (error
            (progn
                (message "Followup??")))))))




  reply	other threads:[~2017-02-22 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 13:50 ignore bcc when followup Uwe Brauer
2017-02-22 19:10 ` Uwe Brauer [this message]
2017-02-23  7:46   ` SOLVED David Engster
2017-02-23  8:41     ` Bcc Adam Sjøgren
2017-02-23 18:21       ` Bcc David Engster
2017-02-22 19:54 ` ignore bcc when followup Adam Sjøgren
2017-02-22 21:34   ` Uwe Brauer
2017-02-22 22:03     ` Adam Sjøgren
2017-02-22 22:23     ` Adam Sjøgren
2017-02-23 10:24       ` Uwe Brauer
2017-02-23 12:49         ` Adam Sjøgren
2017-02-23 14:10           ` Uwe Brauer
2017-02-23 14:54             ` Adam Sjøgren
2017-02-23 15:33               ` 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=87o9xu6nz0.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).