all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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, 27 Jan 2017 09:56:02 +0200	[thread overview]
Message-ID: <83vat10wdp.fsf@gnu.org> (raw)
In-Reply-To: <87ziids1j2.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)

> From: npostavs@users.sourceforge.net
> Cc: 25521@debbugs.gnu.org,  Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 26 Jan 2017 21:02:41 -0500
> 
> > I wonder whether we should reinstate a wait there, but make it limited
> > so that it never infloops.  Otherwise, these issues will continue to
> > haunt us and the users.
> 
> This case can be solved in a simpler way, and in the other case
> (Bug#25511), I believe Martin was saying something similar, so I think
> it would be a bit premature to add the busy wait again.

Issues with rare use cases usually take many moons to emerge, but in
this case the complaints started right away.  So it seems like the
elimination of the loop interferes with non-rare use cases, which
means we will probably be seeing much more of similar complaints in
the future, including for stuff people do in their init files without
too detailed understanding of the underlying machinery.  I'd expect at
least some of these case not easily solved, and in any case it's a
nuisance to users and Lisp package developers.

What's more, a similar loop still exists on w32, so we will have
subtly different behavior on different platforms.

Reinstating the loop, but without the danger of inflooping, could have
taken care of these issues in advance.  Thus my proposal.





  reply	other threads:[~2017-01-27  7:56 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=83vat10wdp.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 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.