From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: What happened to the key-menu patch? Date: 10 Jul 2002 11:43:55 +0900 Sender: emacs-devel-admin@gnu.org Message-ID: References: <200205050534.g455YfF01634@aztec.santafe.edu> <5xbsbumexh.fsf@kfs2.cua.dk> <200205141941.g4EJfud15293@aztec.santafe.edu> <5xvg9qmgzt.fsf@kfs2.cua.dk> <200205151927.g4FJRRW26103@rum.cs.yale.edu> <5x3cwr4q7m.fsf@kfs2.cua.dk> <87g00rd74y.fsf@tc-1-100.kawasaki.gol.ne.jp> <87sn4otknt.fsf@tc-1-100.kawasaki.gol.ne.jp> <200205191441.g4JEfMg23080@rum.cs.yale.edu> <200205202134.g4KLYHj26031@aztec.santafe.edu> <200205222227.g4MMRIX29393@aztec.santafe.edu> <87g0030xah.fsf@tc-1-100.kawasaki.gol.ne.jp> <5xn0t3p362.fsf_-_@kfs2.cua.dk> <200207091358.g69Dwlr26999@rum.cs.yale.edu> Reply-To: Miles Bader NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1026269143 23426 127.0.0.1 (10 Jul 2002 02:45:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 10 Jul 2002 02:45:43 +0000 (UTC) Cc: storm@cua.dk (Kim F. Storm), rms@gnu.org, monnier+gnu/emacs@RUM.cs.yale.edu, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17S7U7-00065j-00 for ; Wed, 10 Jul 2002 04:45:43 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17S7co-0005bI-00 for ; Wed, 10 Jul 2002 04:54:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17S7UZ-0002cy-00; Tue, 09 Jul 2002 22:46:11 -0400 Original-Received: from tyo201.gate.nec.co.jp ([202.32.8.214]) by fencepost.gnu.org with smtp (Exim 3.35 #1 (Debian)) id 17S7TY-0002bh-00; Tue, 09 Jul 2002 22:45:09 -0400 Original-Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id g6A2idR03284; Wed, 10 Jul 2002 11:44:40 +0900 (JST) Original-Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id g6A2ico21947; Wed, 10 Jul 2002 11:44:38 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp ([10.30.114.133]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id g6A2i0N24339; Wed, 10 Jul 2002 11:44:14 +0900 (JST) Original-Received: from mcspd15.ucom.lsi.nec.co.jp (mcspd15 [10.30.114.174]) by mcsss2.ucom.lsi.nec.co.jp (8.10.2+Sun/3.7Wlsi_mx_6.0) with ESMTP id g6A2htK22042; Wed, 10 Jul 2002 11:43:55 +0900 (JST) Original-Received: by mcspd15.ucom.lsi.nec.co.jp (Postfix, from userid 31295) id B964C37D5; Wed, 10 Jul 2002 11:43:55 +0900 (JST) Original-To: "Stefan Monnier" System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: <200207091358.g69Dwlr26999@rum.cs.yale.edu> Original-Lines: 51 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5618 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5618 "Stefan Monnier" writes: > > sure if it's worth it to add a `dobindings' macro or not. > > Agreed. There's already a `loop' macro for it in CL. Yeah, but we don't really like cl in emacs, remember? Oh wait, you do. > > key-description list' is, but it's something like (meta control x). > > I guess this is a canonical format for key names in xemacs, but it > > doesn't appear to be so in emacs, so I'm not sure how that argument > > should be handled (perhaps just punt, and pass whatever's stored in > > the keymap). > > I don't think we should try to re-create the XEmacs (meta control x) form > from our M-C-x symbols. We could provide an additional compatibility layer > on top of it, if it proves useful/necessary later on. So, just pass whatever's stored in the keymap directly? > > (2) How are menu entries handled with this? > > As for how we should treat them, I think we should not do anything > special with them: i.e. `function' will be called with key `menu-bar' > and with the corresponding sub-keymap as the binding. That would be consistent with `lookup-key', but it also throws out a bunch of useful information for menu-entries -- in particular, the very information that I want for the key-menus! How about just passing something similar to the corresponding arguments to define-key, e.g., for keys, `function' would be the function, but for menu-entries, it would be the whole (menu-item ...) list. Either way, we have to provide some other sort of function to allow easily going from one form to the other -- if we just pass the function/sub-keymap, there needs to be a way for the user to lookup all the menu-item information, and if we pass the (menu-item...) list directly, there should probably be some access function(s) to make getting at the various pieces cleanly. Perhaps the thing to do is to pass only the function/sub-keymap by default, but have an optional argument that says `pass all menu info for menu-items'; this could possible be combined with Richard's suggestion of having an option to suppress passing menu-items altogether. We could (rather, should) add a similar optional argument to `lookup-key' for conistency and utility. -Miles -- Is it true that nothing can be known? If so how do we know this? -Woody Allen