all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Po Lu <luangruo@yahoo.com>
Cc: 53957@debbugs.gnu.org
Subject: bug#53957: 29.0.50; pgtk: starting emacsclient from thunar breaks X clipboard access
Date: Sun, 13 Feb 2022 08:08:45 +0000	[thread overview]
Message-ID: <d20a85fc-19bc-b150-d42d-74096c6e2f44@posteo.eu> (raw)
In-Reply-To: <878rufo99v.fsf@yahoo.com>

Po Lu writes:
> If you're using X, you shouldn't be using PGTK.  The support provided by
> the real X port is miles ahead of what GTK can offer.
Is --with-xinput2 supposed to work well without PGTK ? I run into a
separate issue with key bindings that makes it unusable without.
> That aside, I suspect emacsclient is causing Emacs to open a second
> display connection, which causes clipboard access in PGTK to be disabled
> due to a GTK bug.
>
> What does (x-display-list) evaluate to in the buggy Emacs, after you
> create the other frame which causes the bug?
Indeed, (x-diplay-list) originally reports (":0.0"), and after the
second frame is created, (":0.0" ":0").

If the bug is with GTK, can you think of any workaround on my end ?
> Thanks.

Thank you.

-- 
Sébastien Miquel






  reply	other threads:[~2022-02-13  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 12:46 bug#53957: 29.0.50; pgtk: starting emacsclient from thunar breaks X clipboard access Sébastien Miquel
2022-02-13  1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13  8:08   ` Sébastien Miquel [this message]
2022-02-13  8:17     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13  8:39       ` Sébastien Miquel
2022-02-13  9:44         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d20a85fc-19bc-b150-d42d-74096c6e2f44@posteo.eu \
    --to=sebastien.miquel@posteo.eu \
    --cc=53957@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.