unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>,
	emacs-devel@gnu.org
Subject: Re: [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem
Date: Sun, 24 Feb 2008 16:01:31 +0000	[thread overview]
Message-ID: <47C194DB.4070206@gnu.org> (raw)
In-Reply-To: <87r6f2cqap.fsf@catnip.gol.com>

Miles Bader wrote:
> Isn't that sort of dangerous?  If Emacs only uses characters which are
> _garanteed_ to work on any no matter how stupid, that would seem to
> dramatically increase the chances of a clash with a real filename...
>   
autosave files and backup files already have that possibility, but noone 
has worried about it in the past.
By avoiding *?<>|" and control characters, we slightly reduce the 
possibilities for file names, but I don't think the chance of a clash 
realistically increases that much, as long as we use some unusual 
characters like # and/or ~ and append the process id or whatever the 
number is we're appending.

Even on filesystems that support them, those characters can be 
problematic for naive users who forget to quote them, so avoiding them 
is a good idea in general.





  reply	other threads:[~2008-02-24 16:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 22:00 [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem Chong Yidong
2008-02-23 22:22 ` Eli Zaretskii
2008-02-23 22:30   ` Chong Yidong
2008-02-23 22:33   ` David Kastrup
2008-02-24  4:16     ` Eli Zaretskii
2008-02-24 14:36   ` Jason Rumney
2008-02-24 15:39     ` Stefan Monnier
2008-02-24 15:44       ` Miles Bader
2008-02-24 16:01         ` Jason Rumney [this message]
2008-02-24 19:44           ` Eli Zaretskii
2008-02-24 20:41         ` Stefan Monnier
2008-02-25 10:57           ` Richard Stallman
2008-02-25 15:57             ` Stefan Monnier
2008-02-26 12:36               ` Richard Stallman
2008-02-24 19:43       ` Eli Zaretskii
2008-02-24 23:04       ` Richard Stallman
2008-02-24 23:44         ` Jason Rumney
2008-02-25 19:01           ` Richard Stallman
2008-02-25 23:58             ` Jason Rumney
2008-02-26  1:57               ` Stefan Monnier
2008-02-26  3:41                 ` Chong Yidong
2008-02-26  4:53                   ` Stefan Monnier
2008-02-26  9:07                   ` Jason Rumney
2008-02-26  9:39                 ` Jason Rumney
2008-02-26 15:18                   ` Stefan Monnier
2008-02-24 22:30     ` Richard Stallman
2008-02-24 15:23   ` Richard Stallman
2008-02-24 20:01     ` Eli Zaretskii
2008-02-25 10:57       ` Richard Stallman
2008-02-25 20:04         ` Eli Zaretskii
2008-02-25 20:52           ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47C194DB.4070206@gnu.org \
    --to=jasonr@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).