emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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-u usage
Date: Tue, 17 Aug 2010 13:55:35 +0200	[thread overview]
Message-ID: <494020DD-B763-4F38-B221-DE126BAA2679@gmail.com> (raw)
In-Reply-To: <4C6A554F.4030009@easy-emacs.de>

Hi Andreas,

On Aug 17, 2010, at 11:24 AM, Andreas Röhler wrote:

>
> Hi Carsten,
>
> while dealing with the key/command-name issue,
> thanks for the last hint BTW, works now,
>
> stumble over
>
> C-u C-u C-u <TAB>
>
> Don't it break common Emacs usage somehow?

No, it is customary that C-u changes the behavior as a function.
Admittedly Org does this more extensively than other programs.

>
> The problem arises, as C-h k does not report a
> combination starting with C-u...

Yes, for your command name listing this is a problem.

Two cases

1. Using prefix arguments actually internally calls a different command.
    Then one can try to find this command, and if it can be called in a
    stand-alone way, it would actually be useful to give this indirect  
command
    in the list

2. The prefix argument just modified the command a bit - here I think
    we have no choice but to repeat the command name as it was given  
for the
    un-prefixed call.  Normally one would in fact describe the effect  
of the
    prefix arg in the description of the un-prefixed command.  But  
sometimes
    I have found it useful to list the prefixed call explicitly.

HTH

- Carsten

>
> Just for consideration.
>
> Andreas

- Carsten

      parent reply	other threads:[~2010-08-17 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  9:24 C-u usage Andreas Röhler
2010-08-17  9:51 ` Tassilo Horn
2010-08-17 11:55 ` Carsten Dominik [this message]

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=494020DD-B763-4F38-B221-DE126BAA2679@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).