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: Thu, 24 Jan 2013 19:06:56 -0500 Message-ID: References: <83ehhbn680.fsf@gnu.org> <83wqv2ldk1.fsf@gnu.org> <83obgel94c.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1359072459 28985 80.91.229.3 (25 Jan 2013 00:07:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Jan 2013 00:07:39 +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 01:07:56 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 1TyWpo-000470-Dq for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2013 01:07:56 +0100 Original-Received: from localhost ([::1]:35959 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TyWpW-0005Zi-O5 for ged-emacs-devel@m.gmane.org; Thu, 24 Jan 2013 19:07:38 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:50678) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TyWpT-0005Zb-Oz for emacs-devel@gnu.org; Thu, 24 Jan 2013 19:07:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TyWpR-0004FG-8F for emacs-devel@gnu.org; Thu, 24 Jan 2013 19:07:35 -0500 Original-Received: from smtp207.alice.it ([82.57.200.103]:59633) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TyWpF-0004Dg-Ok; Thu, 24 Jan 2013 19:07:21 -0500 Original-Received: from fmsmemgm.homelinux.net (82.107.57.105) by smtp207.alice.it (8.6.060.12) id 51011B060036D1DE; Fri, 25 Jan 2013 01:06:58 +0100 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id CBB9FAE4CE; Thu, 24 Jan 2013 19:06:56 -0500 (EST) In-Reply-To: <83obgel94c.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Jan 2013 20:38:11 +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.103 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:156627 Archived-At: >> > So you are saying that each primitive should detect unibyte file names >> > it gets as arguments and DECODE_FILE them right away? >> I think not: I was talking about decoding the file names *returned* >> by primitives. > What would be the difference, from the POV of the callers of the > primitives? 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 there is no difference, what I suggested is easier to implement, > because it eliminates the need to test whether a given file name is > multibyte (and needs to be encoded) or not, before handing the file > names to system APIs. I don't see why it eliminates this need: file-exists-p can still be called with multibyte and unibyte strings. Stefan