unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
Subject: Re: is there C-h help for a "require" feature?
Date: Sat, 28 Sep 2002 19:54:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209281953040.15147-100000@dell> (raw)
In-Reply-To: <87d6qxity7.fsf@shadizar.dyndns.org>

On Sat, 28 Sep 2002, Michael J. Barillier wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >>>>> "rd" == Robert P J Day <rpjday@mindspring.com> writes:
> 
>     rd>   looking at someone else's elisp load file, and for the line
>     rd> (require 'cl), is there any C-h help for "cl"?  given that
>     rd> it's not a function or variable, is there another C-h key
>     rd> sequence that would give help for that, perhaps from embedded
>     rd> documentation in the corresponding file?
> 
> `(require 'cl)' makes sure cl.el (Common Lisp-like functions) are
> loaded.  `cl' is just a symbol, and if it's not in the `features' list
> then the corresponding file is loaded.

that part i had pretty much figured out.

> Are you looking for some
> method of attaching per-file documentation?  Sounds like a slick idea,
> but not supported by the current `require'/`provide' mechanism

that's what i was asking about, kind of like the DOCSTRING part of
a "defvar".  ah well, it was a shot in the dark.

rday

  reply	other threads:[~2002-09-28 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 17:31 is there C-h help for a "require" feature? Robert P. J. Day
2002-09-28 23:18 ` Michael J. Barillier
2002-09-28 23:54   ` Robert P. J. Day [this message]
     [not found] <mailman.1033234465.16189.help-gnu-emacs@gnu.org>
2002-09-28 17:55 ` Jesper Harder
     [not found] <mailman.1033257451.14053.help-gnu-emacs@gnu.org>
2002-09-29 21:35 ` Stefan Monnier <foo@acm.com>

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=Pine.LNX.4.44.0209281953040.15147-100000@dell \
    --to=rpjday@mindspring.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.
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).