[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: C-c / r key-setting bug (?)

From: Andreas Röhler
Subject: [Orgmode] Re: C-c / r key-setting bug (?)
Date: Thu, 21 Oct 2010 13:44:45 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20100711 Thunderbird/3.0.6

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


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?

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


Seeing a contradiction in so far, when the second command is on the top of the first, whose key has been hitten...

Understand: first I must create, to get a show. But can't I have "show" on base of a before created?

I'll proceed anyway...

Thanks being patient :-)


So when there is an entry
for `C-c /', describe it as org-sparse-tree. When it is `C-c / r' you
can leave it as it was, and I will fix it.

- Carsten

reply via email to

[Prev in Thread] Current Thread [Next in Thread]