From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: C-c / r key-setting bug (?)
Date: Thu, 21 Oct 2010 13:52:31 +0200 [thread overview]
Message-ID: <C0F31431-9C3C-4A06-B15F-55F9937D9FD7@gmail.com> (raw)
In-Reply-To: <4CC027AD.5010902@easy-emacs.de>
On Oct 21, 2010, at 1:44 PM, Andreas Röhler wrote:
> Am 21.10.2010 12:51, schrieb Carsten Dominik:
>> Hi Andreas,
>>
>> On Oct 21, 2010, at 12:37 PM, Andreas Röhler wrote:
>>
>>>
>>> Hi Carsten,
>>>
>>> key-setting below looks like a bug
>>>
>>> if
>>>
>>> C-c /, org-sparse-tree
>>>
>>> is set, there is no chance calling
>>>
>>> C-c / r
>>>
>>> as the first already matches (?)
>>
>> 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.
>
> Sincerely undecided here, just a question.
>
>
>>
>> To simplify you work, you can just leave these keys unchanged in the
>> manual,and I will take a look at those later.
>
> Remains something to do anyway IMHO.
>
> First a creating command is mentioned, after it says "showing".
>
> @orgcmd{C-c /,org-sparse-tree}
> This prompts for an extra key to select a sparse-tree creating
> command.
>
> ;;;;;;;
>
> @kindex C-c / r
> @item C-c / r
> @vindex org-remove-highlights-with-change
> Occur. Prompts for a regexp and shows a sparse tree with all
> matches. If
In this end, this should simply be
@orgcmd{C-c / r, org-occur}
Because the dispatcher command will call this command after "r" has
been pressed.
But as I said, I can do these indirect calls pretty easily, I know
most of them by heart.
- Carsten
next prev parent reply other threads:[~2010-10-21 11:52 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 [this message]
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
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=C0F31431-9C3C-4A06-B15F-55F9937D9FD7@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=andreas.roehler@easy-emacs.de \
--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).