From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Add procedures to convert alists into hash tables
Date: Mon, 24 Mar 2014 23:15:18 +0100 [thread overview]
Message-ID: <8761n3mefd.fsf@gnu.org> (raw)
In-Reply-To: <87ha6nux0w.fsf@pobox.com> (Andy Wingo's message of "Mon, 24 Mar 2014 22:06:23 +0100")
Andy Wingo <wingo@pobox.com> skribis:
> On Mon 18 Nov 2013 21:32, ludo@gnu.org (Ludovic Courtès) writes:
>
>>> +(define (alist->hashx-table hash assoc alist)
>>> + "Convert @var{alist} into a hash table with custom @var{hash} and
>>> +@var{assoc} procedures."
>>
>> Currently Texinfo markup in docstrings is left uninterpreted so it
>> can/should be avoided (it may change in the future, but the future’s not
>> now ;-)).
>
> Actually the future has always been now, but just not everywhere :)
>
> If you add this to your .guile:
>
> (use-modules (texinfo reflection))
>
> then all docstrings will be parsed and rendered using Guile's texinfo
> toolchain.
Yep, I discovered that in the meantime. :-)
> Also modules get nice help too; see e.g. (help (ice-9 popen)). We
> should probably fix whatever small bugs are out there regarding the
> output and just enable it by default.
Yes, agreed. The output appears to be “good enough”, AFAICS.
What would be the right way to enable it? Should (ice-9 session)
#:autoload (texinfo reflection), and do the ‘add-value-help-handler!’
itself?
Ludo’.
next prev parent reply other threads:[~2014-03-24 22:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 14:14 [PATCH] Add procedures to convert alists into hash tables David Thompson
2013-10-20 14:28 ` David Thompson
2013-10-21 17:00 ` Mark H Weaver
2013-10-22 3:03 ` David Thompson
2013-10-28 12:17 ` Chris K. Jester-Young
2013-10-28 23:51 ` David Thompson
2013-10-26 11:41 ` David Thompson
2013-10-29 12:38 ` Ludovic Courtès
2013-10-30 20:19 ` Thompson, David
2013-11-03 12:43 ` Thien-Thi Nguyen
2013-11-05 19:57 ` Mark H Weaver
2013-11-06 12:54 ` Ludovic Courtès
2013-11-06 13:14 ` Thompson, David
2013-11-18 1:50 ` David Thompson
2013-11-18 2:42 ` David Thompson
2013-11-18 3:22 ` Mark H Weaver
2013-11-18 20:32 ` Ludovic Courtès
2013-11-19 2:00 ` David Thompson
2013-11-19 4:06 ` Mark H Weaver
2013-11-19 13:14 ` Thompson, David
2014-03-24 21:06 ` Andy Wingo
2014-03-24 22:15 ` Ludovic Courtès [this message]
2014-03-24 22:26 ` Andy Wingo
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=8761n3mefd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).