From: Po Lu <luangruo@yahoo.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK.
Date: Thu, 07 Apr 2022 08:32:36 +0800 [thread overview]
Message-ID: <87a6cxzqaj.fsf@yahoo.com> (raw)
In-Reply-To: <87tub6dl8a.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Wed, 06 Apr 2022 22:12:53 +0200")
Óscar Fuentes <ofv@wanadoo.es> writes:
> Is it possible at all to use the PGTK port on multiple graphical
> displays? Wayland does not provide network transparency.
X isn't network-transparent for the same reasons Wayland isn't: DRI2,
DRI3, GLX (unless you use indirect rendering) and MIT-SHM are not
network transparent. That doesn't mean the entire protocol can be
discarded as "not network transparent", and with various small proxies
both X and Wayland can be made completely network transparent.
Besides, you can run multiple Wayland displays locally as well.
next prev parent reply other threads:[~2022-04-07 0:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164921225790.11115.15669298143254852205@vcs2.savannah.gnu.org>
[not found] ` <20220406023058.315C7C009A8@vcs2.savannah.gnu.org>
2022-04-06 15:37 ` master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK Sean Whitton
2022-04-06 15:44 ` Robert Pluim
2022-04-06 18:45 ` Sean Whitton
2022-04-06 20:12 ` Óscar Fuentes
2022-04-07 0:32 ` Po Lu [this message]
2022-04-07 0:28 ` Po Lu
2022-04-07 0:49 ` Sean Whitton
2022-04-07 1:02 ` Po Lu
2022-04-07 2:11 ` Stefan Monnier
2022-04-07 2:45 ` Po Lu
2022-04-07 3:16 ` Stefan Monnier
2022-04-07 5:32 ` Sean Whitton
2022-04-07 23:04 ` Stefan Monnier
2022-04-08 4:09 ` Sean Whitton
2022-04-08 5:29 ` Sean Whitton
2022-04-08 6:13 ` Eli Zaretskii
2022-04-08 14:06 ` Sean Whitton
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=87a6cxzqaj.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).