unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Ethan Glasser-Camp <ethan.glasser.camp@gmail.com>
To: Ethan Glasser-Camp <ethan.glasser.camp@gmail.com>,
	Tomi Ollila <tomi.ollila@iki.fi>,
	Michael Stapelberg <michael+nm@stapelberg.de>,
	notmuch@notmuchmail.org
Subject: Re: [BUG] Saving attachments containing UTF-8 chars
Date: Sun, 18 Nov 2012 13:02:55 -0500	[thread overview]
Message-ID: <87txsm23hs.fsf@betacantrips.com> (raw)
In-Reply-To: <87zk2f1nt0.fsf@betacantrips.com>

Ethan Glasser-Camp <ethan.glasser.camp@gmail.com> writes:

> Writing this buffer using C-x C-w encodes it correctly too. So I think
> this is an emacs MIME problem. We call mm-save-part, which calls
> mm-save-part-to-file, which calls mm-with-unibyte-buffer. Hmm..
>
> Indeed, it seems that inserting this character into a file that's been
> marked "unibyte" using (set-buffer-multibyte nil) turns it into the ^Y
> character (ASCII code 0x19 -- the character that comes out in the patch
> file). There's probably a technical reason that this should be true, but
> I can't think of why that would be.

The more I think about this, the more convinced I become that this is a
bug in emacs's multibyte handling. I've filed a bug, see:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12925

But I think Tomi's going to formalize his hacky patch and send that out
later too. When he does, it has my +1.

Ethan

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 13:30 [BUG] Saving attachments containing UTF-8 chars Michael Stapelberg
2012-10-29 16:31 ` Tomi Ollila
2012-11-18  5:29   ` Ethan Glasser-Camp
2012-11-18 18:02     ` Ethan Glasser-Camp [this message]
2012-11-27  2:11 ` David Bremner
2012-11-30  8:51   ` Michael Stapelberg
2012-11-30  9:34     ` Mark Walters
2012-11-30 11:14       ` Michael Stapelberg
2012-11-30 13:02         ` Mark Walters
2012-11-30 13:25           ` Michael Stapelberg
2012-11-30 13:12         ` Tomi Ollila

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=87txsm23hs.fsf@betacantrips.com \
    --to=ethan.glasser.camp@gmail.com \
    --cc=michael+nm@stapelberg.de \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).