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: Why bring new features to Emacs and not Emacs to new applications? Date: Mon, 25 Nov 2013 22:14:32 +0100 Message-ID: References: <8761rhv7kc.fsf@informatimago.com> <87pppptlpu.fsf@informatimago.com> <878uwctf4z.fsf@informatimago.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1385414108 2649 80.91.229.3 (25 Nov 2013 21:15:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Nov 2013 21:15:08 +0000 (UTC) Cc: Emacs-Devel devel To: "Pascal J. Bourguignon" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 25 22:15:14 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 1Vl3Uv-0001WN-KJ for ged-emacs-devel@m.gmane.org; Mon, 25 Nov 2013 22:15:13 +0100 Original-Received: from localhost ([::1]:55089 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vl3Uu-00089s-TM for ged-emacs-devel@m.gmane.org; Mon, 25 Nov 2013 16:15:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vl3Uq-00083o-47 for emacs-devel@gnu.org; Mon, 25 Nov 2013 16:15:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vl3Um-0003dC-80 for emacs-devel@gnu.org; Mon, 25 Nov 2013 16:15:08 -0500 Original-Received: from mail-wi0-x233.google.com ([2a00:1450:400c:c05::233]:55898) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vl3Um-0003Z7-12 for emacs-devel@gnu.org; Mon, 25 Nov 2013 16:15:04 -0500 Original-Received: by mail-wi0-f179.google.com with SMTP id ez12so6137587wid.12 for ; Mon, 25 Nov 2013 13:15:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xFz9R84WlMGQeH1EzMumNlyrXRuX2JREiBYiUDZ22MY=; b=Jod7sSpqG3Iq3LXWFSmeiOe87qdS4BadQZHBQFPvcq4waWJq3SXLWqiNmWkBGrww3o c0WNi9Yw+qavgUd83KE7Xr3nEInSYsJiKWVRXran5i6AA+9Gi+M6QGoCRzBZiSs+HhqH r1j5IHKAsLSBvo0FmqhHDZT8uACRkjNDxaBWucjwdCAwz9BiSpaznXNtD+1F+rNNMqJS +ycXdO8FZJmfhRaQPz4/xU9dmd+RaceXdeMls69IR6iyx2aF5af/qVrnE1qXzn216gn+ t0Uc6IPnrkmp+t4L6vNv+gbeQkTur4BIp2GwtuXKu0QWSnEK8nIeEe+M8Du14TbkQPXa 6jqg== X-Received: by 10.194.78.141 with SMTP id b13mr7254110wjx.32.1385414102713; Mon, 25 Nov 2013 13:15:02 -0800 (PST) Original-Received: by 10.194.216.227 with HTTP; Mon, 25 Nov 2013 13:14:32 -0800 (PST) In-Reply-To: <878uwctf4z.fsf@informatimago.com> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::233 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:165725 Archived-At: On Mon, Nov 25, 2013 at 9:12 PM, Pascal J. Bourguignon wrote: > Lennart Borgman writes: > >> On Mon, Nov 25, 2013 at 12:37 AM, Pascal J. Bourguignon >> wrote: >>> >>>>> - incompatible control structure. >>>>> >>>>> While most applications will have like emacs a main event loop, it is >>>>> not designed usually to go thru (dynamically modifiable) keymaps to >>>>> handle in a uniform way the events, but would rather rely on >>>>> frameworks, which may implement their own modal control loops. >>>> >>>> Isn't this an area where Emacs must change? >>> >>> On the contrary, this is the essence of what an emacs is. >> >> I think we are misunderstanding each other. There are all sort of >> events that must be handled. Isn't there loops inside the keyboard >> handling now? (Or, do I misremember?) > > Not really. There's function like read-from-minibuffer, but they're > called explicitely by the commands that are called when receiving > commands asking for minibuffer input, like M-x = > execute-extended-command. I meant on a lower level in the C code, but I do not remember the details any more.