ABI and emacs-guix

ABI and emacs-guix

[Brett Gilio]

Hi all,

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?

If this is the case, is there a consistent way to have emacs-guix be
rebuilt after these changes?

Best,
Brett Gilio

Re: ABI and emacs-guix

[Ludovic Courtès]

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

Re: ABI and emacs-guix

[Brett Gilio]

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

Re: ABI and emacs-guix

[Brett Gilio]

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

After pulling updates today, the issue is fixed on my end.