From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: emacs-devel@gnu.org
Subject: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning
Date: Sun, 27 Nov 2022 00:38:22 +0200 [thread overview]
Message-ID: <87cz99l4td.fsf@thaodan.de> (raw)
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?
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örn
next reply other threads:[~2022-11-26 22:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:38 Björn Bidar [this message]
2022-11-27 0:48 ` Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Po Lu
2022-11-28 0:09 ` Björn Bidar
2022-11-28 1:17 ` Po Lu
2022-11-28 8:44 ` Björn Bidar
2022-11-28 11:41 ` Po Lu
2022-11-30 9:27 ` xenodasein--- via Emacs development discussions.
2022-11-30 10:13 ` Po Lu
2022-11-30 12:50 ` Stefan Monnier
2022-11-30 13:39 ` Po Lu
2022-11-30 16:50 ` Stefan Monnier
2022-12-01 0:52 ` Po Lu
2022-12-01 0:56 ` Stefan Monnier
2022-12-01 2:38 ` Po Lu
2022-12-01 5:24 ` Stefan Monnier
2022-12-01 6:45 ` Po Lu
2022-12-05 20:01 ` chad
2022-12-06 11:39 ` Po Lu
2022-12-06 13:05 ` xenodasein--- via Emacs development discussions.
2022-12-06 13:24 ` Po Lu
2022-12-01 10:25 ` Manuel Giraud
2022-12-01 12:44 ` Visuwesh
[not found] ` <87cz94vjgl.fsf@yahoo.com-NI70zP3----9>
2022-11-30 11:51 ` xenodasein--- via Emacs development discussions.
2022-11-30 13:37 ` Po Lu
2022-11-30 14:00 ` xenodasein--- via Emacs development discussions.
2022-11-30 14:09 ` Po Lu
2022-11-30 15:51 ` xenodasein--- via Emacs development discussions.
2022-12-01 0:49 ` Po Lu
2022-11-30 16:23 ` Eli Zaretskii
2022-11-30 16:56 ` xenodasein--- via Emacs development discussions.
2022-11-30 17:43 ` Eli Zaretskii
2022-12-12 23:52 ` Björn Bidar
2022-12-13 1:22 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 6:33 Pedro Andres Aranda Gutierrez
2022-11-29 6:43 ` Po Lu
2022-11-29 9:36 ` Björn Bidar
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=87cz99l4td.fsf@thaodan.de \
--to=bjorn.bidar@thaodan.de \
--cc=emacs-devel@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 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).