From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Bj=C3=B6rn?= Bidar Newsgroups: gmane.emacs.devel Subject: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Date: Sun, 27 Nov 2022 00:38:22 +0200 Message-ID: <87cz99l4td.fsf@thaodan.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15992"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 26 23:39:18 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oz3pN-0003tR-EV for ged-emacs-devel@m.gmane-mx.org; Sat, 26 Nov 2022 23:39:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oz3oc-0005oD-VB; Sat, 26 Nov 2022 17:38:30 -0500 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 1oz3ob-0005o4-6f for emacs-devel@gnu.org; Sat, 26 Nov 2022 17:38:29 -0500 Original-Received: from thaodan.de ([185.216.177.71]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oz3oZ-0006uY-1E for emacs-devel@gnu.org; Sat, 26 Nov 2022 17:38:28 -0500 Original-Received: from odin (dsl-trebng12-b04885-76.dhcp.inet.fi [176.72.133.76]) by thaodan.de (Postfix) with ESMTPSA id 1FC5AD08A05 for ; Sun, 27 Nov 2022 00:38:23 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thaodan.de; s=mail; t=1669502303; bh=ixzRziNfgaaNCNXgac8ydKO45wR7xRWZH1NLnJ9RxEQ=; h=From:To:Subject:Date; b=GmEqP1zMv4RfUd4j9bOO4jtMntXAkfnb5upCXhgaSukgQ7oZ+xaIFmzXp43g/PoWx yIcG1KptHRCGmc5hooYUhIe2JCnrK3LW2PVv4pb+EldDycBlzqsNqIz1DEla9BhLEj QeBMrONB/QataSVIg1q3EYVsreqkcMhFK/9wYPBHDzZv7bscQamGb+ttOBMdMRnD+r veJWqCM4YxIYXpzMQ6xuRkbxnhmothaL9wDpk550SR4LkGpm96gzzGtmp7qh15NEP6 /Ac6oR82SRRI9N8RoNz8JVR2tjzZZjW19TQ7i1PVb0U0YKPZRq2Rcls095+3EZgV2b f1qXiEWQzpOB93CCsIYF+0waEjEjLyR11XLwtAQzoERz1TH46PfY4FuzFg7tnNMERu nrnGNchZsvc9cmRrh1UQNJPjA/XMUJ0QQ1PZkOmSxEFod9N8BQ+7ycH0JSLGN5pl7I 7bYt7d1GZVw6k4vqCBbVtxdHQ99foYal3Fd84KHKKL7icLEAvIIO6+7wqgV9aqcKeQ jJlIuDm+Qe4F6ISwevszUASg8TtDZezPaajhU3wemXKADSfOEety8B6iXE3FHzQt/P lRSgv3lAvbsvS0Qx3mmgt+Sbv8/M3QLD0xZfRU3vYEfdxmDJUliaLTmq+g1BEBWlAk Xo2XS7xzp6DCVd0ypzDi7img= Received-SPF: pass client-ip=185.216.177.71; envelope-from=bjorn.bidar@thaodan.de; helo=thaodan.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300599 Archived-At: Hello, I have a questions regarding PGTK especially in the context of X11 and Wayland in parallel. I sometimes use X11 and sometimes Wayland, I build my Emacs with PGTK to able to do both (without XWayland). I also was under the impression that fondering is better using PGTK when using a high dpi screen, even under X11. Was that wrong?=20 Now there's this big warning block wich appears when you use PGTK under X11. - Will it break emacs --daemon? The frame is spawned right when the X11 display connection is initiated. - I think it kinda rude to right out spawn a big window on every start, it doesn't fit into how emacs usually acts. What I'm trying to say is I think it is ok so show a warning every time server starts but adding this big blob of text that spawns 2/10 of the screen when Emacs is in fullscreen is a little much. I wonder how viable this strategy if Emacs has to be compiled twice for Wayland support. Br, Bj=C3=B6rn