From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rgm@gnu.org, 15803@debbugs.gnu.org
Subject: bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days?
Date: Fri, 11 Sep 2020 14:05:26 +0300 [thread overview]
Message-ID: <83h7s4h8uh.fsf@gnu.org> (raw)
In-Reply-To: <87imck1t1g.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 11 Sep 2020 12:55:55 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rgm@gnu.org, 15803@debbugs.gnu.org
> Date: Fri, 11 Sep 2020 12:55:55 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> All the tools under Linux are so utf-8-focused these days... let's
> >> see... I first, under a utf-8 locale created the directory "émacs",
> >> then converted it to 8859-1:
> >
> > No, please create the directory with non-ASCII name _after_ switching
> > the locale to Latin-1.
>
> Shouldn't the result be the same? I.e., a name with iso-8859-1 name?
No, because the Linux file I/O APIs are encoding-agnostic, they will
(AFAIK) create the directory with a name that is the exact byte stream
that you type at the mkdir command (or at the Emacs make-directory).
> The reason I did it this convoluted name was just that I couldn't
> convince my system to make a 8859 name even after changing the locale.
> That is, when I typed Alt-gr ' e, my terminal still sent over two bytes
> (i.e., in utf-8) instead of a single-byte é.
Try doing this in Emacs, and use one of the Latin input methods if the
keyboard doesn't cooperate.
> 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?
> The tests that were failing all talked about "chmod" and stuff, so I'm
> guessing they were from a sub shell, and my system is apparently forcing
> all new shells to use UTF-8...
Really? So there's no way to change the locale to something
non UTF-8?
> make check:
>
> >>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.elcgtybBC"))
>
> 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.
> So it looks like the patch set has problems, and needs further fixes.
> (Or "make check" has some problems here, since Emacs otherwise seems to
> work fine.)
We could also just install the changes and wait for bug reports, on
the assumption that the problems you see aren't real. Your call.
next prev parent reply other threads:[~2020-09-11 11:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 18:45 bug#15803: default-file-name-coding-system: utf-8 better than latin-1 these days? Glenn Morris
2017-12-01 1:52 ` Glenn Morris
2017-12-01 7:54 ` Eli Zaretskii
2017-12-05 0:35 ` Glenn Morris
2017-12-08 9:46 ` Eli Zaretskii
2017-12-12 1:38 ` Glenn Morris
2020-09-09 13:15 ` Lars Ingebrigtsen
2020-09-09 15:00 ` Eli Zaretskii
2020-09-10 13:07 ` Lars Ingebrigtsen
2020-09-10 14:39 ` Eli Zaretskii
2020-09-11 10:55 ` Lars Ingebrigtsen
2020-09-11 11:05 ` Eli Zaretskii [this message]
2020-09-11 11:27 ` Lars Ingebrigtsen
2020-09-11 12:24 ` Eli Zaretskii
2020-09-11 12:33 ` Lars Ingebrigtsen
2020-09-11 12:41 ` Eli Zaretskii
2020-09-11 14:18 ` Lars Ingebrigtsen
2020-09-11 14:27 ` Lars Ingebrigtsen
2020-09-11 14:46 ` Eli Zaretskii
2020-09-11 14:54 ` Lars Ingebrigtsen
2020-09-11 15:11 ` Eli Zaretskii
2020-09-12 8:47 ` Michael Albinus
2020-09-12 11:21 ` Lars Ingebrigtsen
2020-09-11 12:39 ` Lars Ingebrigtsen
2020-09-11 12:45 ` Eli Zaretskii
2020-09-09 13:33 ` Stefan Kangas
2020-09-09 15:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h7s4h8uh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15803@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.