From: Keisuke Nishida <knishida@sky.sannet.ne.jp>
To: Chris Beggy <chrisb@kippona.com>
Cc: guile-emacs@sources.redhat.com
Subject: Re: emacs-guile
Date: Fri, 18 Jan 2002 00:05:00 -0000 [thread overview]
Message-ID: <m3lmewxevr.wl@xp.netlab.jp> (raw)
In-Reply-To: <20020117.230602.59069554.chrisb@kippona.com>
At Thu, 17 Jan 2002 23:06:02 -0500 (EST),
Chris Beggy wrote:
>
> Do we have any capability to do something like C-h f <scheme
> function> to learn about the scheme functions in the imported
> library? Do we have to worry about collision with elisp symbols?
If you are only interested in docstrings of Scheme procedures,
try guile-scheme-mode and type `C-c C-d' (guile-scheme-describe).
Or if you want to import Scheme procedures with their docstrings,
call `guile-import' with option `:with-docs'. You can specify
the imported symbol by the second argument of `guile-import':
(guile-import assq guile-assq :with-docs)
(documentation 'guile-assq) =>
" - Scheme Procedure: assq key alist
- Scheme Procedure: assv key alist
- Scheme Procedure: assoc key alist
Fetch the entry in ALIST that is associated with KEY. To decide
whether the argument KEY matches a particular entry in ALIST,
`assq' compares keys with `eq?', `assv' uses `eqv?' and `assoc'
uses `equal?'. If KEY cannot be found in ALIST (according to
whichever equality predicate is in use), then return `#f'. These
functions return the entire alist entry found (i.e. both the key
and the value)."
See the README file for (a little bit) more information.
Keisuke
prev parent reply other threads:[~2002-01-18 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 14:25 emacs-guile Chris Beggy
2002-01-17 15:08 ` emacs-guile Keisuke Nishida
2002-01-17 15:23 ` emacs-guile Chris Beggy
2002-01-17 15:40 ` emacs-guile Keisuke Nishida
2002-01-17 15:55 ` emacs-guile Keisuke Nishida
2002-01-17 20:06 ` emacs-guile Chris Beggy
2002-01-18 0:05 ` Keisuke Nishida [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lmewxevr.wl@xp.netlab.jp \
--to=knishida@sky.sannet.ne.jp \
--cc=chrisb@kippona.com \
--cc=guile-emacs@sources.redhat.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).