From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
48029@debbugs.gnu.org, jakanakaevangeli@chiru.no
Subject: bug#48029: 28.1; [native-comp] Function names with non-ascii characters
Date: Thu, 07 Jul 2022 19:47:32 +0200 [thread overview]
Message-ID: <87bku0g6h7.fsf@gnus.org> (raw)
In-Reply-To: <xjfa69lqoy5.fsf@ma.sdf.org> (Andrea Corallo's message of "Thu, 07 Jul 2022 08:58:26 +0000")
Andrea Corallo <akrl@sdf.org> writes:
>>> >>>> Visit it and M-x emacs-lisp-native-compile-and-load.
>>> >>>> A function called "nonascii-test-žžž" will be defined.
[...]
> the place where the C function name is generated is `comp-c-func-name'
> at comp.el:1175.
>
> ATM I'm not 100% sure the fix limited to this tho.
This isn't about the C function name, though -- the problem is that the
Emacs function name is "nonascii-test-žžž" instead of
"nonascii-test-žžž".
Unless the C function name is then later translated back into a
doubly-encoded Lisp function name somehow.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-07 17:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 8:53 bug#48029: 28.1; [native-comp] Function names with non-ascii characters jakanakaevangeli
2021-05-02 8:47 ` Lars Ingebrigtsen
2021-05-02 21:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-30 13:10 ` Lars Ingebrigtsen
2022-07-04 8:51 ` Andrea Corallo
2022-07-04 11:20 ` Eli Zaretskii
2022-07-07 8:58 ` Andrea Corallo
2022-07-07 17:47 ` Lars Ingebrigtsen [this message]
2022-07-07 20:51 ` Andrea Corallo
2022-07-08 5:43 ` Eli Zaretskii
2022-07-08 8:49 ` Andrea Corallo
2022-07-08 12:40 ` Eli Zaretskii
2022-07-08 13:43 ` Andrea Corallo
2022-07-08 13:59 ` Eli Zaretskii
2022-07-08 14:53 ` Andrea Corallo
2022-07-10 12:56 ` Lars Ingebrigtsen
2022-07-10 13:02 ` Eli Zaretskii
2022-07-12 14:24 ` Andrea Corallo
2022-07-12 15:40 ` Eli Zaretskii
2022-07-12 15:46 ` Lars Ingebrigtsen
2022-07-13 13:20 ` Andrea Corallo
2023-06-05 8:50 ` Andrea Corallo
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=87bku0g6h7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48029@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=jakanakaevangeli@chiru.no \
/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).