From: Neil Jerram <neil@ossau.homelinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: add-relative-load-path ?
Date: Sat, 14 Jan 2012 21:48:57 +0000 [thread overview]
Message-ID: <87boq6q7jq.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <87zkdycjl6.fsf@pobox.com> (Andy Wingo's message of "Sun, 08 Jan 2012 16:14:29 +0100")
Andy Wingo <wingo@pobox.com> writes:
> Then in your script you would (add-relative-load-path ".").
>
> Maybe we need an `add-to-load-path' form that handles the eval-when,
> actually, so it would be
>
> (add-to-load-path (dirname (current-source-filename)))
>
> or something like that. (We'd have to define current-source-filename as
> well, in terms of current-source-location.)
>
> What do folks think? Is it work it?
Yes, I think so! I think it will be a great help for uninstalled
experimentation.
I can think of a couple of plausible enhancements:
(1) factoring out any occurrences of "/x/.." and "/." in the directory
that results from the in-vicinity call
(2) only adding the directory to the load path if it isn't already
there.
But neither of those is crucial.
Of the possibilities above, I think I prefer
> (add-to-load-path (dirname (current-source-filename)))
Thanks for thinking about this.
Neil
next prev parent reply other threads:[~2012-01-14 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 15:14 add-relative-load-path ? Andy Wingo
2012-01-14 21:48 ` Neil Jerram [this message]
2012-01-20 23:14 ` Andy Wingo
2012-01-21 23:17 ` Neil Jerram
2012-01-23 10:18 ` Andy Wingo
2012-01-23 15:45 ` Ludovic Courtès
2012-01-23 16:20 ` Andy Wingo
2012-01-23 19:36 ` Neil Jerram
2012-01-25 12:42 ` Ludovic Courtès
2012-01-25 14:31 ` Andy Wingo
2012-01-25 20:41 ` Ludovic Courtès
2012-01-25 23:08 ` Andy Wingo
2012-01-23 20:19 ` Neil Jerram
2012-01-30 20:20 ` add-relative-load-path ? - scm_add_load_path too? Ian Hulin
2012-01-31 8:53 ` Mark H Weaver
2012-01-31 16:10 ` Mark H Weaver
2012-02-01 23:30 ` Ian Hulin
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=87boq6q7jq.fsf@neil-laptop.ossau.uklinux.net \
--to=neil@ossau.homelinux.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).