From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: xenodasein@tutanota.de, "Björn Bidar" <bjorn.bidar@thaodan.de>,
emacs-devel@gnu.org
Subject: Re: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning
Date: Wed, 30 Nov 2022 07:50:28 -0500 [thread overview]
Message-ID: <jwvcz94a9wh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87cz94vjgl.fsf@yahoo.com> (Po Lu's message of "Wed, 30 Nov 2022 18:13:14 +0800")
Po Lu [2022-11-30 18:13:14] wrote:
> xenodasein@tutanota.de writes:
>> To give less headaches to the users, why else. Have one binary,
>> do it dynamically.
> Then will you volunteer to write the code that makes it safe? And keep
> it working for the next 5 or so years, at least? Regardless of what the
> GTK developers decide to do in the meantime?
FWIW, I really wish we moved in this direction. Make it possible to
build a single Emacs executable which can use GNUstep frames, PGTK
frames, tty frames, X11 frames, some with Athena toolkit widgets others
with no-toolkit widgets, etc... ideally all at the same time.
For my own use the most important part is the support of both "toolkit"
and "no-toolkit" scrollbars, since I find the no-toolkit scrollbars more
useful than the toolkit ones.
Stefan
next prev parent reply other threads:[~2022-11-30 12:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:38 Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Björn Bidar
2022-11-27 0:48 ` 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 [this message]
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=jwvcz94a9wh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=xenodasein@tutanota.de \
/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).