From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Mathias Dahl" Newsgroups: gmane.emacs.devel Subject: Re: Problem with non-valid file names on w32 Date: Thu, 30 Nov 2006 18:52:03 +0100 Message-ID: <7dbe73ed0611300952n61414139p5a419d2391edb972@mail.gmail.com> References: <456ED855.9070006@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1164909182 13580 80.91.229.2 (30 Nov 2006 17:53:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 30 Nov 2006 17:53:02 +0000 (UTC) Cc: Lennart Borgman , Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 30 18:52:58 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gpq5D-0007Yy-BX for ged-emacs-devel@m.gmane.org; Thu, 30 Nov 2006 18:52:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gpq5C-00021e-TV for ged-emacs-devel@m.gmane.org; Thu, 30 Nov 2006 12:52:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gpq4w-0001zJ-LD for emacs-devel@gnu.org; Thu, 30 Nov 2006 12:52:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gpq4t-0001xO-Uj for emacs-devel@gnu.org; Thu, 30 Nov 2006 12:52:08 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gpq4s-0001xE-75 for emacs-devel@gnu.org; Thu, 30 Nov 2006 12:52:06 -0500 Original-Received: from [64.233.182.185] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gpq4s-0007Ys-7U for emacs-devel@gnu.org; Thu, 30 Nov 2006 12:52:06 -0500 Original-Received: by nf-out-0910.google.com with SMTP id d4so3340939nfe for ; Thu, 30 Nov 2006 09:52:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=niY5o2LCp3UcnSkynjaE/XI4jo0EcRk4y4Kv6OA+7xL4cml5LsB7J5L/XkgEtDijucCpM0sIOW1OMBZ9G2BbLz2WS/kbKpQCbJ+M3Lm7q5HMoDdrr0HvXMwtfubs4bG7/QBWvyFGq5dBCKqA07LK1UHq3HgN5tlrkTiapvD68Ew= Original-Received: by 10.48.223.10 with SMTP id v10mr5673207nfg.1164909123655; Thu, 30 Nov 2006 09:52:03 -0800 (PST) Original-Received: by 10.49.18.4 with HTTP; Thu, 30 Nov 2006 09:52:03 -0800 (PST) Original-To: "Juanma Barranquero" In-Reply-To: Content-Disposition: inline X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:63145 Archived-At: > If you have shared resources, the rules governing file name validity > could be different in some mounted volumes. How do you plan to say > that to Emacs? Most probably that shared resource would add more restrictions on file names rather than adding possible characters, right? Or is the current file name restrictions in Windows dependent on the file system type? > > It gets a bit worse if you have file names like > > "c:/some/path/d:hidden.txt". In this case Emacs will not complain when > > saving the file. Instead a hidden stream is created. > > That is a feature (if unintended). foo:bar is not an invalid name in > Windows. I agree. That might come handy.