From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: 10567@debbugs.gnu.org
Subject: bug#10567: Fw: guile-library - make bug report
Date: Sat, 4 Feb 2012 14:29:43 -0200 [thread overview]
Message-ID: <20120204142943.21e0ba23@rascar> (raw)
In-Reply-To: <87sjirj554.fsf@pobox.com>
Hi Andy,
> The line in question:
>
> (eq? (car rest) ':)
>
> It seems you have (read-set! keywords 'prefix) in your init.scm, which
> affects the compile-time environment.
Yes I do, sorry i din't think of that but i confirm it is the case.
...
Cheers,
David
Aside, I always did actually [read-set! ...], and questioned myself, as an 'old
lisper', why scheme does requirer, per defaut, that we enter 2 chars instead of
one, what ever i would be, to tell guile/scheme it's dealing with a keyword ?
next prev parent reply other threads:[~2012-02-04 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:25 bug#10567: Fw: guile-library - make bug report David Pirotte
2012-02-03 15:41 ` Andy Wingo
2012-02-04 16:29 ` David Pirotte [this message]
2013-03-02 22:16 ` 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=20120204142943.21e0ba23@rascar \
--to=david@altosw.be \
--cc=10567@debbugs.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).