From: Juanma Barranquero <lekktu@gmail.com>
To: MON KEY <monkey@sandpframing.com>
Cc: 6756-done@debbugs.gnu.org
Subject: bug#6756: 23.2; `describe-function' describing functions that aren't
Date: Sat, 31 Jul 2010 14:05:14 +0200 [thread overview]
Message-ID: <AANLkTikDMHH=v60D4eGgDpa6mTf778JobjsupEZOoxdt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin3agupACMzX2x2Y=M9uzNjRD9jak=x89JuKdG0@mail.gmail.com>
On Sat, Jul 31, 2010 at 04:50, MON KEY <monkey@sandpframing.com> wrote:
> It would be working as expected assuming I could ascertain _what_ to
> expect.
I agree that completion is complex and perhaps underdocumented.
> FWIW I increasingly find it unreasonable that *Help* defaults to
> _just_ pointing the user to `customize'.
I haven't noticed that. I share your opinion on Customize, though.
> It isn't all that helpful that *Help* seems to increasingly
> (implicitly) suggest dropping into *Info* or custom to get help.
I think suggesting to read Info is reasonable. It does not make much
sense to duplicate in docstrings all the information already available
on the Info pages.
I'm closing this bug, as it is no longer about describe-function
failing. Feel free to file bugs about documentation shortcomings, etc.
Juanma
prev parent reply other threads:[~2010-07-31 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 17:22 bug#6756: 23.2; `describe-function' describing functions that aren't MON KEY
2010-07-29 22:55 ` Juanma Barranquero
2010-07-31 2:50 ` MON KEY
2010-07-31 12:05 ` Juanma Barranquero [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.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='AANLkTikDMHH=v60D4eGgDpa6mTf778JobjsupEZOoxdt@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=6756-done@debbugs.gnu.org \
--cc=monkey@sandpframing.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).