From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: C-c / r key-setting bug (?)
Date: Thu, 21 Oct 2010 16:11:39 +0200 [thread overview]
Message-ID: <4CC04A1B.2020109@easy-emacs.de> (raw)
In-Reply-To: <8ED23E58-3FA8-4785-9352-4072D3F2621C@gmail.com>
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?
Andreas
next prev parent reply other threads:[~2010-10-21 14:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 10:37 C-c / r key-setting bug (?) Andreas Röhler
2010-10-21 10:51 ` Carsten Dominik
2010-10-21 11:44 ` Andreas Röhler
2010-10-21 11:52 ` Carsten Dominik
2010-10-21 12:42 ` Andreas Röhler
2010-10-21 13:00 ` Carsten Dominik
2010-10-21 13:34 ` Andreas Röhler
2010-10-21 14:04 ` Carsten Dominik
2010-10-21 14:11 ` Andreas Röhler [this message]
2010-10-21 14:31 ` Carsten Dominik
2010-10-21 14:53 ` Andreas Röhler
2010-10-21 15:33 ` Jambunathan K
2010-10-21 16:36 ` Andreas Röhler
2010-10-21 20:50 ` Carsten Dominik
2010-10-22 7:40 ` Andreas Röhler
2010-10-22 7:49 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CC04A1B.2020109@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).