From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Bikeshedding go! Why is unbound? Date: Mon, 17 Jan 2011 13:23:48 +0100 Message-ID: References: <4D3430B2.20604@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1295267069 9947 80.91.229.12 (17 Jan 2011 12:24:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 17 Jan 2011 12:24:29 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 17 13:24:25 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Peo8E-0006pz-6m for ged-emacs-devel@m.gmane.org; Mon, 17 Jan 2011 13:24:22 +0100 Original-Received: from localhost ([127.0.0.1]:44432 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Peo8D-00049F-Hd for ged-emacs-devel@m.gmane.org; Mon, 17 Jan 2011 07:24:21 -0500 Original-Received: from [140.186.70.92] (port=44647 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Peo83-000496-5U for emacs-devel@gnu.org; Mon, 17 Jan 2011 07:24:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Peo81-0007rO-KY for emacs-devel@gnu.org; Mon, 17 Jan 2011 07:24:11 -0500 Original-Received: from mail-ew0-f41.google.com ([209.85.215.41]:44317) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Peo81-0007rE-Es for emacs-devel@gnu.org; Mon, 17 Jan 2011 07:24:09 -0500 Original-Received: by ewy27 with SMTP id 27so2349635ewy.0 for ; Mon, 17 Jan 2011 04:24:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Yne772JtmDKBGzUNJg88nN5txEFSMNVRpJi3kIfBzXo=; b=nQUgxtZzPpNwZ2m49ZYqD7VsgzULFyt3OyuV7Oumu5e1HYIIorAqIBpvEwFgM4isP0 0JlxvnbjulkvyV2a8/D6nzyo77u7XBsL9g4wR4gruIGZMC8py+1ybPayFHLl/RYHNIOn hs3/vJCzJ8mhK3wWCSWjeIswn6RBXjkP8GBjw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=BKf9oq3QMnebF0lUJRQNfTfQEp0gikh5/vpwKKGz4s+3QdI6ivEtCRsWyHy6t7enSk yIOLoUlOQy4uDS7ij+gNPxjg7deD9vTav6Eb4J61Ld1mXtKUj5tSdPTb46hWjm58TDUI aeisyX2nycQALHxpnKVJEc73fJZX8jz8W9kXo= Original-Received: by 10.213.28.147 with SMTP id m19mr2571339ebc.97.1295267048584; Mon, 17 Jan 2011 04:24:08 -0800 (PST) Original-Received: by 10.213.20.148 with HTTP; Mon, 17 Jan 2011 04:23:48 -0800 (PST) In-Reply-To: <4D3430B2.20604@gmx.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:134642 Archived-At: On Mon, Jan 17, 2011 at 1:06 PM, grischka wrote: >> What I really hoped to discuss where the technical difficulties. Emacs >> does not currently have a way to let key binding fall back to the OS >> binding. I am not sure it is trivial and I have forgotten the details. > > It is nontrivial to say the least. > > Unlike XEmacs, GNU Emacs is still a console application at its heart. > It wants to "read" events in a loop from an input stream until it > finds them complete as a "key-sequence". =C2=A0No function seems to exist > that could deal with events that are already read. > > So I guess at first you'd need to convert keyboard.c:read_key_sequence() > from procedural logic into a state machine such that it does not call > 'read_key()' on its own but instead can be fed with keys one by one. > Once you have that however you can as well run the Windows backend in > the same thread and many things become much simpler ;) The main problem is the state of the default windows message loop. I think you can overcome that problem using the accessibility API:s but I do not know the details about that any more.