From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yuchen Guo Newsgroups: gmane.emacs.bugs Subject: bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland Date: Tue, 10 Oct 2023 12:59:58 +0000 Message-ID: <875y3ews35.fsf@lan> References: <865y3gq2in.fsf@lan> <83mswsvy0p.fsf@gnu.org> <87bkd7k6b8.fsf@lan> <831qe3ws6d.fsf@gnu.org> <87mswr4ntw.fsf@lan> <83wmvvus3w.fsf@gnu.org> <87cyxnoxp3.fsf@lan> <83pm1mvfw4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32410"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 66416@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 10 15:01:54 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qqCMo-0007tf-8M for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 10 Oct 2023 15:01:42 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qqCLy-0006Fa-Sw; Tue, 10 Oct 2023 09:00:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qqCLr-00069U-00 for bug-gnu-emacs@gnu.org; Tue, 10 Oct 2023 09:00:44 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qqCLp-0006Zb-6x for bug-gnu-emacs@gnu.org; Tue, 10 Oct 2023 09:00:42 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qqCMA-0000Ry-BW for bug-gnu-emacs@gnu.org; Tue, 10 Oct 2023 09:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Yuchen Guo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 10 Oct 2023 13:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66416 X-GNU-PR-Package: emacs Original-Received: via spool by 66416-submit@debbugs.gnu.org id=B66416.16969428321678 (code B ref 66416); Tue, 10 Oct 2023 13:01:02 +0000 Original-Received: (at 66416) by debbugs.gnu.org; 10 Oct 2023 13:00:32 +0000 Original-Received: from localhost ([127.0.0.1]:34270 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqCLf-0000Qz-FM for submit@debbugs.gnu.org; Tue, 10 Oct 2023 09:00:31 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:50789) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqCLb-0000Qe-Pw for 66416@debbugs.gnu.org; Tue, 10 Oct 2023 09:00:29 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id B19E4240104 for <66416@debbugs.gnu.org>; Tue, 10 Oct 2023 14:59:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1696942799; bh=ySczAILrhKgdO2Q+02Fex9LULfRMfRpcUwlHZXyrUM4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=SxzFAig40wjFDwKhVJmRnA7O1750zsKAIl7bs+wius1QRslCeL7l/64sj3gn6G2v4 Qw8prawYuoOYbao2qR3dWGOQsIqB1DNdLpvMRQhE8Wai4sdMQC/4h+5pzMM96jZLet /3mhHzkk1/NaxyMt2TbKAPZF42KBYj8qxKOldsPAlKus8J4cWS6Pt1HzNw35GO5aj4 /OeLvMdbHoz1MyArWvxF2EDpG/jewWc3Us/hk027t5U+qWPKescgGq9iWyqlf+4Vp5 I6AlrhG4Ui+o0wvjOG6ccO+edJpRdrAz/OBgnG4lx6kJGu1XMdnR4XvkKlP1GdFE2u Zb0oP6n6LLGag== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4S4bbM0zTLz9s08; Tue, 10 Oct 2023 14:59:58 +0200 (CEST) In-Reply-To: <83pm1mvfw4.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Oct 2023 15:08:43 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:272209 Archived-At: Eli Zaretskii writes: > You do have the freedom, and Emacs gives users more freedom in > customizing fonts than most other GUI apps. In my experience, Emacs is certainly one of, if not the most effective at customizing fonts, made even more impressive considering the fact that everything is controlled by elisp. Kudos to you for making a truly wonderful GUI possible! > 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. Yes. In a previous reply you mentioned that this configuration is non-trivial, and indeed a perfect out-of-the-box experience is a noble goal in itself. Alas, some of us users would still try to customize the fonts with very little understanding of the intricacies of Emacs internals. > Thanks. The question is: how can Emacs distinguish between these > fonts and decide that one of them is not suitable. I think this is not possible without the user explicitly specifying which variant is needed. In HTML this is done with language tags, such as lang="zh-Hans", but this strategy only covers a minority of cases, because - the author of the HTML document has to specify this language tag - the browser must understand this tag - only applies to HTML documents In most other cases, such as the user interface of an Android phone, the default variant is chosen during language configuration. If a non-CJK language was chosen, such as en-US for American English (I do this), it will behave in the same manner as Emacs. > 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. "Good" is, in this case, defined by user. One font suitable for Mainland China users is not suitable for Taiwan, Hong Kong or Japan users, and vice versa. In other words, it is impossible for Emacs to determine what variant does a given user prefer. But there's good news. I've rebuilt Emacs from latest commit (9 hours ago) in the emacs-29 branch, with debug symbols enabled. Fresh out of the oven! This was all made very simple and declarative thanks to the Nix package manager: https://codeberg.org/m0p/dotfiles/commit/e1fb4ffc4b4ce3a914adbd4c4a49863b2a48afeb with the following init.el https://codeberg.org/m0p/dotfiles/raw/commit/eec25a4ae443de78ea3d8ea3d94541060d7861d7/imports/not-nix-config-files/emacs-init.el We will see if Emacs crashes again. So far with (4 hours, 43 minutes, 3 seconds) uptime.