From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62498-done@debbugs.gnu.org,
Christos Vagias <chris.actondev@gmail.com>,
Andrea Corallo <akrl@sdf.org>
Subject: bug#62498: 29.0.60; paredit and native-comp issues
Date: Wed, 16 Aug 2023 04:57:19 -0400 [thread overview]
Message-ID: <yp18rab9xg0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1cz2ac6k1.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Mon, 05 Jun 2023 10:44:30 -0400")
Andrea Corallo <acorallo@gnu.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Christos Vagias <chris.actondev@gmail.com>
>>> Date: Mon, 27 Mar 2023 22:41:32 +0200
>>>
>>> I'm experiencing issues in emacs 29 built from source (commit
>>> 08fbc133756) when using paredit.
>>> When native-compilation hasn't yet created the .eln file it's working
>>> fine. When it's natively compiled though I'm having issues such that
>>> (example is when M-x paredit-mode)
>>>
>>> Debugger entered--Lisp error: (void-function toggle)
>>> toggle(toggle #^[nil nil keymap ....
>>> paredit-mode(toggle)
>>> funcall-interactively(paredit-mode toggle)
>>> command-execute(paredit-mode record)
>>> ...
>>
>> Could be bug#61917 again.
>
> Yep probably. Latest paredit is native compiling fine for me ATM.
>
> Christos could you report if you still see the issue or it's fixed for
> you as well?
No feedback was given so I assume the issue is solved. Happy to reopen
if is not the case.
Best Regards
Andrea
prev parent reply other threads:[~2023-08-16 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 20:41 bug#62498: 29.0.60; paredit and native-comp issues Christos Vagias
2023-03-28 12:05 ` Eli Zaretskii
2023-06-05 14:44 ` Andrea Corallo
2023-08-16 8:57 ` Andrea Corallo [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp18rab9xg0.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=62498-done@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=chris.actondev@gmail.com \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.