From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 42904@debbugs.gnu.org, alan@idiocy.org
Subject: bug#42904: [PATCH] Non-Unicode frame title crashes Emacs on macOS
Date: Tue, 18 Aug 2020 17:40:33 +0300 [thread overview]
Message-ID: <83a6ysf25a.fsf@gnu.org> (raw)
In-Reply-To: <CDAE06B8-6113-457E-9C7D-F3D2064286A5@acm.org> (message from Mattias Engdegård on Tue, 18 Aug 2020 16:11:02 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 18 Aug 2020 16:11:02 +0200
> Cc: Alan Third <alan@idiocy.org>, 42904@debbugs.gnu.org
>
> 18 aug. 2020 kl. 14.24 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > It isn't wrong (and there's no need to worry about alignment in this
> > case, AFAIK).
>
> Do you mean that SDATA is guaranteed to be aligned, or that no NS platforms that Emacs runs on (or is likely to run on in the near future, such as macOS on arm64) trap on unaligned?
Both, AFAIK.
> it is not reasonable to depend on non-Unicode characters being translated to spaces
We are not the only program which does that, but.
> > Why is it a problem to display a space instead of invalid bytes in
> > this case?
>
> A problem is not necessary for a change to be desirable. The Unicode replacement character clearly indicates that something could not be encoded correctly, and the exact position for it
But that character only makes sense when it can be displayed, because
otherwise no one will realize what was the problem.
Anyway, this discussion should be on emacs-devel, not as part of an
unrelated bug report.
next prev parent reply other threads:[~2020-08-18 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 14:11 bug#42904: [PATCH] Non-Unicode frame title crashes Emacs on macOS Mattias Engdegård
2020-08-17 14:54 ` Andrii Kolomoiets
2020-08-17 15:55 ` Mattias Engdegård
2020-08-17 15:55 ` Eli Zaretskii
2020-08-17 16:11 ` Mattias Engdegård
2020-08-17 17:05 ` Eli Zaretskii
2020-08-17 18:48 ` Mattias Engdegård
2020-08-17 19:56 ` Alan Third
2020-08-18 8:07 ` Mattias Engdegård
2020-08-18 8:43 ` Alan Third
2020-08-18 11:48 ` Mattias Engdegård
2020-08-18 12:22 ` Eli Zaretskii
2020-08-18 17:28 ` Alan Third
2020-08-20 9:27 ` Mattias Engdegård
2020-08-20 13:24 ` Eli Zaretskii
2020-08-20 18:46 ` Mattias Engdegård
2020-08-20 19:13 ` Eli Zaretskii
2020-08-21 9:39 ` Mattias Engdegård
2020-08-21 13:26 ` Eli Zaretskii
2020-08-21 14:53 ` Mattias Engdegård
2020-08-21 15:27 ` Eli Zaretskii
2020-08-21 15:50 ` Mattias Engdegård
2020-08-23 17:23 ` Mattias Engdegård
2020-08-20 13:24 ` Alan Third
2020-08-20 17:44 ` Mattias Engdegård
2020-08-18 12:24 ` Eli Zaretskii
2020-08-18 14:11 ` Mattias Engdegård
2020-08-18 14:40 ` Eli Zaretskii [this message]
2020-08-18 15:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6ysf25a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42904@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=mattiase@acm.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.