all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Halley <halley@play-bow.org>
To: Alan Third <alan@idiocy.org>
Cc: 23924@debbugs.gnu.org
Subject: bug#23924: 25.1.50; Emacs NSInternalInconsistencyException on macos Sierra developer beta 2
Date: Mon, 11 Jul 2016 08:13:54 -0700	[thread overview]
Message-ID: <B9537EA8-92C3-480C-A01B-F8751D750138@play-bow.org> (raw)
In-Reply-To: <39AC2AF3-C87A-4743-803D-155A9E35081A@play-bow.org>


> Is it a bad thing to just always set send_appdefined=YES?  The code appears to be trying to suppress appdefined events in some cases, but it's not clear to me what happens if we stop trying to send only one.  Naively I'd think "why not, so the run loop gets stopped twice, it's a little extra work" but I don't know this code and am not familiar with the macOS API :)

FWIW, I made my emacs just always have send_appdefined=YES and nothing obviously bad has happened so far.






  reply	other threads:[~2016-07-11 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  0:20 bug#23924: 25.1.50; Emacs NSInternalInconsistencyException on macos Sierra developer beta 2 Bob Halley
2016-07-10 10:10 ` Alan Third
2016-07-10 16:06   ` Bob Halley
2016-07-10 16:43     ` Alan Third
2016-07-10 17:13       ` Bob Halley
2016-07-10 19:24       ` Bob Halley
2016-07-11 13:13       ` Bob Halley
2016-07-11 15:13         ` Bob Halley [this message]
2016-07-13 21:03         ` bug#23924: [PATCH] Only check for AppDefined events in OS X 10.10 (bug#23924) Alan Third
2016-07-13 23:08           ` Bob Halley
2016-07-17 14:15             ` Alan Third
2016-07-20 18:35               ` Bob Halley
2016-07-20 19:31                 ` Alan Third
2016-07-20 21:09                 ` bug#23924: [PATCH] Post AppDefined events from the main thread ONLY (bug#23934) Alan Third
2016-07-21 13:20                   ` Bob Halley
2016-07-22 21:10                     ` Bob Halley
2016-07-22 21:42                       ` 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=B9537EA8-92C3-480C-A01B-F8751D750138@play-bow.org \
    --to=halley@play-bow.org \
    --cc=23924@debbugs.gnu.org \
    --cc=alan@idiocy.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 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.