From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Andrus Newsgroups: gmane.emacs.devel Subject: Re: OS X / nextstep port: Loss of keyboard events Date: Tue, 15 Jan 2013 21:55:31 +0100 Message-ID: <6B0C48AE-E75A-42AF-B93E-CA0E74CE31D2@gmail.com> References: <20130107.183649.582103995909405288.hanche@math.ntnu.no> <18633CB6-56BF-400C-87D0-8F6D5250942C@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_CAEEF749-57F6-4F15-859D-A7E52DB64EEB" X-Trace: ger.gmane.org 1358283342 13544 80.91.229.3 (15 Jan 2013 20:55:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Jan 2013 20:55:42 +0000 (UTC) To: "emacs-devel@gnu.org discussions" , =?iso-8859-1?Q?Jan_Dj=E4rv?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 15 21:56:00 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TvDY5-0001eB-K8 for ged-emacs-devel@m.gmane.org; Tue, 15 Jan 2013 21:55:57 +0100 Original-Received: from localhost ([::1]:58781 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvDXp-0002i1-Ca for ged-emacs-devel@m.gmane.org; Tue, 15 Jan 2013 15:55:41 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:32863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvDXk-0002fu-Nv for emacs-devel@gnu.org; Tue, 15 Jan 2013 15:55:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TvDXj-0006sh-1S for emacs-devel@gnu.org; Tue, 15 Jan 2013 15:55:36 -0500 Original-Received: from mail-bk0-f42.google.com ([209.85.214.42]:47705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvDXi-0006s4-Mm for emacs-devel@gnu.org; Tue, 15 Jan 2013 15:55:34 -0500 Original-Received: by mail-bk0-f42.google.com with SMTP id ji2so332072bkc.29 for ; Tue, 15 Jan 2013 12:55:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:message-id:mime-version:subject:date :references:to:in-reply-to:x-mailer; bh=z3CgqQr5SL3WZyiYGC9r95SMT9joiiYsrjmnvLX2wSw=; b=ze+M7aQHkY8RyWEsaH5i5CAJHXfPq2HqqVJr7XP8Ij63fbVrOaSubkpTzJKj7h3VBv Gk2rYfNInvgfGIqZdZObTff2uBRL2MLpy/nMMKp3g37h1DADXnm1yZg/7QJnzrbci6Qw Mwlk2r6+xiW0cOlcrKWsGWO+DwT3Qk7zLG9gL7FNrhnWAxpy1Gka1LSAnu7Jphfx3oaM WkITtwBa6K8ezZs/yjfVl/K3yJb4ZeXQ2XQ9VmzlKXp+RE+ZOYphFhckRhDkt1HOwZHf S+apbpPZTNta8unRQIfP6Jd/K7L86mB1U5bIAntLty4+AaRITf81RfyWkYOIm8KFoEXf D0jA== X-Received: by 10.204.148.154 with SMTP id p26mr40853487bkv.31.1358283333580; Tue, 15 Jan 2013 12:55:33 -0800 (PST) Original-Received: from [10.0.2.25] (catv-80-99-48-145.catv.broadband.hu. [80.99.48.145]) by mx.google.com with ESMTPS id u3sm13902103bkw.9.2013.01.15.12.55.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 12:55:32 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.1499) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.214.42 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156410 Archived-At: --Apple-Mail=_CAEEF749-57F6-4F15-859D-A7E52DB64EEB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I haven't seen the problem since including this patch. But it was = always rather rare for me. Or rather I would go a long time without = seeing it, and then it would happen a lot and I would restart Emacs. = So, although I can't definitely say it's fixed, it does seem to be. -Ivan On Jan 8, 2013, at 10:22 AM, Jan Dj=E4rv wrote: > Hello. >=20 > Does this patch help: >=20 > =3D=3D=3D modified file 'src/nsterm.m' > --- src/nsterm.m 2012-12-10 02:00:42 +0000 > +++ src/nsterm.m 2013-01-08 09:21:58 +0000 > @@ -5170,6 +5170,7 @@ > if (NS_KEYLOG) > NSLog (@"doCommandBySelector: %@", NSStringFromSelector = (aSelector)); > =20 > + processingCompose =3D NO; > if (aSelector =3D=3D @selector (deleteBackward:)) > { > /* happens when user backspaces over an ongoing composition: >=20 >=20 > Jan D. >=20 > 8 jan 2013 kl. 03:29 skrev Paul Michael Reilly : >=20 >> I see somewhat similar behavior as well. I thought it might be = related to autosave but have no verification yet. I did confirm the = behavior using emacs -q and will gladly go after the problem with gdb = but I would very much appreciate some suggestions. I rebuilt twice in = the past week using the latest bazaar changes and saw the behavior in = both builds. My previous build is about 3 months old and does not show = the bad behavior, fwiw. >>=20 >> -pmr >>=20 >>=20 >> On Mon, Jan 7, 2013 at 2:01 PM, Ivan Andrus = wrote: >> On Jan 7, 2013, at 6:36 PM, Harald Hanche-Olsen = wrote: >>=20 >> > Once in a while, some frame stops receiving keyboard events. It = keeps >> > receiving mouse events, so I can move the cursor around and so = forth, >> > but typing into the frame has no effect. >> > >> > Apparently, if I just keep typing random junk into the frame, the >> > problem will resolve itself, with most of the input lost. (This is = a >> > new observation, not yet thoroughly confirmed. Previously, I would >> > just kill the frame and open a new one.) In any case, the problem >> > only affects one frame, and other frames work as usual. >> > >> > This is happening on OS X, --with-ns, recent builds from trunk. I >> > think the problem has been around for quite a while (i.e., weeks), = but >> > I just haven't gotten around to reporting it until now. >> > >> > I'd file a bug report, but the problem is that I have no idea how = to >> > reproduce the problem. It just happens at random times. >> > >> > Do other OS X users see this? Can you suggest something I could try = to >> > get more information next time it happens? I gather that the event >> > loop is notoriously hard to debug, however. >>=20 >> I have noticed this too. For me the problem "goes away" when I press = a letter. In other words only control or meta (or hyper probably) keys = don't work. When I press a regular letter then it inputs that character = and I am able to type control characters as normal. >>=20 >> Sadly, I can't offer any advice on how to debug it, but thought this = extra data point might be useful. I haven't noticed any clues as to = what might cause it, and it's rather rare. >>=20 >> -Ivan >>=20 >=20 --Apple-Mail=_CAEEF749-57F6-4F15-859D-A7E52DB64EEB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I = haven't seen the problem since including this patch.  But it was = always rather rare for me.  Or rather I would go a long time = without seeing it, and then it would happen a lot and I would restart = Emacs.  So, although I can't definitely say it's fixed, it does = seem to be.

