unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: alan@idiocy.org, 64697@debbugs.gnu.org
Subject: bug#64697: 29.0.92: cannot paste NUL on macOS (regression from Emacs 28)
Date: Tue, 18 Jul 2023 16:02:50 +0300	[thread overview]
Message-ID: <834jm174p1.fsf@gnu.org> (raw)
In-Reply-To: <1CC6B049-A652-4ACE-9E71-590D9A7893D1@gmail.com> (message from Mattias Engdegård on Tue, 18 Jul 2023 14:00:49 +0200)

> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Tue, 18 Jul 2023 14:00:49 +0200
> Cc: 64697@debbugs.gnu.org,
>  alan@idiocy.org
> 
> 18 juli 2023 kl. 13.28 skrev Eli Zaretskii <eliz@gnu.org>:
> 
> > do we want a unibyte string
> > here or a multibyte string?
> >  We should try to call either
> > make_unibyte_string or make_multibyte_string accordingly, because
> > make_string has its own ideas about which one to produce.
> 
> That is more than I expected to change in emacs-29, but we could do that too if you like.

Let's install your change on emacs-29, and do the rest (if needed) on
master.

> Since the input is UTF-8 the result, with the patch, will always be either a multibyte string or a unibyte ASCII string. Always making a multibyte string would also do and be marginally faster, but not more correct in any meaningful way.

OK, but please add a comment there with the above rationale.

Thanks.





  reply	other threads:[~2023-07-18 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  8:30 bug#64697: 29.0.92: cannot paste NUL on macOS (regression from Emacs 28) Mattias Engdegård
2023-07-18  9:22 ` Alan Third
2023-07-18 11:31   ` Eli Zaretskii
2023-07-18 11:28 ` Eli Zaretskii
2023-07-18 12:00   ` Mattias Engdegård
2023-07-18 13:02     ` Eli Zaretskii [this message]
2023-07-18 13:56       ` Mattias Engdegård
2023-08-19 17:34         ` Mattias Engdegård

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=834jm174p1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64697@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=mattias.engdegard@gmail.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 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).