[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
patch for where-is
From: |
Drew Adams |
Subject: |
patch for where-is |
Date: |
Tue, 26 Feb 2008 20:06:17 -0800 |
Attached is a patch for `where-is' (help.el), in case people find it useful.
Currently:
* All commands are completion candidates. If you choose a command that is in
fact not bound to any key in the currently active keymaps, then the result
is a message saying that it is not bound.
* A prefix argument inserts the message in the current buffer instead of the
minibuffer.
In the patched definition:
* By default, only commands that are bound to a key are completion
candidates.
* A plain prefix argument, C-u, acts the same as before. It inserts the
message in the current buffer. And all commands are candidates.
* A numeric argument, e.g. C-9 or M--, acts as before without a prefix arg:
all commands are completion candidates.
Argument:
* Completion is simplified by reducing the number of interesting candidates.
No sense (most of the time) asking for the binding of command that is not
bound.
* *Completions* shows you immediately all of the bound commands that match
your current input - and only the bound commands. This gives you an overview
of what's pertinent in the current context, since important commands are
often bound.
* In that case, why bother to allow the old behavior at all (via a numeric
arg)? Because you sometimes do want to use `C-h w' to see if a command is
bound in the current context. This is not the default behavior, because
people use `where-is' less frequently just to see if a command is bound.
help-2008-02-26.patch
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- patch for where-is,
Drew Adams <=