From: Ian Price <ianprice90@googlemail.com>
To: Alex Kost <alezost@gmail.com>
Cc: 18127@debbugs.gnu.org, 18127-done@debbugs.gnu.org
Subject: bug#18127: add-to-load-path adds a path twice
Date: Wed, 30 Jul 2014 19:36:36 +0100 [thread overview]
Message-ID: <87wqau66dn.fsf@kagami.home> (raw)
In-Reply-To: <8761ihab01.fsf@gmail.com> (Alex Kost's message of "Mon, 28 Jul 2014 17:06:22 +0400")
Alex Kost <alezost@gmail.com> writes:
> taylanub from #guile explained that it may happen because in the REPL
> the compilation and execution happen in the same session and
> “‘add-to-load-path’ takes care of modifying the path both at
> compile-time and at run-time.” (from manual).
This is correct, it will also happen in scripts if they are
auto-compiled, but you will only see it once on subsequent runs, since
macro-expansion doesn't need to happen again.
The fix is simple, and there is no harm in it, so I've pushed a fix to
stable-2.0.
> Also I have a question: Why there is no ‘add-to-load-compiled-path’? I
> think such function may also be useful.
Fair question. I have no idea about the answer, but I've not touched
this one. As a general principle, I wouldn't like to see us have a
separate macro for each of these.
Thanks
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
prev parent reply other threads:[~2014-07-30 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 13:06 bug#18127: add-to-load-path adds a path twice Alex Kost
2014-07-30 18:36 ` Ian Price [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=87wqau66dn.fsf@kagami.home \
--to=ianprice90@googlemail.com \
--cc=18127-done@debbugs.gnu.org \
--cc=18127@debbugs.gnu.org \
--cc=alezost@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).