From: Rob Browning <rlb@defaultvalue.org>
To: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: SLIB
Date: Sun, 02 Sep 2007 17:42:51 -0700 [thread overview]
Message-ID: <87ejhgtw8k.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87odh7gkwx.fsf@zip.com.au> (Kevin Ryde's message of "Fri\, 17 Aug 2007 08\:43\:42 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Yep. Rob worked on that, or on slib.scm loading guile.init at least.
> He checked-in an slib.scm along those lines into the 1.6 branch,
>
> http://cvs.savannah.gnu.org/viewvc/guile/guile-core/ice-9/slib.scm?revision=1.32.2.10&root=guile&view=markup&pathrev=branch_release-1-6
>
> I'm not certain if it covers every possibility, but it does mean current
> and future slib has a good chance of working. (I've only really nosed
> around this stuff lately to let my lint program work with it.)
Yes, and I had intended for us to add a similar adjustment to 1.8, but
it didn't happen before the release.
Since Aubrey Jaffer seems quite willing to work with us to accommodate
adjustments to guile.init, I had thought that it might be reasonable
to just alter (ice-9 slib) to load guile.init and begin forwarding all
of our changes to him.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-09-03 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 11:36 SLIB Ludovic Courtès
2007-08-11 17:00 ` SLIB Mikael Djurfeldt
2007-08-15 23:05 ` SLIB Kevin Ryde
2007-08-16 8:24 ` SLIB Mikael Djurfeldt
2007-08-16 22:43 ` SLIB Kevin Ryde
2007-09-03 0:42 ` Rob Browning [this message]
2007-09-03 7:22 ` SLIB Ludovic Courtès
2007-09-04 5:23 ` SLIB Rob Browning
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=87ejhgtw8k.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=user42@zip.com.au \
/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).