From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= Newsgroups: gmane.emacs.devel Subject: Improve input handling documentation (was Re: Best way to intercept terminal escape sequences?) Date: Sat, 04 Sep 2010 15:01:28 +0200 Message-ID: <87bp8dfys7.fsf_-_@gmail.com> References: <20100827142724.E1DD712F@hazard.ece.cmu.edu> <4C77CF3C.6050406@ece.cmu.edu> <834oegm5c3.fsf@gnu.org> <4C78C0AF.5040502@ece.cmu.edu> <4C7D8C45.8060500@ece.cmu.edu> <4C7F99A0.4090502@ece.cmu.edu> 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 1283606427 10988 80.91.229.12 (4 Sep 2010 13:20:27 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 4 Sep 2010 13:20:27 +0000 (UTC) Cc: Eli Zaretskii , Kenichi Handa , Stefan Monnier , emacs-devel@gnu.org To: Ryan Johnson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 04 15:20:25 2010 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 1OrsfP-00072t-Ci for ged-emacs-devel@m.gmane.org; Sat, 04 Sep 2010 15:20:23 +0200 Original-Received: from localhost ([127.0.0.1]:59060 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OrsfO-0006OD-Fb for ged-emacs-devel@m.gmane.org; Sat, 04 Sep 2010 09:20:22 -0400 Original-Received: from [140.186.70.92] (port=58281 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OrsR4-0002cw-BZ for emacs-devel@gnu.org; Sat, 04 Sep 2010 09:05:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OrsNj-0005Oa-VX for emacs-devel@gnu.org; Sat, 04 Sep 2010 09:02:08 -0400 Original-Received: from mail-px0-f169.google.com ([209.85.212.169]:52339) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OrsNi-0005OB-BH; Sat, 04 Sep 2010 09:02:06 -0400 Original-Received: by pxi5 with SMTP id 5so855158pxi.0 for ; Sat, 04 Sep 2010 06:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject :in-reply-to:references:user-agent:date:message-id:mime-version :content-type:content-transfer-encoding; bh=P1OvZt0KidMVDq4wjyOycZld9EDXD9soEFzkS2bPmzE=; b=FT3Qmb3brse7c75X5FbcZHkhRwHYFUApCYxXa2v3sZu8nBTbHrJJK+MZpnJtbG4YnF M1C47YwouR8Axd8yQ14iit7QHR1+4T+LVQrQENeKfvqNpYQfRaOm9rCYaJ9lm+O+c47M LUF0hVv/Tby16rairp0G4vNY4vbjxElSPsofY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type:content-transfer-encoding; b=wXw5dCptxLJtxh15V6P3WZNZ/gXpKigzMidYkMGy7Vtq8MHfQicVlXI0QG9A1wHE7Z 7mUpJJ703+LF4LShW8ncbar0t58cbFmPiHanVxFM0KR74T9h8/0ubBm9zy6vQuc6Nw3R ypI27KgubKqXrkVuf0+qohUBQ0g90y0i3HzEg= Original-Received: by 10.143.9.19 with SMTP id m19mr356869wfi.127.1283605325098; Sat, 04 Sep 2010 06:02:05 -0700 (PDT) Original-Received: from localhost ([88.103.132.186]) by mx.google.com with ESMTPS id q11sm624684wfc.17.2010.09.04.06.02.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Sep 2010 06:02:04 -0700 (PDT) In-Reply-To: <4C7F99A0.4090502@ece.cmu.edu> (Ryan Johnson's message of "Thu, 02 Sep 2010 14:33:36 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) 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:129672 Archived-At: Ryan Johnson writes: [...] > It would be really nice to have, somewhere in the emacs docs, a diagram > showing what processing happens to keyboard input, starting from raw byte= s and > UI events, and tracing them (or their translations) through coding system= s, > input methods, command loop, various keymaps, etc. and showing where in t= hat > process the different read-* functions intercept that data (and where the > various unread-*-events reinsert things). A similar diagram for reading a= nd > writing files would probably also be useful. Sounds great indeed! [...] > Unfortunately, even after spending so long on this problem I don't think I > know enough to generate that diagram... But perhaps you could come up with some initial version that others could continue improving upon? =C5=A0t=C4=9Bp=C3=A1n