From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: defun.foo@proton.me, 56643@debbugs.gnu.org,
Andrea Corallo <akrl@sdf.org>
Subject: bug#56643: 29.0.50; Help-mode bookmarks not loading with native compilation
Date: Thu, 21 Jul 2022 00:47:30 +0200 [thread overview]
Message-ID: <87sfmvtn99.fsf@web.de> (raw)
In-Reply-To: <83a693lhms.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Jul 2022 22:16:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> (help-setup-xref
> (list (lambda (function buffer)
> (let ((describe-function-orig-buffer
> (if (buffer-live-p buffer) buffer)))
> (describe-function function)))
> function describe-function-orig-buffer)
> (called-interactively-p 'interactive))
>
> In a natively-compiled Emacs, this lambda produces a native-compiled
> subr. Is there a way of telling Emacs not to produce such a subr, but
> instead to produce byte-code for this lambda? If yes, that could be a
> (somewhat ugly) workaround in this case.
Alternatively we could introduce a named helper function. Note there
are more calls of `help-setup-xref' using lambdas in arguments.
I see a more general problem: anywhere where printing an anonymous
function readably is necessary there is a potential breakage when using
natively compiled Emacs - right? That would be quite a limitation.
Michael.
next prev parent reply other threads:[~2022-07-20 22:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:45 bug#56643: 29.0.50; Help-mode bookmarks not loading with native compilation defun.foo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-19 16:49 ` Eli Zaretskii
2022-07-19 22:22 ` defun.foo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 9:51 ` Andrea Corallo
2022-07-20 11:21 ` Andrea Corallo
2022-07-20 11:45 ` Eli Zaretskii
2022-07-20 18:31 ` Andrea Corallo
2022-07-20 19:16 ` Eli Zaretskii
2022-07-20 22:47 ` Michael Heerdegen [this message]
2022-07-21 5:13 ` Eli Zaretskii
2022-07-21 10:01 ` defun.foo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-21 12:33 ` Eli Zaretskii
2022-07-22 13:40 ` Eli Zaretskii
2022-07-22 13:41 ` Andrea Corallo
2022-07-22 14:40 ` Eli Zaretskii
2022-07-23 9:57 ` Eli Zaretskii
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=87sfmvtn99.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=56643@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=defun.foo@proton.me \
--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 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).