unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Exporting mime email
Date: Fri, 06 Jan 2012 11:07:33 +0000	[thread overview]
Message-ID: <cunsjjt2ioa.fsf@hotblack-desiato.hh.sledj.net> (raw)
In-Reply-To: <87y5tl3xz0.fsf@qmul.ac.uk>

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

On Fri, 06 Jan 2012 10:51:47 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> > Presumably something is converting it from 8bit to base64 along the
> > path.
> 
> If it makes a difference my setup is gmail->offlineimap->notmuch

Mine is the same for the relevant messages.

> > I scouted around for other messages that include © (which is what I
> > presume causes the encoding), but the ones I have are all still 8bit.
> 
> A different example which shows the same problem (for me) is
> id:"m2fwg1uapw.fsf@gmail.com"

This one is encoded as quoted-printable. I agree that the output of
     | cat >/tmp/file
in the emacs UI produces the encoded file and that it is identical to
the file on disk.

Hence, I can reproduce the problem you reported :-)

(Maybe amusingly) the printing stuff that you originally mentioned
included some code to produce a 'text' version of a message for
printing. Maybe that could also be used to implement a simple
`notmuch-show-save-message' command?

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2012-01-06 11:07 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
2012-01-06 10:39     ` David Edmondson
2012-01-06 10:51       ` Mark Walters
2012-01-06 11:07         ` David Edmondson [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=cunsjjt2ioa.fsf@hotblack-desiato.hh.sledj.net \
    --to=dme@dme.org \
    --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).