From: mikel evins <mevins@me.com>
To: Per Bothner <per@bothner.com>
Cc: mikel evins <mevins@me.com>, kawa@sourceware.org
Subject: Re: the right way to compile and load modules
Date: Tue, 13 May 2014 10:23:00 -0000 [thread overview]
Message-ID: <DF4CB16C-DA39-4CF9-B2C8-F381EF8A9EE1@me.com> (raw)
In-Reply-To: <ED4375FE-30EE-4ABC-A9DC-2C6C4D67A87A@me.com>
On May 13, 2014, at 3:40 AM, mikel evins <mevins@me.com> wrote:
> How can I make a system load file that will import or require all of the sources of a project into an interactive session without using load?
Turns out it's easy. If my source files are foo.scm, bar.scm, and baz,scm, I just make a a loadfile like this:
(require "foo,scm")
(require "bar,scm")
(require "baz,scm")
...and place the loadfile in the same directory as "foo.scm", "bar.scm", and "baz.scm".
next prev parent reply other threads:[~2014-05-13 10:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 4:09 mikel evins
2014-05-13 7:29 ` Charles Turner
2014-05-13 7:45 ` mikel evins
2014-05-13 7:49 ` Per Bothner
2014-05-13 7:55 ` Per Bothner
2014-05-13 8:02 ` mikel evins
2014-05-13 8:40 ` mikel evins
2014-05-13 10:23 ` mikel evins [this message]
2014-05-14 1:13 ` mikel evins
2014-05-14 1:19 ` parameters not working? mikel evins
2014-05-14 1:31 ` Per Bothner
2014-05-14 1:41 ` mikel evins
2014-05-14 2:12 ` mikel evins
2014-05-14 2:19 ` mikel evins
2014-05-14 9:32 ` mikel evins
2014-05-14 16:07 ` Per Bothner
2014-05-14 1:43 ` the right way to compile and load modules Per Bothner
2014-05-14 1:50 ` mikel evins
2014-05-14 2:05 ` mikel evins
2014-05-14 3:52 ` Per Bothner
2014-05-14 3:59 ` mikel evins
2014-05-14 6:29 ` Per Bothner
2014-05-14 6:52 ` mikel evins
2014-05-14 18:59 ` Kawa experience [was: the right way to compile and load modules] Per Bothner
2014-05-14 20:06 ` Charles Turner
2014-05-15 2:16 ` mikel evins
2014-05-14 7:26 ` the right way to compile and load modules mikel evins
2014-05-14 7:33 ` Per Bothner
2014-05-14 7:35 ` mikel evins
2014-05-14 18:46 ` Per Bothner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DF4CB16C-DA39-4CF9-B2C8-F381EF8A9EE1@me.com \
--to=mevins@me.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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).