From: William Xu <william.xwl@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: help-fns.el patch for commands to describe options and commands
Date: Sun, 21 Oct 2007 14:25:04 +0900 [thread overview]
Message-ID: <m2wsthghu7.fsf@gmail.com> (raw)
In-Reply-To: jwvmyudte2p.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Yes. When you are looking for a command, you don't want to see a zillion
>> non-interactive functions as candidates. This cuts down that noise
>> *considerably*.
>
> I could buy that. But those users for whom it matters most won't know to
> use the C-u prefix. And usually the C-u prefix means something like "give
> me more control", so it would make more sense to only list commands/options
> and let C-u specify that we actually want to see all functions/variables.
I like Drew's idea. But if i have to C-u everytime to see all
functions/variables, then it would be a great pain writing elisps..
On the contrary, C-u is not friendly to newbies. So maybe a better
solution is to add/redefine two new bindings, `C-h c' and `C-h o' for
commands and options, respectively. [Currently `C-h c' is binded to
describe-key-briefly, which i find myself nearly never use..]
--
William
http://williamxu.net9.org
next prev parent reply other threads:[~2007-10-21 5:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 19:06 help-fns.el patch for commands to describe options and commands Drew Adams
2007-10-20 1:46 ` Miles Bader
2007-10-20 14:57 ` Richard Stallman
2007-10-20 16:59 ` Drew Adams
2007-10-21 2:09 ` Stefan Monnier
2007-10-21 2:22 ` Drew Adams
2007-10-21 2:46 ` Miles Bader
2007-10-21 2:57 ` Drew Adams
2007-10-21 16:26 ` Richard Stallman
2007-10-21 5:25 ` William Xu [this message]
2007-10-21 6:02 ` Drew Adams
2007-10-22 9:00 ` Richard Stallman
2007-10-22 9:15 ` William Xu
2007-10-21 16:26 ` Richard Stallman
2007-10-21 17:30 ` Drew Adams
2007-10-23 7:12 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wsthghu7.fsf@gmail.com \
--to=william.xwl@gmail.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.