public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: scheme-describe-symbol
Date: Sat, 29 Apr 2000 12:42:00 -0000	[thread overview]
Message-ID: <m37ldgg0cw.fsf@kei.cwru.edu> (raw)
In-Reply-To: <877ldgrc8y.fsf@PC486.Niemitalo.LAN>

Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:

> OW!  I spent the last few hours implementing a generic
> `describe-object' with methods for procedures, macros and generic
> functions... until I noticed GOOPS has had the functionality all
> the time:

> I guess I'll use that instead... except `describe' doesn't show
> documentation strings.  What would be the best way to add them?

I think we'd better modify the file goops/describe.scm so that it
merges ice-9/doc.scm, though I'm not sure if GOOPS supports docstrings.
Once `describe' comes to display enough information, we can redirect
the output to the Emacs buffer.

Maybe we should discuss this part in the guile mailing list.

      reply	other threads:[~2000-04-29 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-29  1:25 scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29  2:12 ` scheme-describe-symbol Keisuke Nishida
2000-04-29 11:37   ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29 12:22     ` scheme-describe-symbol Keisuke Nishida
2000-04-30  6:57       ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-05-01 18:16         ` scheme-describe-symbol Keisuke Nishida
2000-04-29 11:37   ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29 12:42     ` 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=m37ldgg0cw.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.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).