From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, 12925@debbugs.gnu.org,
ethan.glasser.camp@gmail.com
Subject: bug#12925: 24.1; string-make-unibyte instead of string-as-unibyte
Date: Wed, 02 Jun 2021 16:36:27 +0300 [thread overview]
Message-ID: <83o8coxuas.fsf@gnu.org> (raw)
In-Reply-To: <877djcct0w.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 02 Jun 2021 15:09:35 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@iro.umontreal.ca, 12925@debbugs.gnu.org,
> ethan.glasser.camp@gmail.com
> Date: Wed, 02 Jun 2021 15:09:35 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Please note that I wasn't talking about inserting raw bytes, whether
> > they come from unibyte or multibyte buffers, I was talking about
> > inserting multibyte text that represents human-readable characters.
>
> OK, then we're in violent agreement there. I was simply pointing out
> that we can't change insertion of multibyte text in the simple way you
> seemed to be suggesting (i.e., just insert the bytes in the multibyte
> string
Yes, we need special handling of raw bytes, as usual.
> because a multibyte raw character is represented by several bytes
> (is it two or three? I forget)).
2 or 5.
prev parent reply other threads:[~2021-06-02 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 17:45 bug#12925: 24.1; string-make-unibyte instead of string-as-unibyte Ethan Glasser-Camp
2012-11-19 2:27 ` Stefan Monnier
2021-06-01 7:02 ` Lars Ingebrigtsen
2021-06-01 11:56 ` Eli Zaretskii
2021-06-01 13:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-01 14:03 ` Eli Zaretskii
2021-06-01 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-01 15:26 ` Eli Zaretskii
2021-06-02 5:07 ` Lars Ingebrigtsen
2021-06-02 12:07 ` Eli Zaretskii
2021-06-02 13:09 ` Lars Ingebrigtsen
2021-06-02 13:36 ` 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=83o8coxuas.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12925@debbugs.gnu.org \
--cc=ethan.glasser.camp@gmail.com \
--cc=larsi@gnus.org \
--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).