From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Running with both PGTK and an X toolkit?
Date: Sat, 11 Mar 2023 10:08:34 +0200 [thread overview]
Message-ID: <83cz5fyakd.fsf@gnu.org> (raw)
In-Reply-To: <87mt4kgll1.fsf@catern.com> (message from Spencer Baugh on Sat, 11 Mar 2023 00:47:55 +0000 (UTC))
> From: Spencer Baugh <sbaugh@catern.com>
> Date: Sat, 11 Mar 2023 00:47:55 +0000 (UTC)
> Cc: help-gnu-emacs@gnu.org
>
> Is this a change which would be interesting to upstream? I'm hesitant
> to embark on it if not...
Yes, we are definitely interested.
> Also, are there any smaller component changes which would be interesting
> upstream?
Yes, these changes can be made piecemeal. We already did similar
changes in the past, like converting the x_*, w32_*, and ns_*
functions into platform-independent gui_* functions. The trick is to
make this safely, because there's a possibility of never reaching the
end goal, due to Life(TM) or whatever, and so too deep changes that
increase complexity but are not taken to their projected goal are a
burden we should avoid. Small changes, which make it easier to
parameterize the implicit window-system dependencies and make them
explicit, and thus move us towards the goal, without introducing
unneeded complexities, is the way to go.
next prev parent reply other threads:[~2023-03-11 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:49 Running with both PGTK and an X toolkit? Spencer Baugh
2023-03-10 23:44 ` Po Lu
2023-03-11 0:47 ` Spencer Baugh
2023-03-11 1:21 ` Po Lu
2023-03-11 8:09 ` Eli Zaretskii
2023-03-11 8:08 ` Eli Zaretskii [this message]
2023-03-11 8:04 ` Eli Zaretskii
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=83cz5fyakd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).