From: "Andreas Vögele" <voegelas@gmx.net>
Subject: Re: The load path
Date: Sat, 06 Nov 2004 15:38:41 +0100 [thread overview]
Message-ID: <m1actvkpou.fsf@ID-28718.user.uni-berlin.de> (raw)
In-Reply-To: <87u0s3r30n.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Fri, 05 Nov 2004 22:54:16 -0600")
Rob Browning writes:
> One of the simlplest solutions is to load all the files in a
> well-specified /etc dir in some order. That's what Marius proposed,
> and that's what Debian tends to do, both with Emacs, and with
> various other things (ppp, ifup, cron, rc.?, etc.).
All this could be done from init.scm without changing Guile. The only
thing that would be required is a new command-line option that
inhibits loading of init.scm so that users may skip the site-wide
initialization.
IMHO it would be okay to distribute an init.scm that loads init files
from a directory with Guile. But please make it optional. Packagers
could then decide whether to use that init.scm or not. I don't see
why things that can be done outside of the Guile core should go into
the core. The way Emacs loads init files on Debian is also not part
of Emacs and the same is true of ifup, cron etc.
What makes me especially wary is the fact that people have mentioned
Debian's init.d system in this thread. I use Debian at work and at
home but I've never liked System V init scripts. And Debian's
incarnation is by far the worst implementation of that scheme that
I've ever seen.
_______________________________________________
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 14:38 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
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 [this message]
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=m1actvkpou.fsf@ID-28718.user.uni-berlin.de \
--to=voegelas@gmx.net \
/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).