From: raingloom <raingloom@riseup.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: jgart <jgart@dismail.de>, Edouard Klein <edou@rdklein.fr>,
help-guix@gnu.org
Subject: Re: Loading Common Lisp Libraries with GNU/Guix in a REPL
Date: Sun, 12 Dec 2021 20:27:16 +0100 [thread overview]
Message-ID: <20211212202716.089695f9@riseup.net> (raw)
In-Reply-To: <87wnk9g3kh.fsf@gmail.com>
On Sun, 12 Dec 2021 11:01:34 -0600
Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:
> Edouard Klein <edou@rdklein.fr> writes:
>
> I also don't know the canonical way, but I do it a different way. I'm
> wondering what the simpler way to do things is? I know nothing about
> rlwrap. But here's how I do things:
>
> Depending on the project, I may have a =guix.scm= package defined for
> it or not. This only changes how I invoke =guix shell=, not the
> technique.
>
> From emacs, I run slime: with =C-u M-x slime=. It prompts me for
> which lisp I want to run, and then I type =guix shell -D -- sbcl=.
> This seems pretty simple.
>
> I think I did have to include this in my bash initialization though.
> I'm not sure if it will work without it, or if there's a more correct
> way to do what I'm doing:
>
> #+begin-src bash
> if [ -n "${GUIX_ENVIRONMENT}" ]; then
> export
> XDG_CONFIG_DIRS="${GUIX_ENVIRONMENT}/etc:${XDG_CONFIG_DIRS}" export
> XDG_DATA_DIRS="${GUIX_ENVIRONMENT}/share:${XDG_DATA_DIRS}" export
> PATH="${GUIX_ENVIRONMENT}/bin:${PATH}" export
> PATH="${GUIX_ENVIRONMENT}/sbin:${PATH}" fi
> #+end_src
>
> I hope this helps!
>
> --
> Katherine
>
I think Ambrevar's Lisp REPL page mentions something about sourcing
Bash scripts from Emacs? Maybe?
https://ambrevar.xyz/lisp-repl-shell/index.html
prev parent reply other threads:[~2021-12-12 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 10:44 Loading Common Lisp Libraries with GNU/Guix in a REPL jgart
2021-12-10 10:54 ` jgart
2021-12-10 15:03 ` Edouard Klein
2021-12-12 17:01 ` Katherine Cox-Buday
2021-12-12 19:27 ` raingloom [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211212202716.089695f9@riseup.net \
--to=raingloom@riseup.net \
--cc=cox.katherine.e@gmail.com \
--cc=edou@rdklein.fr \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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).