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: Physical keyboard events Date: Mon, 04 Nov 2024 18:49:41 +0200 Message-ID: <865xp3ueoq.fsf@gnu.org> References: <31bdc55d-8c13-4de0-9cef-bd6cc4fb033f@imayhem.com> <19ab52d0-88bd-4378-8fa8-8603e01233e3@imayhem.com> <871pzrl4sn.fsf@yahoo.com> <86ldxzuohg.fsf@gnu.org> <877c9jjc93.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24389"; mail-complaints-to="usenet@ciao.gmane.io" Cc: cpardo@imayhem.com, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 04 17:50:09 2024 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 1t80HH-0006AQ-Qm for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Nov 2024 17:50:07 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t80Gv-0003dk-B4; Mon, 04 Nov 2024 11:49:45 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t80Gu-0003dV-I2 for emacs-devel@gnu.org; Mon, 04 Nov 2024 11:49:44 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t80Gu-00049w-5G; Mon, 04 Nov 2024 11:49:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=TfY6+GWnNoXrY8bvgoxEKi+fwQ3ydSgdb1RcYRKlKDA=; b=l0YJlyyWDkxI E8XHfr7oMPjLFHwqdsyTxM4fMIXZpCdN1ZhMZgk5VAQNG+WpSHdl74BYhpylBBuE9CqzQfEqYnp4v lE80zH5GCcupepvHDHxHhqHxcud3aawKxMQfO8kzkw2wCRCy36FeQ2FIcBZI3hD1KST7UysJV0/OU nYPG2nZcrcLsbbUqOZYDdKTOwl2KkgtehhW04HvMsc97A2JcJ9rDPjxZMuDJGYfCBqARmBomJ3xmU ZSMfN6L8G/Ul/VWuz6ZCrAkV1R9AG9RJkzGEa5evhI4n24INa7f9ptZkO84mYtk3DBBir5wQucMP8 EdmKa88taQsYXnRlv3A0vQ==; In-Reply-To: <877c9jjc93.fsf@yahoo.com> (message from Po Lu on Mon, 04 Nov 2024 22:37:44 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325109 Archived-At: > From: Po Lu > Cc: cpardo@imayhem.com, emacs-devel@gnu.org > Date: Mon, 04 Nov 2024 22:37:44 +0800 > > Emacs already tries to establish a sensible relationship between > modifier bits and Emacs modifiers, and clearly, the reasonable way > forward is to write a small quantity of code to deduce the modifier bits > produced by a keysym, and reuse the existing mechanism to report a > modifier that users will expect, instead of engineering a different > mechanism for the purposes of reporting modifier activation and > deactivation, or, as Cecilio's patch currently does, reporting keysyms > totally independent of the modifiers actually bound to their keys. I can see a place for both. It all depends on what the Lisp program wants to do. So I guess we should allow Lisp programs to receive one or the other. > >> BTW, if the intention is to forward just modifier key events to Lisp, > >> don't let's refer to them as "physical keyboard events", but in more > >> specific terms. > > > > Yes, I think the idea is to generate modifier key events and expose > > them to Lisp. What is more specific than "physical keyboard events"? > > "Modifier activation and release events", perhaps? That's a mouthful. How about "low-level keyboard events"?