GNU bug report logs -
#48029
28.1; [native-comp] Function names with non-ascii characters
Previous Next
Reported by: jakanakaevangeli <at> chiru.no
Date: Mon, 26 Apr 2021 08:49:02 UTC
Severity: normal
Tags: confirmed
Found in version 28.1
Done: Andrea Corallo <acorallo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: larsi <at> gnus.org, 48029 <at> debbugs.gnu.org, jakanakaevangeli <at> chiru.no
> Date: Fri, 08 Jul 2022 13:43:15 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> > Why do we have ";; -*-coding: nil; -*- "? I think that's the problem:
> >> > it should be ";; -*-coding: utf-8; -*- " instead. Where does the nil
> >> > come from?
> >>
> >> AFAIR at the time we encountered a situation when one of these files was
> >> read back with some other encoding (I guess it's heuristic?) so fixing
> >> the encoding to nil solved the issue.
> >
> > You mean, bug#45433?
>
> Yes that's the one.
>
> > If the problem is EOL conversion, using
> > utf-8-unix instead of utf-8 should take care of that. Or maybe even
> > use utf-8-emacs-unix.
>
> Will utf-8-unix or utf-8-emacs-unix work on every OS?
Yes.
> If yes which one would you recommend we use?
The latter, I think.
> > Are we likely to write bytecode into this temporary file?
>
> Yes definitely
OK, then I think utf-8-emacs-unix it is.
> >> Should this patch go in master or into the release branch?
> >
> > To the release branch, if Lars agrees. But let's first try to see if
> > bug#45433 is not back after the above change.
>
> I can't see the test failing even removing the original fix so probably
> some of the code in Emacs that is leveraged changed. This also suggests
> the test is not really useful anymore (I'll double check and remove it).
OK, thanks.
This bug report was last modified 1 year and 353 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.