From: Andy Wingo <wingo@pobox.com>
To: Richard Shann <richard.shann@virgin.net>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>, Mike Gran <spk121@yahoo.com>
Subject: Re: Creating a top level definition if none so far exists, on the fly.
Date: Sat, 07 Sep 2013 11:48:17 +0200 [thread overview]
Message-ID: <87y579vu72.fsf@pobox.com> (raw)
In-Reply-To: <20130815143730.5afc5963@DebianBox.loc> (Richard Shann's message of "Thu, 15 Aug 2013 14:37:30 +0100")
On Thu 15 Aug 2013 15:37, Richard Shann <richard.shann@virgin.net> writes:
> Hmm, so I asked about this before in February. Gives me an idea of the
> extent of my memory span - it didn't even ring a bell.
You know, I forgot about the answer too ;-)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-09-07 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 10:57 Creating a top level definition if none so far exists, on the fly Richard Shann
2013-08-15 11:10 ` rixed
2013-08-15 11:18 ` Mike Gran
2013-08-15 12:08 ` Richard Shann
2013-08-15 12:17 ` Mike Gran
2013-08-15 13:37 ` Richard Shann
2013-09-07 9:48 ` Andy Wingo [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=87y579vu72.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=richard.shann@virgin.net \
--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).