unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Ryan Prior <rprior@protonmail.com>, 55013@debbugs.gnu.org
Subject: bug#55013: Guix-emacs doesn't work
Date: Fri, 22 Apr 2022 07:27:22 +0200	[thread overview]
Message-ID: <87o80tvgat.fsf@gnu.org> (raw)
In-Reply-To: <871qxqjzau.fsf@xelera.eu> (Giovanni Biscuolo's message of "Thu,  21 Apr 2022 16:17:45 +0200")

Giovanni Biscuolo writes:

Hi!

> I was able to solve.

Great!

> I repeat, I'm using emacs-guix on a foreing distro, I don't know if on
> Guix System this workaround is not needed.

I'm on Guix System and emacs-guix's command line completion hasn't
worked for me for about a year.  Starting an emacs shell and typing
"guix TAB", I got

    Starting Guix REPL ... [5 times]
    guix-geiser-eval: Error in evaluating guile expression: ice-9/boot-9.scm:1685:16: In procedure raise-exception:
    /home/janneke/.config/guix/current/share/guile/site/3.0/guix/scripts/deploy.scm:169:7: Unknown # object: "#~"

    Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
    scheme@(emacs-guix) [1]> 

> The most similar upstream bug is this one:
> https://gitlab.com/emacs-guix/emacs-guix/-/issues/23
>
> In that thread Adam Porter points to this comment that explains how to
> start Guix REPL instead of Guile REPL, from emacs-guix:
> https://gitlab.com/emacs-guix/emacs-guix/-/issues/19#note_559028370
>
> (with-eval-after-load 'guix-repl
>     (setq guix-guile-program  '("guix" "repl")
>           guix-config-scheme-compiled-directory  nil
>           guix-repl-use-latest  nil
>           guix-repl-use-server  nil))
>
> Evaluating the above code /before/ starting any emacs-guix command (thus
> before starting Guile REPL) all is working well now!

This sort-of works for me, i.e., typing "guix TAB" in an emacs shell
buffer no longer gives this error...but there also are no completions.

My ~/.emacs/init_bash.sh is empty and I seem to remember having
something there?

Greetings,
Janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com




  reply	other threads:[~2022-04-22  5:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 23:46 bug#55013: Guix-emacs doesn't work Ryan Prior via Bug reports for GNU Guix
2022-04-21  9:50 ` Giovanni Biscuolo
2022-04-21 14:17   ` Giovanni Biscuolo
2022-04-22  5:27     ` Jan Nieuwenhuizen [this message]
2022-04-27  9:13       ` Giovanni Biscuolo
2022-04-27  9:16     ` Giovanni Biscuolo
2023-03-20 19:09 ` Ricardo Wurmus
2023-03-22  6:51   ` Giovanni Biscuolo
2023-03-23 13:32   ` Giovanni Biscuolo
2023-03-23 14:10     ` Giovanni Biscuolo
2023-03-23 14:11     ` Giovanni Biscuolo
2023-03-23 16:31       ` Ricardo Wurmus
2023-03-23 17:06         ` Giovanni Biscuolo
2023-03-25 21:00   ` Ryan Prior via Bug reports for GNU Guix
2023-03-25 22:46     ` Ricardo Wurmus

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=87o80tvgat.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=55013@debbugs.gnu.org \
    --cc=g@xelera.eu \
    --cc=rprior@protonmail.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).