From: martin rudalics <rudalics@gmx.at>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 25521@debbugs.gnu.org, qwxlea@gmail.com
Subject: bug#25521: 26.0.50; After (make-frame '((name . "foo"))) (select-frame-by-name "foo") doesn't see the frame
Date: Fri, 29 Sep 2017 10:33:18 +0200 [thread overview]
Message-ID: <59CE054E.1010604@gmx.at> (raw)
In-Reply-To: <87poacfifx.fsf@users.sourceforge.net>
> I think you might have to change window managers.
Then I'll probably prefer to rather not play around with this.
> Hmm, that is actually less effect than I expected. I recall now that
> some non-relevant MapNotify events get sent in this case [1]. These
> make x_wait_for_event (f, MapNotify) return earlier than the previous
> busy wait.
>
> Should we wrap a timeout loop around the x_wait_for_event call? Or make
> the wait more selective (e.g., check that the given frame matches)?
> Seems a bit like overkill considering that a timeout of longer than 1
> second is unlikely to be wanted, on the other hand, we're not really
> waiting for the right thing...
>
> [1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24091#57
Shouldn't it work to wait only for VisibilityNotify events for the given
frame?
martin
next prev parent reply other threads:[~2017-09-29 8:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 21:05 bug#25521: 26.0.50; After (make-frame '((name . "foo"))) (select-frame-by-name "foo") doesn't see the frame Alex 'QWxleA' Poslavsky
2017-01-24 23:35 ` npostavs
2017-01-25 3:37 ` Eli Zaretskii
2017-01-25 3:31 ` Eli Zaretskii
2017-01-25 6:47 ` Alex (QWxleA)
2017-01-25 23:43 ` npostavs
2017-01-26 11:40 ` Alex (QWxleA)
2017-01-26 14:37 ` npostavs
2017-01-26 15:48 ` Alex (QWxleA)
2017-01-27 2:02 ` npostavs
2017-01-27 7:56 ` Eli Zaretskii
2017-06-30 3:08 ` npostavs
2017-06-30 6:09 ` Eli Zaretskii
2017-06-30 6:52 ` martin rudalics
2017-09-01 3:13 ` npostavs
2017-09-01 6:56 ` Eli Zaretskii
2017-09-01 13:02 ` martin rudalics
2017-09-01 13:41 ` npostavs
2017-09-01 15:45 ` martin rudalics
2017-09-26 2:54 ` Noam Postavsky
2017-09-27 8:11 ` martin rudalics
2017-09-27 12:13 ` Noam Postavsky
2017-09-29 8:33 ` martin rudalics [this message]
2017-09-29 12:48 ` Noam Postavsky
2017-09-29 18:19 ` martin rudalics
2017-09-29 22:47 ` Noam Postavsky
2017-09-29 13:39 ` Eli Zaretskii
2017-10-14 2:14 ` Noam Postavsky
2017-10-14 8:36 ` martin rudalics
2017-10-15 18:22 ` Noam Postavsky
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=59CE054E.1010604@gmx.at \
--to=rudalics@gmx.at \
--cc=25521@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=qwxlea@gmail.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 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).