From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-devel <guile-devel@gnu.org>,
Marius Vollmer <marius.vollmer@uni-dortmund.de>
Subject: Re: The load path
Date: Sat, 06 Nov 2004 02:25:06 -0500 [thread overview]
Message-ID: <m3vfcj5thz.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87lldgt0i3.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Fri, 05 Nov 2004 16:05:40 -0600")
Rob Browning <rlb@defaultvalue.org> wrote:
> Overall, what I wanted was a way to specify a set of actions that will
> be taken at init time, where the ordering can be easily specified,
> where actions can be added and removed easily (i.e. by adding/removing
> files), and where the local admin has a well defined way to make at
> least some adjustments if necessary.
If the init actions are limited to %load-path tweaking, then I think a
directory-of-(directories|symlinks) is sufficient. If the init
actions can go beyond that (which will be possible if they are
represented in Scheme files), then I'm not sure I want that to affect
every one of my Guile invocations. I'm glad my shell scripts, Perl
scripts, Python scripts, etc., aren't all forced to load some
site-wide initialization code. Scripts know what they need, and take
care of it themselves. Arbitrary init code is convenient for
interactive interpreters, but I'm wary of establishing it for all
invocations.
paul
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-11-06 7:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 17:52 The load path Andy Wingo
2004-10-17 19:40 ` Rob Browning
2004-10-17 23:13 ` Greg Troxel
2004-11-05 15:05 ` Marius Vollmer
2004-11-05 15:25 ` Paul Jarc
2004-11-05 16:43 ` Rob Browning
2004-11-05 17:43 ` Paul Jarc
2004-11-05 18:59 ` Rob Browning
2004-11-05 19:22 ` Paul Jarc
2004-11-05 22:05 ` Rob Browning
2004-11-06 7:25 ` Paul Jarc [this message]
2004-11-06 16:19 ` Rob Browning
2004-11-06 22:58 ` Rob Browning
2004-11-05 16:15 ` Rob Browning
2004-11-05 17:31 ` Andreas Rottmann
2004-11-05 18:57 ` Greg Troxel
2004-11-05 19:07 ` Rob Browning
2004-11-05 19:19 ` Greg Troxel
2004-11-05 23:53 ` Neil Jerram
2004-11-06 4:54 ` Rob Browning
2004-11-06 14:38 ` Andreas Vögele
2004-11-06 17:49 ` Neil Jerram
2004-11-06 21:21 ` Rob Browning
2004-11-07 18:46 ` Neil Jerram
2004-11-07 21:16 ` Rob Browning
2004-11-09 15:22 ` Paul Jarc
2004-11-10 18:43 ` Andy Wingo
2004-11-11 13:23 ` Greg Troxel
2004-11-12 21:31 ` Neil Jerram
2004-11-13 0:22 ` Greg Troxel
2004-11-13 1:08 ` Rob Browning
2004-11-13 16:12 ` Greg Troxel
2004-11-14 11:02 ` Neil Jerram
2004-11-14 14:05 ` Greg Troxel
2004-11-18 19:44 ` Neil Jerram
2004-11-19 14:46 ` Greg Troxel
2004-11-14 10:48 ` Neil Jerram
2004-11-15 16:43 ` Andy Wingo
2004-11-18 19:54 ` Neil Jerram
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=m3vfcj5thz.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-devel@gnu.org \
--cc=marius.vollmer@uni-dortmund.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).