From: Brett Gilio <brettg@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: ABI and emacs-guix
Date: Fri, 26 Apr 2019 09:53:24 -0500 [thread overview]
Message-ID: <87v9z0yg0r.fsf@posteo.net> (raw)
In-Reply-To: <871s1pnow9.fsf@gnu.org>
Ludovic Courtès writes:
> Hi Brett,
>
> Brett Gilio <brettg@posteo.net> skribis:
>
>> Was there another ABI change to Guix? The last time this happened
>> emacs-guix began behaving improperly and spitting out unresolvable error
>> messages in the *Messages* buffer. This is happening again, and Ludo
>> fixed it by rebuilding it I think?
>
> Can you share those terrible error messages?
>
> As I write this, Emacs-Guix works awesomely fine for me. :-)
>
>> If this is the case, is there a consistent way to have emacs-guix be
>> rebuilt after these changes?
>
> I haven’t checked how Emacs-Guix spawns its REPL server, but I think
> that to be safe, it should spawn it via ‘guix repl’, which is
> guaranteed to be using the right APIs and all.
>
> Thanks,
> Ludo’.
Hey Ludo,
Thank you for picking this up again.
Here is the *Messages* with an attached backtrace from *Guix
Internal Repl*
guix-geiser-eval: Error in evaluating guile expression: texinfo.scm:745:27: Throw to key `parser-error' with args `(#<input: string 2c63e70> "EOF while reading a token " "reading char data")'.
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(emacs-guix)> ,bt
12 (eval (#<procedure 2767780 at <unknown port>:19:16 ()>) #)
In emacs-guix/packages.scm:
790:23 11 (package/output-sexps _ output _ _ (synopsis installed …))
In guix/discovery.scm:
179:3 10 (fold-module-public-variables _ _ _)
In guix/combinators.scm:
45:26 9 (fold2 #<procedure 3fb7c40 at guix/discovery.scm:179:1…> …)
45:26 8 (fold2 #<procedure 3d58ce0 at guix/discovery.scm:180:1…> …)
In guix/discovery.scm:
182:33 7 (_ #<package bubblewrap@0.3.1 gnu/packages/virtualizat…> …)
In emacs-guix/packages.scm:
338:23 6 (_ #<package bubblewrap@0.3.1 gnu/packages/virtualizat…> …)
369:22 5 (_ _)
In guix/ui.scm:
1271:23 4 (texi->plain-text _)
In texinfo.scm:
1131:22 3 (parse _)
979:31 2 (loop #<input: string 2c63e70> (*fragment*) _ _ _)
910:31 1 (loop #<input: string 2c63e70> #f #<procedure identity…> …)
745:27 0 (_ #<input: string 2c63e70> #f #f #<procedure 7fb98357…> …)
scheme@(emacs-guix) [1]>
Here is my `guix describe'.
Generation 95 Apr 26 2019 09:38:14 (current)
guix-system e29665d
repository URL: https://git.sr.ht/~brettgilio/guix-channel
branch: master
commit: e29665df7da5d4472896d28da6a3fe7d71487866
guix 272db5b
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 272db5bcf53d9d05d5c4b2df021d9e74f78866cd
next prev parent reply other threads:[~2019-04-26 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 21:18 ABI and emacs-guix Brett Gilio
2019-04-26 8:37 ` Ludovic Courtès
2019-04-26 14:53 ` Brett Gilio [this message]
2019-04-27 17:37 ` Brett Gilio
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=87v9z0yg0r.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).