emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 13:44:45 +0200	[thread overview]
Message-ID: <4CC027AD.5010902@easy-emacs.de> (raw)
In-Reply-To: <DF4AE39E-B636-4629-9BB8-D59CF70494C3@gmail.com>

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?

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 :-)

Andreas


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	other threads:[~2010-10-21 11:45 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 [this message]
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
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=4CC027AD.5010902@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).