Maxime Devos writes:
Sorry for getting back to you so late, life got in the way, work and
setting up my POWER9 machine :). But I still hope you can provide some
wisdom.
> I've heard about something about Guile sockets and REPLs, so I've
> investigated a bit and I think I found a Guix bug instead
calcium writes:
> The problem can be tracked back from elisp procedure
> `guix-pcomplete-search-in-help` in guix-pcomplete.el to
> `guix-help-string` in guix-misc.el, to this problematic code :
>
> ```
> (guix-eval-read "(help-string )")
> ```
>
>
> The procedure help-string exists, as can be see
To Guix,
Just following up for the record, turning (setq guix-repl-use-server
nil) does fix the reading issue. For whats it worth at least we can
safely say it with how sockets (at least in for guile) handle gexp.
I will investigate further with do time.
stay safe,
-Joshua
To Guix,
Emacs-guix tab-completion or M-x guix-command returns:
Error in evaluating guile expression: ice-9/boot-9.scm:1685:16: In procedure
raise-exception:
/home/crono/.config/guix/current/share/guile/site/3.0/guix/scripts/deploy.scm:177:7:
Unknown # object: "#~"
Entering a new prompt. Type