unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@adelphia.net>
Cc: guile-user@gnu.org
Subject: Re: docstrings and snarfing
Date: Sat, 15 Jul 2006 14:21:00 -0400	[thread overview]
Message-ID: <8255671.1152987660797.JavaMail.root@web23> (raw)

---- Kevin Ryde <user42@zip.com.au> wrote: 
> "Dave Griffiths" <dave@pawfal.org> writes:
> >
> > I tried running the example through the C preprocessor, and it seems
> > the docstring is lost anyway:
> 
> There's some magic with a "-DSCM_MAGIC_SNARF_DOCS" to get them, then
> the scripts/snarf-check-and-output-texi program picks them out from
> the code.  (Or something like that.)  Not documented in the manual
> though (alas).

Docsnarfing is something I'd like to see made available (again) for quite some time now.  The pieces that implement this for Guile (several scripts and some compiled code) are not currently installed.  It was at one time, but removed because of the difficulty in supporting all the platfroms that Guile supports. (If I remember correctly)

I've been (very slowly!) bringing scwm up to date with Guile 1.8.  Scwm uses docstrings as heavily as emacs.  It would *really* be great to have docsnarfing working again.  My currenty plans are to lift the Guile code and inlcude it as part of scwm.

-Dale



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2006-07-15 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-15 18:21 dsmich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-15 21:19 docstrings and snarfing dsmich
2006-07-16 21:48 ` dave
2006-07-18 17:14   ` Neil Jerram
2006-07-13 10:15 Dave Griffiths
2006-07-15  1:57 ` Kevin Ryde

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8255671.1152987660797.JavaMail.root@web23 \
    --to=dsmich@adelphia.net \
    --cc=guile-user@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.
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).