From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Thibault Polge <thibault@thb.lt>
Cc: 58945@debbugs.gnu.org
Subject: bug#58945: 29.0.50; Setting frame name in pgtk Emacs is asynchronous
Date: Thu, 03 Nov 2022 08:31:30 +0800 [thread overview]
Message-ID: <87fsf0g9p9.fsf@yahoo.com> (raw)
In-Reply-To: <87pme6oh69.fsf@thb.lt> (Thibault Polge's message of "Tue, 01 Nov 2022 15:58:22 +0100")
tags 58945 notabug
thanks
Thibault Polge <thibault@thb.lt> writes:
> In pgtk Emacs (built from a very recent git HEAD), running under the
> Sway window manager, setting a frame name like this:
>
> (set-frame-parameter (selected-frame) 'name "Some new name")
> (redisplay t)
>
> Doesn't immediately take effect.
>
> The example program below demonstrates this by triggering a race
> condition: it renames all frames, then immediately requests the state of
> the Sway window manager, and renames them back. Repeatedly eval'ing the
> final sexp randomly returns either the original or the renamed frame
> names. (When testing with a few frames, it never returned a mix of
> original or renamed names --- it's 100% one or the other)
>
> This is an issue because frame names is the only way to associate Emacs
> frames with Sway identifiers (or any wayland wm) on pgtk Emacs).
Setting the title on Wayland is asynchronous, just as it is with X. By
the time the request or PropertyNotify event reaches the compositor or
window manager, other processes may already have run. In addition,
running asynchronously improves performance.
I would recommend just waiting a set delay after setting the title.
next prev parent reply other threads:[~2022-11-03 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 14:58 bug#58945: 29.0.50; Setting frame name in pgtk Emacs is asynchronous Thibault Polge
2022-11-03 0:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-12 20:34 ` Stefan Kangas
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=87fsf0g9p9.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58945@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=thibault@thb.lt \
/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.