From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7626@debbugs.gnu.org
Subject: bug#7626: 23.2.91; Rmail shows incorrect message encoding in the mode line
Date: Mon, 17 Jan 2011 20:35:38 +0900 [thread overview]
Message-ID: <tl7vd1nyd85.fsf@m17n.org> (raw)
In-Reply-To: <E1Pemui-00053A-Iv@fencepost.gnu.org> (message from Eli Zaretskii on Mon, 17 Jan 2011 06:06:20 -0500)
In article <E1Pemui-00053A-Iv@fencepost.gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > Rmail-mime does not perform file I/O, but decodes a text
> > that is already stored in a mbox buffer.
> But the mbox format uses Unix EOLs.
On Windows too? I didn't know that.
> In fact, Rmail will barf if you
> say "C-u g FILE RET", and FILE has DOS EOLs. So the EOL format is
> known in advance in this case.
Are you arguing that typing 'o' (rmail-output) will write
DOS EOL file when EOL type of buffer-file-coding-system of
rmail buffer is undecided and the system_eol_type is DOS?
Then, isn't it a bug of rmail-output?
The reason I decided to leave EOL type undecided is for the
case of M-x write-region on rmail buffer. In that case, I
think, following system_eol_type is the right thing.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2011-01-17 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 22:21 bug#7626: 23.2.91; Rmail shows incorrect message encoding in the mode line Eli Zaretskii
2010-12-13 0:29 ` Kenichi Handa
2010-12-13 3:47 ` Eli Zaretskii
2011-01-01 11:20 ` Eli Zaretskii
2011-01-14 4:28 ` Kenichi Handa
2011-01-14 17:22 ` Eli Zaretskii
2011-01-17 1:22 ` Kenichi Handa
2011-01-17 11:06 ` Eli Zaretskii
2011-01-17 11:35 ` Kenichi Handa [this message]
2011-01-17 12:24 ` Eli Zaretskii
2011-01-18 11:44 ` Kenichi Handa
2011-01-18 15:23 ` Eli Zaretskii
2011-01-20 3:53 ` Kenichi Handa
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=tl7vd1nyd85.fsf@m17n.org \
--to=handa@m17n.org \
--cc=7626@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.