unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@MIT.EDU>
To: Kelly Dean <kellydeanch@yahoo.com>
Cc: "emacs-devel@gnu.org devel" <emacs-devel@gnu.org>
Subject: Re: [PATCH] Unify fn and var help to make learning elisp a little easier
Date: Fri, 7 Dec 2012 10:30:34 -0800	[thread overview]
Message-ID: <41CC575D-91E9-4967-8CC9-F622631F4F05@mit.edu> (raw)
In-Reply-To: <1354903977.95634.YahooMailClassic@web141102.mail.bf1.yahoo.com>

On 07 Dec 2012, at 10:12, Kelly Dean <kellydeanch@yahoo.com> wrote:

>> Actually, there is already a function for that, called
>> `help-xref-interned', so all we need is to give it a nicer
>> name
>> (e.g. describe-symbol), and an `interactive' spec which
>> provides completion.
> That's what my patch does.

FWIW, when faced with a similar issue long ago, I did something like
this:

	;; add apropos to Help
	(define-key help-map "A" 'apropos)

Actually, I rebind `a' to apropos and bind `A' to apropos-command, but
I doubt Emacs wants that change by default. Neither of these gets
completion, if that's important to you. At the time, I liked the word list
well enough that I didn't miss completion, but that was before things
like ido, icomplete, and anything/company/helm/etc were so common.

Hope that helps,
~Chad






  reply	other threads:[~2012-12-07 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 18:59 [PATCH] Unify fn and var help to make learning elisp a little easier Kelly Dean
2012-12-07  2:09 ` Stefan Monnier
2012-12-07 18:12   ` Kelly Dean
2012-12-07 18:30     ` chad [this message]
2012-12-07 18:50     ` Stefan Monnier
2012-12-07 19:32       ` [PATCH] Unify fn and var help to make learning elisp a littleeasier Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2012-12-08 19:19 [PATCH] Unify fn and var help to make learning elisp a little easier Kelly Dean
2012-12-22 21:20 ` Dmitry Gutov
2012-12-22 21:43   ` Glenn Morris
2012-12-23 14:35   ` Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41CC575D-91E9-4967-8CC9-F622631F4F05@mit.edu \
    --to=yandros@mit.edu \
    --cc=emacs-devel@gnu.org \
    --cc=kellydeanch@yahoo.com \
    /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.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).