all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuchen Guo <yguo@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66416@debbugs.gnu.org
Subject: bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland
Date: Wed, 11 Oct 2023 12:45:58 +0000	[thread overview]
Message-ID: <86r0m1coop.fsf@lan> (raw)
In-Reply-To: <838r89v1iv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 11 Oct 2023 14:31:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Try font-info instead, and look at the last, 13th, element of the
> vector it returns.  The doc string of font-info describes what it can
> tell you.

I obtained the following output for the Simplified Chinese Serif font:

(opentype
 ((DFLT (nil aalt calt ccmp dlig fwid hist hwid liga pwid ruby vert
             vrt2))
  (cyrl (nil aalt calt ccmp dlig fwid hist hwid liga locl pwid ruby
             vert vrt2)
        (JAN\  aalt calt ccmp dlig fwid hist hwid liga locl pwid ruby
               vert vrt2)
        (KOR\  aalt calt ccmp dlig fwid hist hwid liga locl pwid
               ruby vert vrt2)
        (ZHH\  aalt calt ccmp dlig fwid hist hwid liga locl pwid
               ruby vert vrt2)
        (ZHS\  aalt calt ccmp dlig fwid hist hwid liga locl pwid
               ruby vert vrt2)
        (ZHT\  aalt calt ccmp dlig fwid hist hwid liga locl pwid
               ruby vert vrt2))...)

...500+ lines omitted...

It seems to me that the font declares support for all CJK scripts.

> font-spec

Thanks for the detailed suggestions, but I think I will not tweak that
any further at the moment, since I still do not have sufficient
knowledge for doing so.  Besides, I am already able to sit back and
enjoy variable pitch font in its full 4K-resolution, pure GTK on Wayland
glory.

By God, I was writing TeX in TUI Emacs for a whole year!  I didn't know
what was missing in my life.  Obligatory screenshot:

https://codeberg.org/m0p/ublock-origin-mirror/raw/branch/main/4k.png

===================================================

Back to the original bug report:

Emacs has not crashed since the rebuild from latest commit in emacs-29
branch.  Previously Emacs server was crashing every few hours.

If there is no more crashes in the coming week, then I think this issue
can be closed.





  reply	other threads:[~2023-10-11 12:45 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86r0m1coop.fsf@lan \
    --to=yguo@posteo.net \
    --cc=66416@debbugs.gnu.org \
    --cc=eliz@gnu.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.