From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem Date: Mon, 25 Feb 2008 22:41:08 -0500 Message-ID: <87pruk9ygb.fsf@stupidchicken.com> References: <877igvl4dn.fsf@stupidchicken.com> <47C180F9.2060901@gnu.org> <47C2014A.4090702@gnu.org> <47C35614.6020407@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1203997385 28297 80.91.229.12 (26 Feb 2008 03:43:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 Feb 2008 03:43:05 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org, rms@gnu.org, Jason Rumney To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 26 04:43:30 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JTqj3-0003dW-Ad for ged-emacs-devel@m.gmane.org; Tue, 26 Feb 2008 04:43:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTqiX-0005xw-HT for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2008 22:42:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JTqiT-0005xa-UO for emacs-devel@gnu.org; Mon, 25 Feb 2008 22:42:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JTqiS-0005vo-4i for emacs-devel@gnu.org; Mon, 25 Feb 2008 22:42:53 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTqiS-0005vl-1Q for emacs-devel@gnu.org; Mon, 25 Feb 2008 22:42:52 -0500 Original-Received: from cyd.mit.edu ([18.115.2.24]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JTqiG-0001kZ-97; Mon, 25 Feb 2008 22:42:40 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id D129D4E3F9; Mon, 25 Feb 2008 22:41:08 -0500 (EST) In-Reply-To: (Stefan Monnier's message of "Mon\, 25 Feb 2008 20\:57\:47 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.91 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:90473 Archived-At: Stefan Monnier writes: >> Here is a patch against EMACS_22_BASE. > > I'd rather use a less arbitrary scheme. E.g. > - only accept unchanged safe chars (rather than rule out > dangerous ones), e.g. [:alnum:] and maybe a couple more. > - everything else encoded following quoted-printable. > > Of course, QP applies to bytes, not to chars, which also points to > a potential problem with [:alnum:] since it includes multibyte chars > which may also be rejected, but I think that would be safe enough for > a start. What do you mean by quoted-printable? I was thinking that we could instead change all unsafe chars into the same character, e.g. an underscore. I don't think there is much risk of name clashing (in the first place, we already use make-temp-file to generate a unique filename.)