From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: 63564@debbugs.gnu.org
Cc: Jimmy Yuen Ho Wong <wyuenho@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Andrea Corallo <akrl@sdf.org>
Subject: bug#63564: 29.0.91; (setcdr) behaves differently between natively and byte compiled code
Date: Thu, 18 May 2023 09:01:00 +0200 [thread overview]
Message-ID: <F2C82D31-4DFA-4D5D-BB95-A9904CA72EC8@gmail.com> (raw)
In-Reply-To: <m2jzx64b13.fsf@MobileCat.localdomain>
> Users have discovered there's a markdown-mode function that behaves
> differently depending Emacs is executing byte-compiled code or natively
> compiled code.
>
> The issue is documented
> [here](https://github.com/jrblevin/markdown-mode/issues/578).
>
> There are two examples in the issue that will produce an `Wrong type
> argument: consp, nil` error on the natively compiled version of
> `markdown-imenu-create-nested-index`, but not the byte-compiled or
> interpreted version. A user has provided a disassembly of the natively
> compiled code for that function.
>
> The last user has said and I can confirm the offending line seems to be `(setcdr
> sibling-alist alist)` in that function.
>
> Much appreciate it if Andrea could take a look.
I'm not Andrea, but it appears that a related coding error was fixed in a recent commit to markdown-mode, 44f0e89534. Did that help?
prev parent reply other threads:[~2023-05-18 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 2:40 bug#63564: 29.0.91; (setcdr) behaves differently between natively and byte compiled code Jimmy Yuen Ho Wong
2023-05-18 6:50 ` Eli Zaretskii
2023-05-18 7:54 ` Andrea Corallo
2023-05-18 17:45 ` Jimmy Wong
2023-05-18 18:01 ` Mattias Engdegård
2023-05-18 18:58 ` Jimmy Wong
2023-05-18 18:25 ` Eli Zaretskii
2023-05-18 7:01 ` Mattias Engdegård [this message]
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=F2C82D31-4DFA-4D5D-BB95-A9904CA72EC8@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=63564@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=monnier@iro.umontreal.ca \
--cc=wyuenho@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).