From: Miles Bader <miles.bader@necel.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: docs for insert-file-contents use 'bytes'
Date: Tue, 30 Sep 2008 15:06:17 +0900 [thread overview]
Message-ID: <buovdwerwva.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <86hc7y64vm.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 29 Sep 2008 16:04:13 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> EZ> Like with any other random bytes, I think: it will produce eight-bit-*
> EZ> characters in the buffer. IOW, you get garbled text.
>
> This is not a safe operation mode with multibyte sequences; is there a
> way to DTRT? I'm specifically thinking about a paged buffer mode where
> you only see a small portion of the file (for editing large files, as we
> discussed in another newsgroup a while ago).
Why is it "not safe"? How would you do things differently?
In conjunction with _file_ contents, a byte offset seems certainly the
most natural thing. An "encoded character offset", for instance, would
be far less efficient, much more complex to implement (and thus
buggier), and harder to use in general.
-Miles
--
Sabbath, n. A weekly festival having its origin in the fact that God made the
world in six days and was arrested on the seventh.
next prev parent reply other threads:[~2008-09-30 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 19:58 docs for insert-file-contents use 'bytes' Ted Zlatanov
2008-09-29 20:12 ` Eli Zaretskii
2008-09-29 21:04 ` Ted Zlatanov
2008-09-30 6:06 ` Miles Bader [this message]
2008-09-30 7:19 ` Eli Zaretskii
2008-09-30 13:48 ` Ted Zlatanov
2008-09-30 15:58 ` Stefan Monnier
2008-09-30 16:29 ` Eli Zaretskii
2008-10-01 0:44 ` Kenichi Handa
2008-10-01 16:54 ` Ted Zlatanov
2008-10-02 1:33 ` Kenichi Handa
2008-10-02 13:42 ` Ted Zlatanov
2008-10-02 18:55 ` Stefan Monnier
2008-10-03 13:55 ` Ted Zlatanov
2008-10-02 1:58 ` 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=buovdwerwva.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=tzz@lifelogs.com \
/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.