From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: gongyi.liao@gmail.com, halley@play-bow.org,
mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: UI input unresponsive on macOS
Date: Fri, 17 Nov 2017 15:53:56 +0200 [thread overview]
Message-ID: <83r2sxggej.fsf@gnu.org> (raw)
In-Reply-To: <20171116193343.GA18478@breton.holly.idiocy.org> (message from Alan Third on Thu, 16 Nov 2017 19:33:43 +0000)
> Date: Thu, 16 Nov 2017 19:33:43 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: Gong-Yi Liao 廖宮毅 <gongyi.liao@gmail.com>,
> Eli Zaretskii <eliz@gnu.org>, halley@play-bow.org,
> emacs-devel@gnu.org
>
> > (make-thread
> > (lambda ()
> > (let (last-nonmenu-event)
> > (setq test (y-or-n-p-with-timeout "test" 2 'timeout)))))
> >
> > Athena: Works.
> > GTK+2: Timeout works, but buttons are not displayed.
> > GTK+3: Hangs.
> > NS: Crashes.
>
> I’m not sure how we could handle that on NS. Perhaps just refuse to
> display the dialogue at all, and return nil?
If you can detect this situation, it's possible. But silently
returning nil might not be a good idea, as it's hard to distinguish
that from normal return. How about displaying a warning? (You cannot
easily error out in a thread, so that's not a good option.)
next prev parent reply other threads:[~2017-11-17 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 13:36 UI input unresponsive on macOS Bob Halley
2017-01-03 14:36 ` Alan Third
2017-01-03 15:39 ` Bob Halley
2017-01-03 16:59 ` Bob Halley
2017-01-03 17:49 ` Alan Third
2017-01-04 3:52 ` Gong-Yi Liao 廖宮毅
2017-01-04 15:38 ` Eli Zaretskii
2017-01-05 4:34 ` Gong-Yi Liao 廖宮毅
2017-01-05 15:37 ` Eli Zaretskii
2017-01-05 17:00 ` Gong-Yi Liao 廖宮毅
2017-10-05 3:40 ` YAMAMOTO Mitsuharu
2017-11-16 19:33 ` Alan Third
2017-11-17 1:05 ` YAMAMOTO Mitsuharu
2017-11-17 13:53 ` Eli Zaretskii [this message]
2017-11-17 17:42 ` Alan Third
2017-11-18 0:24 ` YAMAMOTO Mitsuharu
2017-12-02 16:51 ` Alan Third
2017-01-04 21:09 ` Alan Third
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=83r2sxggej.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=gongyi.liao@gmail.com \
--cc=halley@play-bow.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.