From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Multibyte and unibyte file names Date: Fri, 25 Jan 2013 17:28:40 -0500 Message-ID: References: <83ehhbn680.fsf@gnu.org> <83wqv2ldk1.fsf@gnu.org> <83obgel94c.fsf@gnu.org> <83k3r1lnlb.fsf@gnu.org> <83vcalj97s.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1359152948 31071 80.91.229.3 (25 Jan 2013 22:29:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Jan 2013 22:29:08 +0000 (UTC) Cc: kzhr@d1.dion.ne.jp, michael.albinus@gmx.de, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 25 23:29:27 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tyrm2-0007qq-SP for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2013 23:29:26 +0100 Original-Received: from localhost ([::1]:34117 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tyrll-00089K-9k for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2013 17:29:09 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:51764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tyrlf-000893-MX for emacs-devel@gnu.org; Fri, 25 Jan 2013 17:29:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tyrld-0000Om-Vu for emacs-devel@gnu.org; Fri, 25 Jan 2013 17:29:03 -0500 Original-Received: from smtp205.alice.it ([82.57.200.101]:57961) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tyrla-0000ON-9F; Fri, 25 Jan 2013 17:28:58 -0500 Original-Received: from fmsmemgm.homelinux.net (82.107.57.105) by smtp205.alice.it (8.6.058.01) id 50AA072A0A349839; Fri, 25 Jan 2013 23:28:44 +0100 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id EF870AE194; Fri, 25 Jan 2013 17:28:40 -0500 (EST) In-Reply-To: <83vcalj97s.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Jan 2013 22:31:19 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 82.57.200.101 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156639 Archived-At: > What I meant was to return decoded file names from all file-name > primitives, such as file-name-nondirectory, even if their input was > encoded. It's probably OK to do that, but I wonder why we'd need to do it: under what circumstances could such a primitive receive an encoded file-name, if all the file names returned to Elisp (by things like directory-files) are already decoded? >> Which is why I suggest to decode right away in the functions that return >> file names (e.g. directory-files). > We already do that, so there's no issue in that department. Good. > The issue is in the file-name primitives that want to support both > encoded and decoded file names, and as I understand from this > discussion, this feature should stay. Of course, we shouldn't just reject encoded filenames, but I don't see why we should worry too much about them. > So some things will never work with encoded file names, but I guess no > one cares, because most of those problems go away if the encoding is > UTF-8. Fine; if no one cares, neither do I. Actually, even with other coding systems, this shouldn't be a serious issue since encoded file names should be rare. Stefan