From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [drew.adams@oracle.com: No doc for cl stuff even after loading cl?]
Date: Wed, 24 May 2006 12:35:06 -0400 [thread overview]
Message-ID: <8764jve5z9.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1Ff6W2-0005gE-Fp@fencepost.gnu.org> (Richard Stallman's message of "Sat, 13 May 2006 22:39:30 -0400")
Richard Stallman <rms@gnu.org> writes:
> I agree that this is a bug. Can someone work on it, then ack?
Having looked into this, I think the only way around the current
behavior would be to have cl.el load all the cl-* libraries instead of
autoloading individual functions (which is Bad), or pasting all the
documentation strings in the cl-* files into cl.el for autoloading
(which is Silly). I don't think this is worth fixing.
> From: "Drew Adams" <drew.adams@oracle.com>
> Subject: No doc for cl stuff even after loading cl?
> To: "Emacs-Pretest-Bug" <emacs-pretest-bug@gnu.org>
>
> emacs -Q
>
> C-h f flet finds no match. Normal
> M-x load-library cl
> C-h f flet then gives this:
>
> flet is an autoloaded Lisp macro in `cl-macs'.
> [Arg list not available until function definition is loaded.]
>
> Not documented.
>
> That doesn't seem right. What's a user to do, chase down the various
> cl libraries (in this case cl-macs.el, presumably) in order to get
> doc?
>
> If a user is asking for doc, we should give it to him/her, instead of
> saying that is not available until the function definition is
> loaded. This looks like Emacs is deliberately being uncooperative,
> making the user jump through hoops to get what s?he asks for. If we
> want to avoid loading large libraries, then perhaps we should split
> off the doc in such cases so we can provide it without loading
> everything.
next prev parent reply other threads:[~2006-05-24 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 2:39 [drew.adams@oracle.com: No doc for cl stuff even after loading cl?] Richard Stallman
2006-05-24 16:35 ` Chong Yidong [this message]
2006-05-24 17:35 ` Stefan Monnier
2006-05-25 0:37 ` Richard Stallman
2006-05-29 9:09 ` Stefan Monnier
2007-06-27 19:19 ` Stefan Monnier
2007-06-27 19:52 ` Juanma Barranquero
2007-06-28 15:12 ` Stefan Monnier
2007-06-28 15:45 ` Juanma Barranquero
2007-06-27 23:42 ` 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=8764jve5z9.fsf@stupidchicken.com \
--to=cyd@stupidchicken.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.