From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: `write-region' writes different bytes than passed to it?
Date: Mon, 11 Feb 2019 14:44:57 -0500 [thread overview]
Message-ID: <jwv4l9aqfsx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 83imxql1rd.fsf@gnu.org
> Yes, in a better world, a better deity would be well advised to make
> raw bytes unnecessary and non-existent.
I think raw bytes are OK. The problem here is the encoding of a unibyte
text (i.e. treating the unibyte text as holding chars rather than bytes).
The two are quite different: Raw bytes happen because of "faulty" data.
Encoding of unibyte text happens because of faulty *code* (the code
should either not encode, or should be using multibyte text instead).
To some extent both are unavoidable, but we have more control over the code
executed in Emacs than over the data it has to manipulate.
Stefan
next prev parent reply other threads:[~2019-02-11 19:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 12:30 `write-region' writes different bytes than passed to it? Philipp Stephani
2018-12-11 12:42 ` Philipp Stephani
2018-12-11 15:42 ` Eli Zaretskii
2018-12-11 15:41 ` Eli Zaretskii
2018-12-11 16:36 ` Stefan Monnier
2018-12-11 18:05 ` Eli Zaretskii
2018-12-11 19:47 ` Stefan Monnier
2018-12-22 23:16 ` Philipp Stephani
2018-12-22 23:13 ` Philipp Stephani
2018-12-22 22:59 ` Philipp Stephani
2018-12-22 22:58 ` Philipp Stephani
2018-12-23 15:20 ` Eli Zaretskii
2019-02-10 19:06 ` Philipp Stephani
2019-02-10 20:05 ` Eli Zaretskii
2018-12-24 4:27 ` Stefan Monnier
2019-02-10 19:15 ` Philipp Stephani
2019-02-10 20:13 ` Eli Zaretskii
2019-02-10 22:25 ` Stefan Monnier
2019-02-11 3:31 ` Eli Zaretskii
2019-02-11 14:05 ` Stefan Monnier
2019-02-11 16:37 ` Eli Zaretskii
2019-02-11 19:44 ` Stefan Monnier [this message]
2019-02-11 20:20 ` Eli Zaretskii
2019-02-11 22:06 ` Stefan Monnier
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=jwv4l9aqfsx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.