From: Mark Walters <markwalters1009@gmail.com>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: Exporting mime email
Date: Fri, 06 Jan 2012 10:27:16 +0000 [thread overview]
Message-ID: <87k455p1mj.fsf@qmul.ac.uk> (raw)
In-Reply-To: <cunehvd44a8.fsf@hotblack-desiato.hh.sledj.net>
Hello
On Fri, 06 Jan 2012 08:35:27 +0000, David Edmondson <dme@dme.org> wrote:
> On Fri, 06 Jan 2012 00:29:39 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> > What is the best way of exporting/saving as text a mime-encoded email
> > from the emacs interface (e.g, if I want to save a mime-encoded email
> > containing a patch)?
> >
> > For non-mime emails View-raw is fine, but with mime encoded emails such
> > as (picked pretty much at random)
> > id:"1325240897-27525-1-git-send-email-dme@dme.org"
> > I haven't found any non-hack method.
>
> That message is 8bit UTF-8 at my end. Saving it use '|' works just fine
> for me. What encoding do you see?
Does saving the message like this give you a file you can apply directly
with the patch command? When I save it (using | or from view-raw) I get
a message which looks like
(Delivery headers)
From: ...
To: ...
Subject: =?UTF-8?q?=5BPATCH=5D=20emacs=3A=20Improved=20printing=20support=2E?=
Date: ..
(some X and list headers)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: notmuch-bounces@notmuchmail.org
Errors-To: notmuch-bounces@notmuchmail.org
QWRkIHZhcmlvdXMgZnVuY3Rpb25zIHRvIHByaW50IG5vdG11Y2ggbWVzc2FnZXMgYW5kIHRpZSB0
aGVtIHRvZ2V0aGVyCndpdGggYSBzaW1wbGUgZnJvbnRlbmQuIE5vIGtleWJpbmRpbmcgaXMgY3Vy
cmVudGx5IG1hZGUgdG8gZW5jb3VyYWdlCnBhcGVyIHNhdmluZy4KLS0tCgpSZXN1cnJlY3Rpbmcg
.. for 100 lines or so
The saved file is identical to the file in my maildir. But feeding it
to patch in the form patch -p1 < exported_file does not work.
I have just discovered git am which solves this problem for patches but
I think it might be useful to be able to export the plain-text email
sometimes.
(If this is all some messed up utf-8 settings my end then many apologies
for the noise)
Many thanks
Mark
next prev parent reply other threads:[~2012-01-06 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 0:29 Exporting mime email Mark Walters
2012-01-06 0:44 ` Jameson Graef Rollins
2012-01-06 1:01 ` Mark Walters
2012-01-06 8:35 ` David Edmondson
2012-01-06 10:27 ` Mark Walters [this message]
2012-01-06 10:39 ` David Edmondson
2012-01-06 10:51 ` Mark Walters
2012-01-06 11:07 ` David Edmondson
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=87k455p1mj.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=dme@dme.org \
--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).