From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Andreas_R=F6hler?= Subject: Re: C-c / r key-setting bug (?) Date: Thu, 21 Oct 2010 16:53:26 +0200 Message-ID: <4CC053E6.80504@easy-emacs.de> 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> <89A5A483-D79C-4E93-9CC1-1C6FA8612B51@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from [140.186.70.92] (port=32900 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8wXC-0000s2-8h for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:54:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8wXA-0004qM-Tz for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:54:26 -0400 Received: from moutng.kundenserver.de ([212.227.17.10]:57561) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8wXA-0004pk-HR for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 10:54:24 -0400 In-Reply-To: <89A5A483-D79C-4E93-9CC1-1C6FA8612B51@gmail.com> 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: Carsten Dominik Cc: emacs-orgmode Am 21.10.2010 16:31, schrieb Carsten Dominik: > > On Oct 21, 2010, at 4:11 PM, Andreas Röhler wrote: > >> Am 21.10.2010 16:04, schrieb Carsten Dominik: >>> >>> On Oct 21, 2010, at 3:34 PM, Andreas Röhler wrote: >>> >>>> Am 21.10.2010 15:00, schrieb Carsten Dominik: >>>>> >>>>> On Oct 21, 2010, at 2:42 PM, Andreas Röhler wrote: >>>>> >>>>>> [ ... ] >>>>>>>>> C-c / will prompt for another key and then dispatch depending on >>>>>>>>> that >>>>>>>>> key. >>>>>>>>> Many do. >>>>>>>> >>>>>>>> Hmm, that would fit into the already mentioned coding-style >>>>>>>> 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 number >>>>>>> of full-scale prefix keys. And it is much easier to remember 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, then >>>>>>> you >>>>>>> want to have the real command names. This is one of the reasons >>>>>>> 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 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 the > dispatcher with its friendly prompt etc. > > In fact, I do not want describe-mode to show all these. I have thought > carefully about this. > > - Carsten OK, you are the mastermind :-) There is a bug-report still an-responded. Been sent with mail at 14:42 Missing org-occur, no key displayed as expected. Andreas