From: Andy Wingo <wingo@pobox.com>
To: Marco Maggi <marco.maggi-ipsu@poste.it>
Cc: bug-guile@gnu.org, Mike Gran <spk121@yahoo.com>
Subject: Re: [r6rs] #\x0 is a perfectly valid character datum representation
Date: Mon, 21 Jun 2010 21:26:19 +0200 [thread overview]
Message-ID: <m3d3vkb31g.fsf@pobox.com> (raw)
In-Reply-To: <8739wg4xe0.fsf@rapitore.luna> (Marco Maggi's message of "Mon, 21 Jun 2010 10:12:39 +0200")
On Mon 21 Jun 2010 10:12, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> #\x0
Add (read-enable 'r6rs-hex-escapes) to your guile init file.
Mike: is there a more sensible default than the one we have?
Thanks,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-21 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 8:12 [r6rs] #\x0 is a perfectly valid character datum representation Marco Maggi
2010-06-21 19:26 ` Andy Wingo [this message]
2010-06-21 20:27 ` Mike Gran
2010-06-21 20:36 ` Andy Wingo
2010-06-21 20:42 ` Mike Gran
-- strict thread matches above, loose matches on Subject: below --
2010-07-17 11:22 Mike Gran
2010-07-17 11:38 ` 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=m3d3vkb31g.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
--cc=spk121@yahoo.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).