From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
1215@emacsbugs.donarmstrong.com
Cc: lekktu@gmail.com
Subject: bug#1215: 23.0.60; unibyte->multibyte conversion problem (in
Date: Sat, 17 Jan 2009 12:10:17 +0200 [thread overview]
Message-ID: <uwscu2qgm.fsf@gnu.org> (raw)
In-Reply-To: <jwv7i4vrn0y.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 16 Jan 2009 15:56:44 -0500
> Cc: 1215@emacsbugs.donarmstrong.com
>
> > but according to raw-text-unix's description:
>
> > t -- raw-text-unix
>
> > Raw text, which means text contains random 8-bit codes.
> > Encoding text with this coding system produces the actual byte
> > sequence of the text in buffers and strings. An exception is made for
> > eight-bit-control characters. Each of them is encoded into a single
> > byte.
>
> > you can save (almost) anything with it. What is the bug?
>
> The bug is that you can currently save (almost) anything with it. This is
> due to historical reasons, where different notions of "no encoding" were
> mixed up. So on save, raw-text-unix behaves pretty much like
> utf-8-mule under Emacs-23 and emacs-mule under Emacs-22. On load, it
> behaves pretty much like `binary'.
I documented this in the ELisp manual.
prev parent reply other threads:[~2009-01-17 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:00 bug#1215: 23.0.60; unibyte->multibyte conversion problem (in search-forward and friends) Eduardo Ochs
2008-10-22 14:51 ` Stefan Monnier
2009-01-16 0:19 ` Juanma Barranquero
2009-01-16 2:47 ` bug#1215: 23.0.60; unibyte->multibyte conversion problem (in Stefan Monnier
2009-01-16 2:59 ` Juanma Barranquero
2009-01-16 3:37 ` Stefan Monnier
2009-01-16 11:08 ` Juanma Barranquero
2009-01-16 20:56 ` Stefan Monnier
2009-01-17 10:10 ` Eli Zaretskii [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uwscu2qgm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1215@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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://git.savannah.gnu.org/cgit/emacs.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).