From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: C-c / r key-setting bug (?) Date: Thu, 21 Oct 2010 16:31:33 +0200 Message-ID: <89A5A483-D79C-4E93-9CC1-1C6FA8612B51@gmail.com> References: <4CC017E4.8040005@easy-emacs.de> <4CC027AD.5010902@easy-emacs.de> <4CC0354F.8020205@easy-emacs.de> <5AB3A2E2-2ECE-4789-8C20-D3D807B5F55B@gmail.com> <4CC04160.1070506@easy-emacs.de> <8ED23E58-3FA8-4785-9352-4072D3F2621C@gmail.com> <4CC04A1B.2020109@easy-emacs.de> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=48182 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8wB8-0005fq-KP for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:31:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8wB6-0007b1-VX for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:31:38 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:50501) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8wB6-0007ao-P1 for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:31:36 -0400 Received: by eydd26 with SMTP id d26so91922eyd.0 for ; Thu, 21 Oct 2010 07:31:35 -0700 (PDT) In-Reply-To: <4CC04A1B.2020109@easy-emacs.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?ISO-8859-1?Q?Andreas_R=F6hler?= Cc: emacs-orgmode On Oct 21, 2010, at 4:11 PM, Andreas R=F6hler wrote: > Am 21.10.2010 16:04, schrieb Carsten Dominik: >> >> On Oct 21, 2010, at 3:34 PM, Andreas R=F6hler wrote: >> >>> Am 21.10.2010 15:00, schrieb Carsten Dominik: >>>> >>>> On Oct 21, 2010, at 2:42 PM, Andreas R=F6hler wrote: >>>> >>>>> [ ... ] >>>>>>>> C-c / will prompt for another key and then dispatch depending =20= >>>>>>>> on >>>>>>>> that >>>>>>>> key. >>>>>>>> Many do. >>>>>>> >>>>>>> Hmm, that would fit into the already mentioned coding-style =20 >>>>>>> category. >>>>>>> Is it wise to do it that way? >>>>>>> For example M-x describe-mode fails telling about these keys. >>>>>>> Are reasons for this? >>>>>> >>>>>> Yes. There are not enough keys, unless I introduce a larger =20 >>>>>> number >>>>>> of full-scale prefix keys. And it is much easier to remember =20 >>>>>> just `C-c >>>>>> /' and then get a friendly prompt for a number of options. For >>>>>> interactive use, I think this is just perfect. >>>>>> >>>>>> Now, if you want to write programs based on these functions, =20 >>>>>> then you >>>>>> want to have the real command names. This is one of the reasons =20= >>>>>> why I >>>>>> like to have them in the manual, for look up. >>>>>> >>>>> >>>>> Hi, >>>>> >>>>> I'm following, thanks for the explanation. >>>>> Remains a describe-mode bug than (?) >>>> >>>> I would not call it a bug. Describe-mode looks at the key maps, it >>>> cannot look into the functions. >>>> >>> >>> OK, but can't you make it known to the keymap? >> >> No, I cannot. >> >> - Carsten >> >> >> >> > > Ah, we can, I'm sure. > Let's assume you assigned the same keys to different commands. > Somehow Emacs must discriminate the states where the one or the =20 > other are to use. > So let's call these states modes, make a keymap for it, no? Hi Andreas, We could make C-c / a prefix and define the other commands in the keymap of the prefix command. But this would defeat the purpose of =20 the dispatcher with its friendly prompt etc. In fact, I do not want describe-mode to show all these. I have =20 thought carefully about this. - Carsten=