From: Catonano <catonano@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: Haunt load path
Date: Mon, 22 Jan 2018 16:30:18 +0100 [thread overview]
Message-ID: <CAJ98PDyHw04o-vYdPmxWVfW8ZD+U3_9aoQCVztWPWT5k6F3wqQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ98PDyt0U-dOPCjn-0L7MLD0VP9OyRSo-EgoqTBfC=85S1x6g@mail.gmail.com>
2018-01-14 8:44 GMT+01:00 Catonano <catonano@gmail.com>:
> I have a naive question (as usual)
>
> I'm trying David Thompson's Haunt static site builder
>
> In my blog root I made a "scheme/builder/blog.scm" path
>
> and blog.scm contains a builder called "my-builder"
>
> my-builder is copied from the built in builder that comes with Haunt
>
> I just copied and pasted it and changed its name
>
> haunt build can't reach it
>
> I understood that my blog root was being added to the load path
>
> What is going on here ?
>
> Thanks
>
I managed to make it work
Thanks anyway
prev parent reply other threads:[~2018-01-22 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 7:44 Haunt load path Catonano
2018-01-22 15:30 ` Catonano [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=CAJ98PDyHw04o-vYdPmxWVfW8ZD+U3_9aoQCVztWPWT5k6F3wqQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guile-user@gnu.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).