-Ivan

On Jan 8, = 2013, at 10:22 AM, Jan Dj=E4rv <jan.h.d@swipnet.se> = wrote:

2012-12-10 02:00:42 = +0000
+++ src/nsterm.m 2013-01-08 09:21:58 = +0000
@@ -5170,6 +5170,7 @@
   if = (NS_KEYLOG)
     NSLog (@"doCommandBySelector: = %@", NSStringFromSelector (aSelector));
 
+ =  processingCompose =3D NO;
   if (aSelector =3D=3D= @selector (deleteBackward:))
    =  {
       /* happens when user = backspaces over an ongoing = composition:


Jan = D.

8 jan 2013 kl. 03:29 skrev Paul Michael = Reilly <pmr@pajato.com>:

I see somewhat similar behavior as well.  I thought it = might be related to autosave but have no verification yet.  I did = confirm the behavior using emacs -q and will gladly go after the problem = with gdb but I would very much appreciate some suggestions.  I = rebuilt twice in the past week using the latest bazaar changes and saw = the behavior in both builds.  My previous build is about 3 months = old and does not show the bad behavior, fwiw.

-pmr


On Mon, Jan 7, = 2013 at 2:01 PM, Ivan Andrus <darthandrus@gmail.com> wrote:
On Jan 7, 2013, at = 6:36 PM, Harald Hanche-Olsen <hanche@math.ntnu.no> = wrote:

> Once in a while, some frame stops receiving keyboard events. It = keeps
> receiving mouse events, so I can move the cursor around and so = forth,
> but typing into the frame has no effect.
>
> Apparently, if I just keep typing random junk into the frame, = the
> problem will resolve itself, with most of the input lost. (This is = a
> new observation, not yet thoroughly confirmed. Previously, I = would
> just kill the frame and open a new one.) In any case, the = problem
> only affects one frame, and other frames work as usual.
>
> This is happening on OS X, --with-ns, recent builds from trunk. = I
> think the problem has been around for quite a while (i.e., weeks), = but
> I just haven't gotten around to reporting it until now.
>
> I'd file a bug report, but the problem is that I have no idea how = to
> reproduce the problem. It just happens at random times.
>
> Do other OS X users see this? Can you suggest something I could try = to
> get more information next time it happens? I gather that the = event
> loop is notoriously hard to debug, however.

I have noticed this too.  For me the problem "goes away" when I = press a letter.  In other words only control or meta (or hyper = probably) keys don't work. When I press a regular letter then it inputs = that character and I am able to type control characters as normal.

Sadly, I can't offer any advice on how to debug it, but thought this = extra data point might be useful.  I haven't noticed any clues as = to what might cause it, and it's rather rare.

-Ivan

=


= --Apple-Mail=_CAEEF749-57F6-4F15-859D-A7E52DB64EEB--