unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Hecker via Bug reports for GNU Guix <bug-guix@gnu.org>
To: calcium <calcium@disroot.org>, 59256@debbugs.gnu.org
Subject: bug#59256: Emacs-guix tab-completion returns gexp error
Date: Mon, 02 Jan 2023 01:29:34 -0600	[thread overview]
Message-ID: <87h6x95r8h.fsf@mailbox.org> (raw)
In-Reply-To: <12c37abe-1c21-dc5f-8b0a-6c6f5c6618af@disroot.org> (calcium@disroot.org's message of "Thu, 15 Dec 2022 13:01:13 +0000")

calcium <calcium@disroot.org> 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 seen below :
>
> ```
> (guix-eval-read
>   "(begin
>    (use-modules (ice-9 format))
>    (format #f \"~s\"
>     help-string))") ;; => "#<procedure help-string commands>"
> ```
>
> but the object that `(help-string)` returns seems incompatible with guile's own repl/shell ....
>
> The solution might be to just change the `help-string` procedure to
> return another kind of object, or to fix guile's repl/shell for that
> kind of object.

Im certain it's not anyone procedure, but rather the internal repl being in a
socket file. I dont know how guile is handling sockets, but guile
(socketed) cant read '#' for some reason.

The next step might be going to the guile mailing list and getting some
answers there, cause guile has nil for documentation and I have come up
empty handed in looking for any answers for guile socket files. Either way, I
think emacs-guix is important enough to get this fix, so will do.

Stay safe,
-Joshua




      reply	other threads:[~2023-01-02  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 22:16 bug#59256: Emacs-guix tab-completion returns gexp error Joshua Hecker via Bug reports for GNU Guix
2022-11-26 20:45 ` Joshua Hecker via Bug reports for GNU Guix
2023-01-03 22:25   ` Maxime Devos
2023-03-22  6:10     ` Joshua Hecker via Bug reports for GNU Guix
2023-04-05 12:36       ` Maxime Devos
2022-12-15 13:01 ` calcium via Bug reports for GNU Guix
2023-01-02  7:29   ` Joshua Hecker via Bug reports for GNU Guix [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=87h6x95r8h.fsf@mailbox.org \
    --to=bug-guix@gnu.org \
    --cc=59256@debbugs.gnu.org \
    --cc=calcium@disroot.org \
    --cc=joshua0609@mailbox.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.
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).