From: diogofsr@gmail.com (Diogo F. S. Ramos)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: Guile Mailing List <guile-user@gnu.org>
Subject: Re: Loading a module before and after adding a load path
Date: Sat, 19 Jan 2013 04:05:02 -0200 [thread overview]
Message-ID: <87ehhhwvw1.fsf@supernova.vialactea> (raw)
In-Reply-To: <CA+U71=OG6j9C7vuxu0EDQ=fDX_CEBd4yavQ6E8-ppQJ8cnj8fA@mail.gmail.com> (Noah Lavine's message of "Fri, 18 Jan 2013 23:32:35 -0500")
Noah Lavine <noah.b.lavine@gmail.com> writes:
> As a workaround, remove your module from the list "autoloads-done". (actually, there will be a pair
> in that list, where the cdr of the pair is the name of the module as a string. remove that.)
Nice! Thank you.
Here is a little procedure that might help someone (it needs srfi-1):
(define (remove-from-autoloads-done module)
(define (make-item module)
(let ((strings-module (map symbol->string module)))
(cons (string-join (drop-right strings-module 1) "/" 'suffix)
(last strings-module))))
(set! autoloads-done
(delete (make-item module) autoloads-done)))
And an example:
scheme@(guile-user)> (use-modules (foo bar))
While compiling expression:
ERROR: no code for module (foo bar)
scheme@(guile-user)> (add-to-load-path "/tmp")
scheme@(guile-user)> (use-modules (foo bar))
While compiling expression:
ERROR: no code for module (foo bar)
scheme@(guile-user)> (remove-from-autoloads-done '(foo bar))
scheme@(guile-user)> (use-modules (foo bar))
scheme@(guile-user)> (hello)
hello, world
scheme@(guile-user)>
next prev parent reply other threads:[~2013-01-19 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 15:53 Loading a module before and after adding a load path Diogo F. S. Ramos
2013-01-18 17:44 ` Yanbin Zhang
2013-01-18 18:17 ` Diogo F. S. Ramos
2013-01-19 3:17 ` Nala Ginrut
2013-01-19 4:15 ` Diogo F. S. Ramos
2013-01-19 4:32 ` Noah Lavine
2013-01-19 6:05 ` Diogo F. S. Ramos [this message]
2013-01-20 18:34 ` Andy Wingo
2013-01-21 17:20 ` Ludovic Courtès
2013-01-21 18:12 ` 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=87ehhhwvw1.fsf@supernova.vialactea \
--to=diogofsr@gmail.com \
--cc=guile-user@gnu.org \
--cc=noah.b.lavine@gmail.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).