From: Leo Butler <leo.butler@umanitoba.ca>
To: Tim Meehan <btmeehan@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: How to use guile in a development process
Date: Fri, 30 Apr 2021 06:22:38 -0500 [thread overview]
Message-ID: <86tunovwxt.fsf@x201.butler.org> (raw)
In-Reply-To: <CACgrOxJ3=ALeDqbW=8y=Yo92Ah_PL6Qm=CCOftHU6kDytskqFQ@mail.gmail.com> (Tim Meehan's message of "Thu, 29 Apr 2021 21:34:19 -0500")
Tim Meehan <btmeehan@gmail.com> writes:
>>
>> 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?
I use geiser in emacs to run a guile repl and edit source code. This
allows one to write source in a file and compile/load it, or write the
source in the repl and copy it into a file when it is working and either
way works fine.
Leo
prev parent reply other threads:[~2021-04-30 11:22 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
2021-04-30 11:22 ` Leo Butler [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=86tunovwxt.fsf@x201.butler.org \
--to=leo.butler@umanitoba.ca \
--cc=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).