From: Jay K <jay.krell@cornell.edu>
To: <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: RE: error building guile documentation
Date: Fri, 11 Jun 2010 14:11:45 +0000 [thread overview]
Message-ID: <COL101-W289A94D5C658F2AD139AB1E6D90@phx.gbl> (raw)
In-Reply-To: <m3mxv3nkcy.fsf@pobox.com>
Thanks, that worked, of course.
- Jay
---------------------------------------
> From: wingo@pobox.com
> To: jay.krell@cornell.edu
> CC: bug-guile@gnu.org
> Subject: Re: error building guile documentation
> Date: Thu, 10 Jun 2010 14:27:25 +0200
>
> On Thu 10 Jun 2010 11:45, Jay K writes:
>
>> cat alist.doc .... guile-procedures.texi || { rm guile-procedures.texi; false; }
>> ERROR: unknown doc attribute: (location (string . /home/jayk/src/guile-1.8.7/libguile/alist.c) (int . 40) (hash . hash))
>
> https://savannah.gnu.org/bugs/?29583
>
> Andy
> --
> http://wingolog.org/
prev parent reply other threads:[~2010-06-11 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 9:45 error building guile documentation Jay K
2010-06-10 12:27 ` Andy Wingo
2010-06-11 14:11 ` Jay K [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
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=COL101-W289A94D5C658F2AD139AB1E6D90@phx.gbl \
--to=jay.krell@cornell.edu \
--cc=bug-guile@gnu.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).