From: Michael Heerdegen <michael_heerdegen@web.de>
To: Alan Mackenzie <acm@muc.de>
Cc: John Wiegley <jwiegley@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
54079@debbugs.gnu.org,
Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#54079: 29.0.50; Method dispatching eratically fails
Date: Wed, 16 Mar 2022 02:44:07 +0100 [thread overview]
Message-ID: <87sfri1xjs.fsf@web.de> (raw)
In-Reply-To: <Yijj+VerXBIJmSYC@ACM> (Alan Mackenzie's message of "Wed, 9 Mar 2022 17:29:29 +0000")
Alan Mackenzie <acm@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.
next prev parent reply other threads:[~2022-03-16 1:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 0:12 bug#54079: 29.0.50; Method dispatching eratically fails Michael Heerdegen
2022-02-21 1:14 ` Michael Heerdegen
2022-03-04 16:12 ` Lars Ingebrigtsen
2022-02-21 3:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 4:21 ` Michael Heerdegen
2022-02-22 23:55 ` Michael Heerdegen
2022-02-23 0:27 ` Michael Heerdegen
2022-02-23 0:47 ` Michael Heerdegen
2022-03-04 2:08 ` Michael Heerdegen
2022-03-04 19:11 ` Alan Mackenzie
2022-03-05 16:37 ` Alan Mackenzie
2022-03-05 17:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 19:00 ` Alan Mackenzie
2022-03-05 23:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 18:19 ` Eli Zaretskii
2022-03-05 19:07 ` Alan Mackenzie
2022-03-06 2:19 ` Michael Heerdegen
2022-03-08 19:28 ` Alan Mackenzie
2022-03-08 19:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 20:48 ` Alan Mackenzie
2022-03-08 21:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 17:42 ` Alan Mackenzie
2022-03-09 18:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 20:32 ` Alan Mackenzie
2022-03-09 22:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-11 22:01 ` Alan Mackenzie
2022-03-12 4:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-13 16:49 ` Alan Mackenzie
2022-03-14 12:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 4:10 ` Michael Heerdegen
2022-03-09 17:29 ` Alan Mackenzie
2022-03-16 1:44 ` Michael Heerdegen [this message]
2022-03-16 11:52 ` Alan Mackenzie
2022-03-16 19:22 ` Michael Heerdegen
2022-03-17 2:58 ` Michael Heerdegen
2022-03-16 19:29 ` Alan Mackenzie
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfri1xjs.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=54079@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=jwiegley@gmail.com \
--cc=larsi@gnus.org \
--cc=thierry.volpiatto@gmail.com \
/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/emacs.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).