From: Christopher Schmidt <christopher@ch.ristopher.com>
To: ding@gnus.org
Subject: Re: Changing GPG encryption for GCC copy
Date: Wed, 7 Nov 2012 10:44:28 +0000 (GMT) [thread overview]
Message-ID: <87sj8lu1yp@ch.ristopher.com> (raw)
In-Reply-To: <87ip9hyegx.fsf@rss01.mhs.man.ac.uk> (Matt Ford's message of "Wed, 07 Nov 2012 09:00:46 +0000")
Matt Ford <matt@dancingfrog.co.uk> writes:
> Inspired by a recent thread I wondered if there was an elegant way of
> switching the encryption key used when saving a copy of an encrypted
> message via GCC.
Check gnus-gcc-pre-body-encode-hook and gnus-gcc-post-body-encode-hook.
I have this in my gnus-init.el:
(ah gnus-gcc-pre-body-encode-hook
(goto-char (message-goto-body))
(while (re-search-forward "^<#\\(secure .*mode=\\(sign\\)?encrypt.*>\\)$"
nil
t)
(replace-match "<|rms\\1")))
(ah gnus-gcc-post-body-encode-hook
(goto-char (message-goto-body))
(while (re-search-forward "^<|rms\\(.*\\)$" nil t)
(replace-match "<#\\1")))
Christopher
prev parent reply other threads:[~2012-11-07 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 9:00 Matt Ford
2012-11-07 9:50 ` Adam Sjøgren
2012-11-07 10:54 ` Matt Ford
2012-11-07 10:44 ` Christopher Schmidt [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=87sj8lu1yp@ch.ristopher.com \
--to=christopher@ch.ristopher.com \
--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).