From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: OS X / nextstep port: Loss of keyboard events Date: Tue, 8 Jan 2013 10:22:58 +0100 Message-ID: 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=_91DD5E4D-686A-4F07-9D8D-E0FCC3DE3E4C" X-Trace: ger.gmane.org 1357636991 5670 80.91.229.3 (8 Jan 2013 09:23:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jan 2013 09:23:11 +0000 (UTC) Cc: Ivan Andrus , Harald Hanche-Olsen , emacs-devel@gnu.org To: Paul Michael Reilly Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 08 10:23:27 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 1TsVP5-0003NJ-G2 for ged-emacs-devel@m.gmane.org; Tue, 08 Jan 2013 10:23:27 +0100 Original-Received: from localhost ([::1]:42200 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsVOp-0004rl-QY for ged-emacs-devel@m.gmane.org; Tue, 08 Jan 2013 04:23:11 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59833) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsVOl-0004r3-OD for emacs-devel@gnu.org; Tue, 08 Jan 2013 04:23:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsVOj-0001Hi-SG for emacs-devel@gnu.org; Tue, 08 Jan 2013 04:23:07 -0500 Original-Received: from mailout.melmac.se ([62.20.26.67]:44948) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsVOj-0001Gn-Gp for emacs-devel@gnu.org; Tue, 08 Jan 2013 04:23:05 -0500 Original-Received: from mail01.melmac.se (mail01.melmac.se [62.20.26.80]) by mailout.melmac.se (Postfix) with ESMTP id DAFF99265 for ; Tue, 8 Jan 2013 10:22:59 +0100 (CET) Original-Received: (qmail 26973 invoked by uid 89); 8 Jan 2013 09:22:59 -0000 Original-Received: from h-46-59-42-18.na.cust.bahnhof.se (HELO coolsville.localdomain) (boel.djarv@bdtv.se@46.59.42.18) by mail01.melmac.se with ESMTPA; 8 Jan 2013 09:22:59 -0000 Original-Received: from [172.20.199.13] (zeplin [172.20.199.13]) by coolsville.localdomain (Postfix) with ESMTPSA id 739747FA06C; Tue, 8 Jan 2013 10:22:59 +0100 (CET) In-Reply-To: X-Mailer: Apple Mail (2.1499) X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 62.20.26.67 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:156135 Archived-At: --Apple-Mail=_91DD5E4D-686A-4F07-9D8D-E0FCC3DE3E4C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hello. Does this patch help: =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: Jan D. 8 jan 2013 kl. 03:29 skrev Paul Michael Reilly : > 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 --Apple-Mail=_91DD5E4D-686A-4F07-9D8D-E0FCC3DE3E4C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 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=_91DD5E4D-686A-4F07-9D8D-E0FCC3DE3E4C--