From: Eli Zaretskii <eliz@gnu.org>
To: 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, 30 Jun 2017 09:09:05 +0300 [thread overview]
Message-ID: <837ezuqa66.fsf@gnu.org> (raw)
In-Reply-To: <87wp7ukw8x.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: 25521@debbugs.gnu.org, qwxlea@gmail.com
> Date: Thu, 29 Jun 2017 23:08:46 -0400
>
> How about removing the delay from w32 as well, and implementing it in
> lisp, then it will be easier to play with
If it works, why not? Just make sure this is well tested in the many
use cases where new frames pop up, including the initial frame, the
additional frames created by "C-x 5" and 'make-frame', the
minibufferless and minbuffer-only frames, the non-nil pop-up-frames
case, the tooltip frames, ...
> (by the way,
> x_make_frame_visible in nsterm.m does not have any delay so we already
> had different behaviour on different platforms).
To tell the truth, the NS port was never well in our sights.
Thanks.
next prev parent reply other threads:[~2017-06-30 6:09 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 [this message]
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
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=837ezuqa66.fsf@gnu.org \
--to=eliz@gnu.org \
--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).