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 06:36:39 -0500 Message-ID: References: <83ehhbn680.fsf@gnu.org> <83wqv2ldk1.fsf@gnu.org> <83obgel94c.fsf@gnu.org> <83k3r1lnlb.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1359142147 29376 80.91.229.3 (25 Jan 2013 19:29:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Jan 2013 19:29:07 +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 20:29:25 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 1Tyoxi-0005vt-KZ for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2013 20:29:18 +0100 Original-Received: from localhost ([::1]:39629 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TyoxR-00059g-1C for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2013 14:29:01 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:45176) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tyox4-00049F-7C for emacs-devel@gnu.org; Fri, 25 Jan 2013 14:28:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tyox2-000448-Us for emacs-devel@gnu.org; Fri, 25 Jan 2013 14:28:38 -0500 Original-Received: from smtp208.alice.it ([82.57.200.104]:48459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tyox1-00043L-8Q; Fri, 25 Jan 2013 14:28:35 -0500 Original-Received: from fmsmemgm.homelinux.net (82.107.57.105) by smtp208.alice.it (8.6.060.12) id 50FF9F1D0085D65B; Fri, 25 Jan 2013 20:28:31 +0100 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 3CDFEAE4FB; Fri, 25 Jan 2013 06:36:39 -0500 (EST) In-Reply-To: <83k3r1lnlb.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Jan 2013 09:37:52 +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.104 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:156635 Archived-At: >> That the callers get to see meaningful (decoded) names? >> That file-name manipulation functions don't have the side effect of >> encoding/decoding file names? > If we decode unibyte file names at entry to each primitive, before > doing anything else, and thereafter manipulate decoded multibyte > strings, this will happen anyway. I get the impression that we're not talking about the same thing. If you only decode on entry, then Elisp code will first see encoded file names returned by directory-files and will then see them converted to decoded form after passing the result to a file-name manipulation function. Which is why I suggest to decode right away in the functions that return file names (e.g. directory-files). > But since everybody (at least those who spoke) seem to think this is a > w32 only problem, I will solve it for w32 only. I think the specific problems you mentioned are mostly non-issues under POSIX, but the general problem of deciding which representation to use is more general. Stefan