unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kelly Dean <kellydeanch@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Unify fn and var help to make learning elisp a little easier
Date: Fri, 07 Dec 2012 13:50:26 -0500	[thread overview]
Message-ID: <jwvk3stg0tr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1354903977.95634.YahooMailClassic@web141102.mail.bf1.yahoo.com> (Kelly Dean's message of "Fri, 7 Dec 2012 10:12:57 -0800 (PST)")

>> 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.

Duh, sorry!  Your patch is a lot better than "a simple union of
describe-function and describe-variable to do this".  I was fooled by
your humility.

The patch looks pretty good, actually.  I'm not completely sure we want
to use "C-h o" for its binding, tho I don't see any obvious reasons
not to.

But now we have the reverse problem that this goes beyond the "tiny
change" limit, so we'd need you to sign some copyright paperwork before
we can accept it.  Would you be willing to do that?


        Stefan



  parent reply	other threads:[~2012-12-07 18:50 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
2012-12-07 18:50     ` Stefan Monnier [this message]
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=jwvk3stg0tr.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).