unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Adding to the end of the load path
Date: Fri, 16 Nov 2012 16:38:35 -0500	[thread overview]
Message-ID: <CA+U71=NPM=4DqcOcfp0Rv9uHvV8zGDYiuzgcWbUZ1M162+8rfA@mail.gmail.com> (raw)
In-Reply-To: <87r4nts7lq.fsf@tines.lan>

[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]

On Fri, Nov 16, 2012 at 1:52 PM, Mark H Weaver <mhw@netris.org> wrote:

> Hi Noah,
>

Hello,


> In general, I think the idea of requiring people to write scheme code to
> manipulate %load-path (and other settings) is a fine approach.  Maybe
> you're right that this is better than adding a bunch of new environment
> variables.


> However, neither init.scm nor ~/.guile is sufficient for this job.
> init.scm is site-wide, and generally only editable by root, and ~/.guile
> is only run by interactive REPL sessions.  So to do as you suggest, we'd
> need to add another user-specific file that is read when initializing
> guile, even for non-interactive sessions.
>

Ah, I didn't realize that was an issue. I was modeling this on what Emacs
does, but it doesn't run in batch mode very much. Three configuration files
with different meanings seems like a lot, but there's no other way that
preserves backwards compatibility. Maybe we could use the $XDG_CONFIG
directory for it (not that I like their default value).


> Also, note that this still doesn't solve our immediate problem regarding
> Guildhall and SRFIs in a backward-compatible way, so we still need to
> support the "..." marker for the next 7-8 years, unless someone has a
> better suggestion.
>

I see your point, but leaving it like this doesn't fix anything that isn't
already broken; is that right? If so, I think we could justify saying that
people need to upgrade to get the new behavior, especially if the
complexity of supporting old versions is high.

Noah

[-- Attachment #2: Type: text/html, Size: 2300 bytes --]

  reply	other threads:[~2012-11-16 21:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05  3:18 Adding to the end of the load path Ian Price
2012-11-08  1:03 ` Andreas Rottmann
2012-11-11  7:50   ` Mark H Weaver
2012-11-11 19:02     ` Andreas Rottmann
2012-11-11 21:51       ` Mark H Weaver
2012-11-12 16:35         ` Bruce Korb
2012-11-13 21:04   ` Ludovic Courtès
2012-11-15 22:06     ` Andreas Rottmann
2012-11-15 22:37       ` Ludovic Courtès
2012-11-15 22:44       ` Mark H Weaver
2012-11-15 23:06         ` Ludovic Courtès
2012-11-16  0:10         ` Noah Lavine
2012-11-16 14:00           ` Noah Lavine
2012-11-16 18:06           ` Bruce Korb
2012-11-16 18:52           ` Mark H Weaver
2012-11-16 21:38             ` Noah Lavine [this message]
2012-11-28 23:12     ` [PATCH] Add parse-path-with-ellipsis, and use it for GUILE_LOAD_PATH et al Mark H Weaver
2012-11-28 23:46       ` Ludovic Courtès
2012-11-29  3:04         ` Mark H Weaver
2012-11-29 10:27           ` 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='CA+U71=NPM=4DqcOcfp0Rv9uHvV8zGDYiuzgcWbUZ1M162+8rfA@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    /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).