unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Bob Halley <halley@play-bow.org>
Cc: emacs-devel@gnu.org
Subject: Re: UI input unresponsive on macOS
Date: Tue, 3 Jan 2017 17:49:00 +0000	[thread overview]
Message-ID: <20170103174900.GA49916@breton.holly.idiocy.org> (raw)
In-Reply-To: <AD6E8EF1-2155-4806-AE5C-B654DB7CE594@play-bow.org>

On Tue, Jan 03, 2017 at 08:59:43AM -0800, Bob Halley wrote:
> 
> > Can you try the attached patch?
> 
> It didn’t fix things, but I did find a way to reproduce the problem at will.
> 
> If start emacs, and then you run
> 
>     open -a /Applications/Emacs.app whatever_file_here

I didn’t even know you could do that. I wonder if I’ve accidentally
clobbered some notification or event somewhere. I’ll have to try and
work out how this works.

> For a file which isn’t open, then the UI becomes unresponsive to
> input. Typing C-G seems to unstick it eventually, but there can be
> very long delays (I timed one at 49 seconds) before it beeps and the
> UI becomes responsive. I’ve seen it spontaneously complete too,
> again after a long time (at least 30 seconds), but usually it does
> not complete.

I had some trouble with that sort of thing before. What was happening
then was that a time‐out in ns_select was being reached before it
would react. I had thought I’d fixed that particular problem for most
cases in the last patch, though.

> Sometimes when I “continue” in the debugger it unsticks whatever is
> stuck, though the file I was trying to open never opens.

One of the bugs I had with an earlier version of this code would go
away when I put a breakpoint on the relevant function. Debugging can
be hard. :)

Thanks for your help.

-- 
Alan Third



  reply	other threads:[~2017-01-03 17:49 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 [this message]
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
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

  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=20170103174900.GA49916@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=halley@play-bow.org \
    /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).