From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Does a diagram of the key input subsystem exist? Date: Wed, 01 Sep 2021 16:35:42 +0300 Message-ID: <83eea8quz5.fsf@gnu.org> References: <5eef1cbd-e6a0-980f-e3b5-7bfcccf02a53@piermont.com> <83zgsxqb7n.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4984"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "Perry E. Metzger" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 01 15:36:26 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mLQPi-00012N-4H for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Sep 2021 15:36:26 +0200 Original-Received: from localhost ([::1]:56478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLQPg-00015O-Oy for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Sep 2021 09:36:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52364) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLQP6-0000CG-Ar for emacs-devel@gnu.org; Wed, 01 Sep 2021 09:35:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49296) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLQP6-0004uS-35; Wed, 01 Sep 2021 09:35:48 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2561 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLQP5-0000q7-MJ; Wed, 01 Sep 2021 09:35:48 -0400 In-Reply-To: (perry@piermont.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273658 Archived-At: > Date: Wed, 1 Sep 2021 08:44:07 -0400 > Cc: emacs-devel@gnu.org > From: "Perry E. Metzger" > > On 8/31/21 22:30, Eli Zaretskii wrote: > >> Is there anything like a document or diagram that lists the steps, > >> translation tables, maps, etc. that every keystroke goes through in its > >> journey? My guess is no, but I thought I would ask. > > You mean, the description of what the read_char does? > > > read_char is only a portion of the overall processing path, but a > description of read_char would definitely need to be part of such a thing. So what else, in addition to read_char, are you interested in? maybe if you'd ask more specific question, we could answer some of them. To answer your question: the only documentation of this I know of is in the Command Loop chapter of the ELisp manual. Some more is in large comments in keyboard.c. I think we do understand the overall picture, and could describe it (which it would perhaps then make sense to put the description into the comments in keyboard.c), but only on a high enough level, disregarding low-level details. You'd need to read the code to find out the rest.