[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15803: default-file-name-coding-system: utf-8 better than latin-1 th
From: |
Lars Ingebrigtsen |
Subject: |
bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days? |
Date: |
Fri, 11 Sep 2020 13:27:28 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> But I think I know why "make check" was failing:
>>
>> [larsi@stories ~/src/emacs/trunk]$ echo $LANG
>> sv_SE.ISO-8859-1
>> [larsi@stories ~/src/emacs/trunk]$ echo $LANG
>> en_US.UTF-8
>
> I don't understand this: 2 identical commands one after the other
> yield different results?
Sorry, there was a "bash" started in between there.
>> This time over, the directory is "fóo" (in latin-1), and that looks like
>> Emacs is trying to find the utf-8 version of the file name.
>
> If that's the case, then we lack ENCODE_FILE (or more generally don't
> encode a file name) somewhere.
After instrumenting bytecomp (i.e., adding a bunch of messages), I see
what function is actually failing. With this in byte-compile-file:
(message "foo2: %S" (prin1-to-string tempfile))
(unless (= temp-modes desired-modes)
(set-file-modes tempfile desired-modes 'nofollow))
(message "foo1: %S" (prin1-to-string tempfile))
I get this output:
make[1]: Entering directory '/home/larsi/src/emacs/f�o/test'
ELC lisp/eshell/eshell-tests.elc
foo2: "#(\"/home/larsi/src/emacs/fóo/test/lisp/eshell/eshell-tests.elcnjDFYY\"
0 65 (charset iso-8859-1))"
>>Error occurred processing lisp/eshell/eshell-tests.el: File is missing
>>(("Doing chmod" "No such file or directory"
>>"/home/larsi/src/emacs/f\303\263o/test/lisp/eshell/eshell-tests.elcnjDFYY"))
make[1]: *** [Makefile:165: lisp/eshell/eshell-tests.elc] Error 1
So it's created a tempfile, tagged with the correct charset (I had no
idea that that's how it worked), but decoded, and then set-file-modes
interprets that as an UTF-8 file name.
So... it's a bug in set-file-modes? Hm, nope, write-region has the
same problem.
That weird file name (decoded and tagged with a charset text parameter)
comes from make-temp-file -- everything seems to be OK before that.
target-file is:
foo: "\"/home/larsi/src/emacs/f\\363o/test/lisp/eshell/eshell-tests.elc\""
which seems to be correct, but
(tempfile
(make-temp-file (expand-file-name target-file)))
is
"#(\"/home/larsi/src/emacs/fóo/test/lisp/eshell/eshell-tests.elcnjDFYY\" 0 65
(charset iso-8859-1))"
and then things fail. Which makes me wonder why building Emacs at all
works if it's such a fundamental problem... Just to check whether my
system is switching the LANG back to utf-8:
(message "foo: %S" (getenv "LC_ALL"))
in byte-compile-file says
foo: "sv_SE.ISO-8859-1"
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/09
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/09
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/10
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/10
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?,
Lars Ingebrigtsen <=
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Eli Zaretskii, 2020/09/11
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Michael Albinus, 2020/09/12
- bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?, Lars Ingebrigtsen, 2020/09/12