From: Andy Wingo <wingo@pobox.com>
To: taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer")
Cc: 21347-done@debbugs.gnu.org
Subject: bug#21347: include-from-path and relative paths in load-path
Date: Fri, 24 Jun 2016 10:42:17 +0200 [thread overview]
Message-ID: <87k2hfgeqe.fsf@pobox.com> (raw)
In-Reply-To: <87twrni281.fsf@T420.taylan> ("Taylan Ulrich \"Bayırlı/Kammer\""'s message of "Tue, 25 Aug 2015 21:42:54 +0200")
On Tue 25 Aug 2015 21:42, taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
> When there are relative paths in the load-path, `include-from-path'
> seems to always interpret them relative to the directory of the file in
> which the `include-from-path' is called, instead of relative to the
> current working directory in effect when Guile is started.
Indeed, good catch. Fixed in master. I don't know if we can fix in
2.0.
Andy
prev parent reply other threads:[~2016-06-24 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 19:42 bug#21347: include-from-path and relative paths in load-path Taylan Ulrich Bayırlı/Kammer
2016-06-24 8:42 ` Andy Wingo [this message]
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=87k2hfgeqe.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=21347-done@debbugs.gnu.org \
--cc=taylanbayirli@gmail.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).