bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57878: Some further investigation


From: Konrad Hinsen
Subject: bug#57878: Some further investigation
Date: Fri, 09 Dec 2022 15:30:17 +0100

Hi everyone,

On the occasion of a "guix pull", I looked into this issue again,
because magit without ido-completing-read+ is less fun.

Loading this package runs lots of compilation threads, but it does
ultimately terminate, with an error:

  Debugger entered--Lisp error: (native-compiler-error (lambda (arg3 &optional 
arg4 arg5) (let ((f #'call-interactively)) (funcall f arg3 arg4 arg5))) 
"Debugger entered--Lisp error: (native-compiler-err...")
    signal(native-compiler-error ((lambda (arg3 &optional arg4 arg5) (let ((f 
#'call-interactively)) (funcall f arg3 arg4 arg5))) "Debugger entered--Lisp 
error: (native-compiler-err..."))
    comp--native-compile((lambda (arg3 &optional arg4 arg5) (let ((f 
#'call-interactively)) (funcall f arg3 arg4 arg5))) nil 
"/home/hinsen/.emacs.d/eln-cache/28.2-16da12a1/subr...")
    comp-trampoline-compile(call-interactively)
    comp-subr-trampoline-install(call-interactively)
    advice--add-function(:around (#f(compiled-function () #<bytecode 
0x32e14019df7e91>) . #f(compiled-function (gv--val) #<bytecode 
0x9f608bbba7cb3c2>)) call-interactively@ido-cr+-record-current-command nil)
    advice-add(call-interactively :around 
call-interactively@ido-cr+-record-current-command)
    
load-with-code-conversion("/gnu/store/abvhh3kcdpbg9vm2jz5q6zqhmfdpr4m7-emacs-..."
 "/gnu/store/abvhh3kcdpbg9vm2jz5q6zqhmfdpr4m7-emacs-..." nil nil)
    load("/gnu/store/abvhh3kcdpbg9vm2jz5q6zqhmfdpr4m7-emacs-...")
    (progn (load "/gnu/store/abvhh3kcdpbg9vm2jz5q6zqhmfdpr4m7-emacs-..."))
    (setq elisp--eval-defun-result (progn (load 
"/gnu/store/abvhh3kcdpbg9vm2jz5q6zqhmfdpr4m7-emacs-...")))
    elisp--eval-defun()
    eval-defun(nil)
    funcall-interactively(eval-defun nil)
    command-execute(eval-defun)

What I notice here is "advice-add". It makes me wonder whether the
problem is perhaps not native-compiling ido-completing-read+, but
native-compiling the ido code that is getting adviced here.

Cheers,
  Konrad.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]