From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Request: Specification For Denoting Keys Date: Tue, 06 Oct 2020 11:10:52 -0400 Message-ID: References: <83k0w3c1er.fsf@gnu.org> <24444.33059.201129.378700@retriever.mtv.corp.google.com> <24444.34728.646398.923214@retriever.mtv.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1064"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: eliz@gnu.org, emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 06 17:12:29 2020 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 1kPodh-0000C1-Lt for ged-emacs-devel@m.gmane-mx.org; Tue, 06 Oct 2020 17:12:29 +0200 Original-Received: from localhost ([::1]:60124 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kPodg-0003ly-Ol for ged-emacs-devel@m.gmane-mx.org; Tue, 06 Oct 2020 11:12:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39310) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPocE-0002uM-KW for emacs-devel@gnu.org; Tue, 06 Oct 2020 11:10:58 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:15198) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPocC-0003Pu-Ef; Tue, 06 Oct 2020 11:10:58 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id C338B10023C; Tue, 6 Oct 2020 11:10:54 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 3BA4010006F; Tue, 6 Oct 2020 11:10:53 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1601997053; bh=85Z4D39yzNo0mpC/XWyK8qoeXpHlXlQFfnb6mVs9Ewk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=YfDotdRZsfu0MjT2E8J3gfwuZ5DCF0acUYeWXbKLeXFhkq3aS84x1Mw9bHp6ZB1bn wSpwQm9oo69DvAk5dP+uCFHcwuFtTmOMU61MkQaZSb5DTVhqKztfYLkQH/Md1lp3FD VJjQTgxMIMsHzgJK1T2geqv3qpt2uNZ64n446Ppzd9DdEWRWGhMa4Fe1/iErW95LjD Gu1BZxFhNIZ7E4FmvtLWm6easKYDdeE1SCYqFYfP/9l0ADcmJh6TMDWI4j5Ru13bpw rx3MnzE2wTKkNyGsUQfgaY81IhjL5M5I5wp27SbmYtPRkzW4b3Y5NfWhRhXeU+HXH1 e+iODbLGpCOww== Original-Received: from alfajor (unknown [157.52.9.240]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 1656912005C; Tue, 6 Oct 2020 11:10:53 -0400 (EDT) In-Reply-To: <24444.34728.646398.923214@retriever.mtv.corp.google.com> (T. V. Raman's message of "Tue, 6 Oct 2020 08:05:12 -0700") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/06 09:08:42 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:257171 Archived-At: > thx. Because kbd traces back to reading in recorded kbd macros, it > does more than what a function that you use in defining keys need to > do -- look at edmacro-parse-keys to see what I mean by the above. For > instance, kbd handles things like M-x command-name that might have > been invoked while defining or recording a macro. Indeed, that's a historical accident. First came the `edmacro` package and then people started (ab)using its `read-kbd-macro` function for the more simple task of parsing a slightly more human-friendly textual representation of keys sequences than what you get by just using the "raw event vector". Nobody took on the task of separating the two, so that's that. Stefan