From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org
Subject: Re: Errors using `reload' command
Date: Tue, 08 Feb 2011 23:48:08 +0100 [thread overview]
Message-ID: <m3bp2mf8if.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CD91EE4B5F7F3C-2564-1D76E@webmail-m030.sysops.aol.com> (Mark Harig's message of "Thu, 03 Feb 2011 14:18:38 -0500")
Hi Mark,
On Thu 03 Feb 2011 20:18, Mark Harig <idirectscm@aim.com> writes:
> scheme@(guile-user)> ,re
> While executing meta-command:
> ERROR: unknown file name for module #<directory (guile-user) 257d090>
Indeed, `reload' only works with modules that are associated with
files. (guile-user) is not one of them. Neither are these:
> (value-history)
> (guile)
But this is an interesting one:
> scheme@(guile-user)> ,use
> (system base compile)
> (ice-9 readline)
> (ice-9 readline)
> (ice-9 r5rs)
> (ice-9 session)
> (ice-9 regex)
> (ice-9 threads)
>
> [Note that "(ice-9 readline)" is listed twice, above. This is not a
> transcription error.]
This appears to arise because use-modules clauses are evaluated twice
(once at expand-time, and once at load-time) and module-use-interfaces!
was not doing the right thing. Fixed.
> scheme@(guile-user)> ,re (ice-9 readline)
> While executing meta-command:
> ERROR: In procedure primitive-load-path:
> ERROR: Unable to find file "guile-readline/ice-9/readline.scm" in load
> path
Fixed this one too, I think.
Thanks for the reports,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-08 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 19:18 Errors using `reload' command Mark Harig
2011-02-08 22:48 ` Andy Wingo [this message]
2011-02-08 22:58 ` Andy Wingo
2011-02-09 8:20 ` Andy Wingo
2011-02-09 9:51 ` Ludovic Courtès
2011-02-09 19:59 ` Andy Wingo
2011-02-09 20:49 ` Ludovic Courtès
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=m3bp2mf8if.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=idirectscm@aim.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).