From: Eli Zaretskii <eliz@gnu.org>
To: Yuchen Guo <yguo@posteo.net>
Cc: 66416@debbugs.gnu.org
Subject: bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland
Date: Tue, 10 Oct 2023 15:08:43 +0300 [thread overview]
Message-ID: <83pm1mvfw4.fsf@gnu.org> (raw)
In-Reply-To: <87cyxnoxp3.fsf@lan> (message from Yuchen Guo on Tue, 10 Oct 2023 05:26:00 +0000)
> From: Yuchen Guo <yguo@posteo.net>
> Cc: 66416@debbugs.gnu.org
> Date: Tue, 10 Oct 2023 05:26:00 +0000
>
> Besides, in my not so humble opinion, I think Emacs users should have
> the freedom of choosing the preferred font without crashing Emacs,
> regardless of defaults. Font is a personal matter and one shouldn't be
> dragged by others by the nose, as a Chinese idiom would say.
You do have the freedom, and Emacs gives users more freedom in
customizing fonts than most other GUI apps. You just need to know
very well what you are doing to exercise that freedom, so we are
trying hard to make the need for that as small and rare as possible.
> > Can you show screenshots of the same text as Emacs displays by
> > default, and as it should display according to your preferences?
>
> Sure. Here I made a GIF from the screenshots, hope you can spot the
> difference.
>
> https://codeberg.org/m0p/ublock-origin-mirror/raw/branch/main/cjk-good-vs-bad.gif
Thanks. The question is: how can Emacs distinguish between these
fonts and decide that one of them is not suitable. In general, Emacs
picks up the first font that matches the fontset's spec, so we need to
come up with two things: (a) the way for Emacs to distinguish between
these fonts, and (b) the way to encode the requirements for a "good"
font in our default fontset. Then Emacs will be able to pick up the
correct font automatically.
next prev parent reply other threads:[~2023-10-10 12:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 20:32 bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland Yuchen Guo
2023-10-09 10:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 11:19 ` Eli Zaretskii
2023-10-09 11:24 ` Eli Zaretskii
[not found] ` <87bkd7k6b8.fsf@lan>
2023-10-09 18:45 ` Eli Zaretskii
2023-10-09 19:07 ` Yuchen Guo
2023-10-10 2:30 ` Eli Zaretskii
2023-10-10 5:26 ` Yuchen Guo
2023-10-10 12:08 ` Eli Zaretskii [this message]
2023-10-10 12:59 ` Yuchen Guo
2023-10-10 13:40 ` Eli Zaretskii
2023-10-10 16:26 ` Yuchen Guo
2023-10-11 11:31 ` Eli Zaretskii
2023-10-11 12:45 ` Yuchen Guo
2023-10-11 13:12 ` Eli Zaretskii
2023-10-10 4:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 18:44 ` bug#66416: Coredump Yuchen Guo
2023-10-12 7:46 ` bug#66416: GDB output from new crash Yuchen Guo
2023-10-12 8:12 ` Yuchen Guo
2023-10-12 10:23 ` Eli Zaretskii
2023-10-12 11:22 ` Yuchen Guo
2023-10-12 12:31 ` Eli Zaretskii
2023-10-12 13:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 14:28 ` Yuchen Guo
2023-10-12 14:42 ` Yuchen Guo
2023-10-14 11:00 ` Eli Zaretskii
2023-10-14 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 12:38 ` Eli Zaretskii
2023-10-14 12:40 ` Yuchen Guo
2023-10-14 12:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 14:23 ` Yuchen Guo
2023-10-14 15:40 ` Eli Zaretskii
2023-10-15 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-15 5:54 ` Yuchen Guo
2023-10-12 11:43 ` Yuchen Guo
2023-10-14 19:14 ` bug#66416: 29.1; pgtk build crashes due to ftcrfont Yuchen Guo
2024-04-16 0:27 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87mspui23l.fsf@>
2024-04-16 12:16 ` Eli Zaretskii
2024-04-16 13:13 ` Mattias Engdegård
2024-04-16 14:21 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 13:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 14:19 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83pm1mvfw4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66416@debbugs.gnu.org \
--cc=yguo@posteo.net \
/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).