From: Wolfgang Jaehrling <pro-linux@gmx.de>
Cc: guile-devel@gnu.org
Subject: Re: Overwriting bindings by importing
Date: Sat, 1 May 2004 18:12:37 +0200 [thread overview]
Message-ID: <20040501161237.GA236@gmx.de> (raw)
In-Reply-To: <874qr1t5k5.fsf@zip.com.au>
On Sat, May 01, 2004 at 09:22:02AM +1000, Kevin Ryde wrote:
> That's wrong I think.
Loading `(ice-9 history)' in my `.guile' file caused this.
wj@kaputt:~$ guile -q
guile> (use-modules (ice-9 history))
guile> (use-modules (srfi srfi-1))
guile> iota
$1 = #<procedure iota (n)>
wj@kaputt:~$ guile -q
guile> (use-modules (srfi srfi-1))
guile> iota
#<procedure iota (count . rest)>
Cheers,
Wolfgang
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-05-01 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 13:09 Overwriting bindings by importing Wolfgang Jaehrling
2004-04-30 23:22 ` Kevin Ryde
2004-05-01 16:12 ` Wolfgang Jaehrling [this message]
2004-05-09 0:47 ` Kevin Ryde
2004-05-24 20:49 ` Marius Vollmer
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=20040501161237.GA236@gmx.de \
--to=pro-linux@gmx.de \
--cc=guile-devel@gnu.org \
--cc=wolfgang@pro-linux.de \
/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).