From: "Matthew Lear" <matt@bubblegen.co.uk>
To: "Mark Walters" <markwalters1009@gmail.com>
Cc: "Matthew Lear" <matt@bubblegen.co.uk>,
"Daniel Kahn Gillmor" <dkg@fifthhorseman.net>,
"notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: notmuch-emacs: forward messages inline
Date: Tue, 10 Nov 2015 15:06:01 -0000 [thread overview]
Message-ID: <5b7cdc1b10597d9f667939cf4f0b45d4.squirrel@webmail.plus.net> (raw)
In-Reply-To: <871tbz8bil.fsf@qmul.ac.uk>
>
> Hi
>
> Does adding something like the following to your .emacs file do what you
> want?
>
>
> (defun my-forward (prefix)
> (interactive "P")
> (let ((message-forward-as-mime nil)
> (message-forward-ignored-headers ".*"))
> (notmuch-show-forward-message prefix)))
>
> (define-key notmuch-show-mode-map "F" 'my-forward)
>
> Then "F" should forward the message as a plain message rather than
> rfc822, and there should not be any spurious headers.
Hi Mark. Yes, thanks. For plain text emails this is perfect in that it
gives me what I want (and I can customise the start/end of forwarded
message separators). For messages with text and html versions of the body
it is less ideal because it generates an email with three attachments -
one with the plain text of the message body, one with the html of the
message body and one that just contains the 'end of forwarded message'
separator. I'd prefer that the plain text message body was included inline
and that the html portion was the only attachment in this case. Is this
possible?
-- Matt
prev parent reply other threads:[~2015-11-10 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 19:51 notmuch-emacs: forward messages inline Matthew Lear
2015-11-05 21:42 ` Daniel Kahn Gillmor
2015-11-06 6:23 ` Suvayu Ali
2015-11-06 19:23 ` Matthew Lear
2015-11-06 23:48 ` Daniel Kahn Gillmor
2015-11-09 14:58 ` Mark Walters
2015-11-10 15:06 ` Matthew Lear [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b7cdc1b10597d9f667939cf4f0b45d4.squirrel@webmail.plus.net \
--to=matt@bubblegen.co.uk \
--cc=dkg@fifthhorseman.net \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).