From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: 50045@debbugs.gnu.org
Subject: [bug#50045] [André A. Gomes] [PATCH] Documentation fix
Date: Fri, 21 Jan 2022 21:41:01 +0100 [thread overview]
Message-ID: <87ee50stya.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87v8yc9aeb.fsf@gmail.com> ("André A. Gomes"'s message of "Fri, 21 Jan 2022 22:06:04 +0300")
Hello,
André A. Gomes <andremegafone@gmail.com> writes:
> This is still an issue, despite the recent updates. I'm still as
> baffled as I was when I reported. How could I investigate this further?
> Thanks.
>
> Let me restate the issue for the sake of clarity.
>
> Write the s-exp below to a file, let's call it test-emacs-guix.el.
>
> --8<---------------cut here---------------start------------->8---
> (with-eval-after-load 'geiser-guile
> (add-to-list 'geiser-guile-load-path "~/path/to/guix/checkout/"))
> --8<---------------cut here---------------end--------------->8---
>
> --8<---------------cut here---------------start------------->8---
> $ emacs -nw -q -l test-emacs-guix.el
> --8<---------------cut here---------------end--------------->8---
>
> M-x guix RET p ; n. The Guix REPL raises the error mentioned in my
> previous message.
FWIW, I cannot reproduce it. With the command above, I get a prompt in
the minibuffer, without an error.
> When I change the path to /home/$USER/path/to/guix/checkout, the REPL is
> successfully started.
Have you tried to contact Geiser's author? They may have at least a clue
about this.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2022-01-21 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:02 [bug#50045] [André A. Gomes] [PATCH] Documentation fix André A. Gomes
2022-01-15 22:04 ` Nicolas Goaziou
2022-01-21 19:06 ` André A. Gomes
2022-01-21 20:41 ` Nicolas Goaziou [this message]
2022-02-11 19:36 ` André A. Gomes
2023-11-02 9:45 ` bug#50045: Update André A. Gomes
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee50stya.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=50045@debbugs.gnu.org \
--cc=andremegafone@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.