Gnus development mailing list
 help / color / mirror / Atom feed
From: Christopher Schmidt <christopher@ch.ristopher.com>
To: ding@gnus.org
Cc: info-gnus-english@gnu.org
Subject: Control body encoding of Gcc copies (was: Don't encrypt Gcc'ed messages)
Date: Tue, 13 Mar 2012 19:01:14 +0100	[thread overview]
Message-ID: <20120313180130.D4FA51FE11@saturn.ch.ristopher.com> (raw)
In-Reply-To: <20120311222924.9C0AC1FDFB@saturn.ch.ristopher.com> (Christopher Schmidt's message of "Sun, 11 Mar 2012 23:29:11 +0100")

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Christopher Schmidt <christopher@ch.ristopher.com> writes:

> is there any way to get Gnus to ignore mml encrypt tags when storing
> sent mail in a Gcc group?  (I looked in gnus-inews-do-gcc but it looks
> like there is no customisation point or handy hook that I could use to
> achieve that.)

Here is a patch for Gnus master that adds more flexibility to
gnus-inews-do-gcc.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-msg.diff --]
[-- Type: text/x-diff, Size: 1294 bytes --]

diff --git a/lisp/gnus-msg.el b/lisp/gnus-msg.el
index 9411f46..d158600 100644
--- a/lisp/gnus-msg.el
+++ b/lisp/gnus-msg.el
@@ -313,6 +313,20 @@ If nil, the address field will always be empty after invoking
   :group 'gnus-message
   :type 'boolean)
 
+(defcustom gnus-gcc-pre-body-encode-hook nil
+  "A hook called before encoding the body of the Gcc copy of a message.
+Changes made to the message will only affect the Gcc copy, but
+not the original message."
+  :group 'gnus-message
+  :type 'hook)
+
+(defcustom gnus-gcc-post-body-encode-hook nil
+    "A hook called after encoding the body of the Gcc copy of a message.
+Changes made to the message will only affect the Gcc copy, but
+not the original message."
+  :group 'gnus-message
+  :type 'hook)
+
 (autoload 'gnus-message-citation-mode "gnus-cite" nil t)
 
 ;;; Internal variables.
@@ -1643,7 +1657,9 @@ this is a reply."
 	      (nnheader-set-temp-buffer " *acc*")
 	      (setq message-options (with-current-buffer cur message-options))
 	      (insert-buffer-substring cur)
+	      (run-hooks 'gnus-gcc-pre-body-encode-hook)
 	      (message-encode-message-body)
+	      (run-hooks 'gnus-gcc-post-body-encode-hook)
 	      (save-restriction
 		(message-narrow-to-headers)
 		(let* ((mail-parse-charset message-default-charset)

[-- Attachment #3: Type: text/plain, Size: 38 bytes --]


Is this one OK?

        Christopher

[-- Attachment #4: 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

       reply	other threads:[~2012-03-13 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120311222924.9C0AC1FDFB@saturn.ch.ristopher.com>
2012-03-13 18:01 ` Christopher Schmidt [this message]
2012-03-14 14:34   ` Control body encoding of Gcc copies Lars Magne Ingebrigtsen
2012-03-14 17:31     ` Christopher Schmidt
2012-03-15  1:32       ` Lars Magne Ingebrigtsen

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=20120313180130.D4FA51FE11@saturn.ch.ristopher.com \
    --to=christopher@ch.ristopher.com \
    --cc=ding@gnus.org \
    --cc=info-gnus-english@gnu.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).