unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Tim Meehan <btmeehan@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: How to use guile in a development process
Date: Thu, 29 Apr 2021 21:34:19 -0500	[thread overview]
Message-ID: <CACgrOxJ3=ALeDqbW=8y=Yo92Ah_PL6Qm=CCOftHU6kDytskqFQ@mail.gmail.com> (raw)
In-Reply-To: <CAPHgq+JxjG8rTc61ZgrBun5_c+X0T67Tf-1Kb4XV6URhBo5n1w@mail.gmail.com>

Anthony - thanks for asking that question, I always wind up learning
something interesting on this mailing list.

On Wed, Apr 28, 2021 at 7:57 PM Anthony Quizon <anthoq88@gmail.com> wrote:

> Hello,
>
> I'm having trouble finding a good development process with guile.
>
> I have a file foo.scm and I'm trying to load it into the repl.
> However, I couldn't find any documentation on how to easily do this.
> I tried looking up ",help module" in the repl which told me to use ",load
> FILE".
> But when I tried this I got the error "In procedure primitive-load-path:
> Unable to find file "system/repl/foo.scm" in load path"
>
> I don't know where to look to change my load file for the repl.
>
> I read in a forum somewhere to add (add-to-load-path ".") in my .guile file
> but that didn't work.
>
> How do I load a file from the current path that I'm in?
> But more importantly, what is the typical workflow when using guile?
> Do people write files to the filesystem and load them in the repl to try it
> out?
> Or is there a faster way to do things?
>
> Thanks,
>


  parent reply	other threads:[~2021-04-30  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  0:35 How to use guile in a development process Anthony Quizon
2021-04-29  2:19 ` Nala Ginrut
2021-04-29  7:26   ` Dr. Arne Babenhauserheide
2021-04-29  8:16 ` Adriano Peluso
2021-04-29 14:49 ` Jérémy Korwin-Zmijowski
2021-04-30  2:34 ` Tim Meehan [this message]
2021-04-30 11:22   ` Leo Butler

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='CACgrOxJ3=ALeDqbW=8y=Yo92Ah_PL6Qm=CCOftHU6kDytskqFQ@mail.gmail.com' \
    --to=btmeehan@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).