From: Lars Ingebrigtsen <larsi@gnus.org>
To: 50839@debbugs.gnu.org
Cc: Andrea Corallo <akrl@sdf.org>
Subject: bug#50839: 28.0.50; Odd things in comp-ctxt doc string
Date: Mon, 27 Sep 2021 08:58:30 +0200 [thread overview]
Message-ID: <87mtnymrmx.fsf@gnus.org> (raw)
I saw that compiling with native-comp warned about a too-long doc
string, but looking at comp-ctxt-byte-func-to-func-h, it's not too long:
(byte-func-to-func-h (make-hash-table :test #'equal) :type hash-table
:documentation "byte-function -> comp-func.
Needed to replace immediate byte-compiled lambdas with the compiled reference.")
But looking at the actual help buffer, I get the stuff below.
It looks like bits of the doc strings have been replaced with... odd
things? "lambdas" is now "lamcomp-func.dbdas". And also the
"byte-funCL-X.ction" thing. I haven't debugged any further; perhaps
it's obvious to someone what's going on. (I've added Andrea to the CCs.)
comp-ctxt-byte-func-to-func-h is a native compiled Lisp function in
‘comp.el’.
(comp-ctxt-byte-func-to-func-h CL-X)
Access slot "byte-func-to-func-h" of ‘comp-ctxt’ struct
byte-funCL-X.ction ->
Needed to replace immediate byte-compiled lamcomp-func.bdas with the compiled reference.
This function has a compiler macro ‘comp-ctxt-byte-func-to-func-h--cmacro’.
This function does not change global state, including the match data.
In GNU Emacs 28.0.50 (build 23, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
of 2021-09-26 built on elva
Repository revision: 43ae8c828d853382bbc2a27b9e14b9fff6ba18b6
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux 11 (bullseye)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next reply other threads:[~2021-09-27 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 6:58 Lars Ingebrigtsen [this message]
2021-09-27 7:00 ` bug#50839: 28.0.50; Odd things in comp-ctxt doc string Lars Ingebrigtsen
2021-09-27 9:51 ` Stefan Kangas
2021-09-28 5:21 ` Lars Ingebrigtsen
2021-09-28 12:28 ` Stefan Kangas
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=87mtnymrmx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50839@debbugs.gnu.org \
--cc=akrl@sdf.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).