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: Wed, 30 Oct 2024 17:27:17 +0200 Message-ID: <86sesd4nmy.fsf@gnu.org> References: <86r07z58or.fsf@gnu.org> <86froe6eq3.fsf@gnu.org> <864j4u6bug.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39334"; mail-complaints-to="usenet@ciao.gmane.io" Cc: manikulin@gmail.com, emacs-devel@gnu.org To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 30 16:27:54 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 1t6Aby-000A6l-6F for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Oct 2024 16:27:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t6AbV-0006Td-1L; Wed, 30 Oct 2024 11:27:25 -0400 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 1t6AbT-0006T1-4k for emacs-devel@gnu.org; Wed, 30 Oct 2024 11:27:23 -0400 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 1t6AbS-0002Ss-Sc; Wed, 30 Oct 2024 11:27:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=FhwSx6T/r+50u7uO27QtoRsYaUHCnMtjBU/oIH1bInE=; b=EOgIm9tnt5BURoc2PTTx ek2lLDkEUUKZBFSrtzAsDfeFic38m/sCNgX803blPFoUJBEwY9E9Y111+gzPfqStMMsvWj/WPBb85 r0jk5+2Zh2Hj9jZ+Qn3URxUFrufk7afmfcodOUyT/VJnWGGsf8qsG8C+lPtO1Wogth6HKL8U7W7oa 5h9Wyg78gpe+jFhlS7ET0xLxBmmHM2j6p56iiD+uYpA17umvUDwgGKlszYX1GLqbjqwkCT2mtllvt 8JTce+bGH5TAhtYzqls4zJcs+V+nwKlsisiEHUia1jBYYEJXoVu7bBLhtBnlaf6ZmARWjhU8wPIEj w747mfgtcYWMHw==; In-Reply-To: (message from Yuri Khan on Wed, 30 Oct 2024 13:28:20 +0700) 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:324943 Archived-At: > From: Yuri Khan > Date: Wed, 30 Oct 2024 13:28:20 +0700 > Cc: emacs-devel@gnu.org > > On Wed, 30 Oct 2024 at 10:22, Max Nikulin wrote: > > > Not *for key with modifiers*, but during lookup in keymaps. There are > > enough keybindings that include keys without modifiers. > > I’m going to posit the hypothesis that the *only* command for which it > makes sense to use the keysym of the current layout is > ‘self-insert-command’. > > Everything else wants the keysym of “the” Latin-based layout if there > is one and only one; the keycode if there is none; and some heuristic > tiebreaker for the case where the user has more than one Latin-based > layout configured. How do you suggest to arrange for a low-level keyboard interface to know which kind of Emacs command attempted to read the keyboard? Moreover, what about type-ahead? When Emacs is busy, the user can type quite a lot of commands, and the keyboard processing cannot know at that point which Emacs commands will actually read those queued keys. IOW, I don't understand how to use your hypothesis, even if it is true, in practice.