From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Support for slrn-style verbatim marks
Date: Tue, 27 Sep 2005 11:17:17 +0900 [thread overview]
Message-ID: <b4mek7bz236.fsf@jpl.org> (raw)
In-Reply-To: <v9y85jilj7.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9y85jilj7.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
> I \201 in front of every non-ASCII character (Emacs/22.0.50). The
> saved MIME part (loading the file saved with `o') also is encoded as
> `emacs-mule-unix'.
Yes, it is caused by inserting decoded unibyte text into the
multibyte buffer. I've fixed it in the CVS trunk.
Consequently, I made unrelated changes to displaying of
text/verbatim parts, but I think they all are reasonable, and
will commit them into the v5-10 branch later.
next prev parent reply other threads:[~2005-09-27 2:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:31 Reiner Steib
2005-09-26 11:06 ` Adam Sjøgren
2005-09-26 18:08 ` Reiner Steib
2005-09-26 19:15 ` Adam Sjøgren
2005-09-26 21:09 ` Reiner Steib
2005-09-27 2:17 ` Katsumi Yamaoka [this message]
2005-09-27 12:53 ` Reiner Steib
2005-09-27 15:04 ` Simon Josefsson
2005-09-27 16:18 ` Reiner Steib
2005-09-28 9:43 ` Simon Josefsson
2005-09-28 3:23 ` Katsumi Yamaoka
2005-09-28 9:48 ` Reiner Steib
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=b4mek7bz236.fsf@jpl.org \
--to=yamaoka@jpl.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).