GNU bug report logs - #54079
29.0.50; Method dispatching eratically fails

Previous Next

Package: emacs;

Reported by: Michael Heerdegen <michael_heerdegen <at> web.de>

Date: Mon, 21 Feb 2022 00:14:02 UTC

Severity: normal

Found in version 29.0.50

Done: Alan Mackenzie <acm <at> muc.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Alan Mackenzie <acm <at> muc.de>
Cc: John Wiegley <jwiegley <at> gmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>, 54079 <at> debbugs.gnu.org, Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Subject: bug#54079: 29.0.50; Method dispatching eratically fails
Date: Wed, 16 Mar 2022 02:44:07 +0100
Alan Mackenzie <acm <at> muc.de> writes:

> OK.  So the longer I hear nothing from you, the better.  ;-)  Thanks!

Hope is was long enough :-)

I now tried to debug the other thing that is still happening for me -
failing compilation with async-bytecomp.el when updating packages with
M-x list-packages (I CC the maintainers).

In my currently running session I get

#+begin_src emacs-lisp
(async-inject-variables "\\`\\(?:load-path\\'\\|byte-\\)")
  ==>
  (setq byte-set-marker 147 byte-optimize--dynamic-vars
        '(#<symbol magit-log-margin at 854429>
          #<symbol magit-status-mode-map at 854375> ...)
        ...)
#+end_src

These symbols with position in that sexp seem to be the, or one, cause
of the trouble.  The symbols directly come from a `mapatoms' call, and
AFAIK this sexp is then `print'ed and sent to another emacs process,
where it causes a `read' error.

What has to be done to fix this one?

TIA,

Michael.




This bug report was last modified 3 years and 67 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.