From: Ian Price <ianprice90@googlemail.com>
To: 12173@debbugs.gnu.org
Subject: bug#12173: docstrings and .guile
Date: Fri, 10 Aug 2012 20:25:48 +0100 [thread overview]
Message-ID: <87lihma6rn.fsf@Kagami.home> (raw)
Hi guilers,
While debugging, I realised the root cause of my problem was that I
could not access procedure documentation for procedures defined in my
.guile
The issue is simple to reproduce, I added
(define (test)
"docs"
#f)
to my .guile, and from a new guile repl
scheme@(guile-user)> ,d test
#f
scheme@(guile-user)> (define (test) "docs" #f)
scheme@(guile-user)> ,d test
docs
This happens on 32bit fedora 16 on stable-2.0 git commit
1321a36ed61deb9431b41768dc92cb7230c9afa1
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next reply other threads:[~2012-08-10 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 19:25 Ian Price [this message]
2012-11-28 13:33 ` bug#12173: docstrings and .guile Ludovic Courtès
2012-11-28 15:46 ` Ludovic Courtès
2012-11-29 20:19 ` Ian Price
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=87lihma6rn.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=12173@debbugs.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).