From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: OS X / nextstep port: Loss of keyboard events Date: Mon, 7 Jan 2013 21:29:02 -0500 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 Content-Type: multipart/alternative; boundary=bcaec54d3ed2861efa04d2bdb550 X-Trace: ger.gmane.org 1357612152 7879 80.91.229.3 (8 Jan 2013 02:29:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jan 2013 02:29:12 +0000 (UTC) Cc: Harald Hanche-Olsen , emacs-devel@gnu.org To: Ivan Andrus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 08 03:29:28 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 1TsOwO-0004wm-KV for ged-emacs-devel@m.gmane.org; Tue, 08 Jan 2013 03:29:24 +0100 Original-Received: from localhost ([::1]:56662 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsOw8-0004VK-W4 for ged-emacs-devel@m.gmane.org; Mon, 07 Jan 2013 21:29:08 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:54593) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsOw5-0004VF-Vh for emacs-devel@gnu.org; Mon, 07 Jan 2013 21:29:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsOw4-0000CE-B6 for emacs-devel@gnu.org; Mon, 07 Jan 2013 21:29:05 -0500 Original-Received: from mail-ob0-f180.google.com ([209.85.214.180]:53352) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsOw4-0000C6-3l for emacs-devel@gnu.org; Mon, 07 Jan 2013 21:29:04 -0500 Original-Received: by mail-ob0-f180.google.com with SMTP id wd20so18562491obb.11 for ; Mon, 07 Jan 2013 18:29:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ftuPcEUJoOHUlIFKZiaWFqfqB8KWieMUUQkbEzSbU8E=; b=EE7IglkfRXEGyE4bmqvS/kf6LEzgnO/CPnNl/gxvMfP3DJ/YEe126UI5Y+pJFFrzHZ aCc3x28Z3UVYxCtyVza2DJcevDq37bSU413yBrsG1Q2UNwY2u04Z5ifpMKCBpQNfbS35 K8tdeg2FFWmnrQbvvHJejbcpnBEXdIE/SI/olAF6TWvubO2ee2BIM/RB1PsT0tSBS8Kz e2CQidrHYJKz7prQnQBccxMWfKtUeG9b36Nwd/mdn9qPKYW/cMmKwru0bL5y6MxwfUiX ZIgRATnWSRaOI6F5Ozbfp0gTMXit84pMDN2gVbam5XWQTwa+xWCFPkPwx6M/4pg/mstf S94w== Original-Received: by 10.60.171.11 with SMTP id aq11mr34575157oec.104.1357612142960; Mon, 07 Jan 2013 18:29:02 -0800 (PST) Original-Received: by 10.76.141.161 with HTTP; Mon, 7 Jan 2013 18:29:02 -0800 (PST) In-Reply-To: <18633CB6-56BF-400C-87D0-8F6D5250942C@gmail.com> X-Gm-Message-State: ALoCoQmVIKgweF+LtAq34uL/cFy9qGpjcKqrEGLgf8PJYQ+LFKxk/vnbHaVFX3FUCRbJWDyvUPor X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.214.180 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:156130 Archived-At: --bcaec54d3ed2861efa04d2bdb550 Content-Type: text/plain; charset=ISO-8859-1 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 wrote: > On Jan 7, 2013, at 6:36 PM, Harald Hanche-Olsen > 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 > --bcaec54d3ed2861efa04d2bdb550 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I see somewhat similar behavior as well. =A0I thought it m= ight be related to autosave but have no verification yet. =A0I did confirm = the behavior using emacs -q and will gladly go after the problem with gdb b= ut I would very much appreciate some suggestions. =A0I rebuilt twice in the= past week using the latest bazaar changes and saw the behavior in both bui= lds. =A0My previous build is about 3 months old and does not show the bad b= ehavior, fwiw.

-pmr


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

> Once in a while, some frame stops receiving keyboard events. It keeps<= br> > receiving mouse events, so I can move the cursor around and so forth,<= br> > 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. =A0For me the problem "goes away" when I= press a letter. =A0In other words only control or meta (or hyper probably)= keys don't work. When I press a regular letter then it inputs that cha= racter 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 ex= tra data point might be useful. =A0I haven't noticed any clues as to wh= at might cause it, and it's rather rare.

-Ivan

--bcaec54d3ed2861efa04d2bdb550--