From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Moving kbd to subr.el Date: Mon, 18 Oct 2021 19:01:05 +0300 Organization: LINKOV.NET Message-ID: <87czo2nzt6.fsf@mail.linkov.net> References: <20211004081724.6281.11798@vcs0.savannah.gnu.org> <834k9km5no.fsf@gnu.org> <83k0iflsze.fsf@gnu.org> <874k9jzu7a.fsf@gnus.org> <874k9juy0r.fsf@gnus.org> <87mtnbtimj.fsf@gnus.org> <87wnmd13ny.fsf@gnus.org> <87sfx10xs6.fsf@gnus.org> <87h7dfpjn3.fsf@gnus.org> <31b2f1e94178d73e5f05@heytings.org> <87czo3pgs1.fsf@gnus.org> <31b2f1e9412d60db82df@heytings.org> <87o87moopl.fsf@gnus.org> <19fca5d18b63e6eff5de@heytings.org> <87wnmaiida.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39743"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: Lars Ingebrigtsen , Gregory Heytings , Emacs developers To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 18 18:31:24 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 1mcVXo-000AAC-89 for ged-emacs-devel@m.gmane-mx.org; Mon, 18 Oct 2021 18:31:24 +0200 Original-Received: from localhost ([::1]:47766 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mcVXm-0007Hn-EP for ged-emacs-devel@m.gmane-mx.org; Mon, 18 Oct 2021 12:31:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33064) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mcVO5-0005sV-Og for emacs-devel@gnu.org; Mon, 18 Oct 2021 12:21:21 -0400 Original-Received: from relay12.mail.gandi.net ([217.70.178.232]:35493) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mcVO3-0007lY-PS for emacs-devel@gnu.org; Mon, 18 Oct 2021 12:21:21 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 25EBF20000B; Mon, 18 Oct 2021 16:21:15 +0000 (UTC) In-Reply-To: (Stefan Kangas's message of "Mon, 18 Oct 2021 15:53:23 +0200") Received-SPF: pass client-ip=217.70.178.232; envelope-from=juri@linkov.net; helo=relay12.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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:277304 Archived-At: > Can't we impose pretty much any syntax we like in new forms, such as > 'defvar-keymap' and 'kbd-valid-p'? > > I'm looking at a fragment like this: > > "P" #'cvs-status-prev > - (kbd "M-n") #'cvs-status-next > - (kbd "M-p") #'cvs-status-prev > + ["M-n"] #'cvs-status-next > + ["M-p"] #'cvs-status-prev > "t" #'cvs-status-cvstrees > > And I feel like it would be nice if we could avoid putting these > strings in a vector. Especially if we don't do it consistently. It would be perfect if new defvar-keymap would use kbd-strict syntax. Then replacing define-key with define-keymap will also replace the string syntax - safely, and as we already discussed allowing old syntax optionally by using a keyword like ':kbd nil'. > At the same time, maybe I don't understand the overreaching plan. Is > the idea to be able to replace any use of (kbd "M-x") with ["M-x"] > everywhere, including in 'define-key' et al? Any use of (kbd "M-x") can't be replaced with ["M-x"]. For example, this use from (info "(elisp) Functions for Key Lookup") (lookup-key (current-global-map) (kbd "C-x C-f")) can't be replaced with: (lookup-key (current-global-map) ["C-x C-f"])