From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: -I for guile command line
Date: Sat, 21 Aug 2004 19:45:12 +0200 [thread overview]
Message-ID: <87smagidw7.fsf@zagadka.ping.de> (raw)
In-Reply-To: <4594ABAD-EF11-11D8-BD8D-000A95CD5044@mac.com> (Richard Todd's message of "Sun, 15 Aug 2004 18:17:26 -0500")
Richard Todd <rwtodd@mac.com> writes:
> Try this patch... I think it addresses everything you mentioned.
Yep, excellent, thanks! I have applied it.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-21 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 1:35 -I for guile command line Richard Todd
2004-07-10 0:12 ` Kevin Ryde
2004-07-10 1:28 ` Richard Todd
2004-08-15 21:27 ` Marius Vollmer
2004-08-15 21:36 ` Richard Todd
2004-08-15 23:17 ` Richard Todd
2004-08-15 23:18 ` Richard Todd
2004-08-21 17:45 ` Marius Vollmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 17:56 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=87smagidw7.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/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).