unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jason Rumney <jasonr@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Chong Yidong <cyd@stupidchicken.com>,
	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 10:39:23 -0500	[thread overview]
Message-ID: <jwvlk5a2wmy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <47C180F9.2060901@gnu.org> (Jason Rumney's message of "Sun, 24 Feb 2008 14:36:41 +0000")

>>> Does anyone here have a vfat/ntfs partition for investigating this bug?
>> 
>> There's no need to investigate, as the problem is clearly evident:
>> Windows-based filesystems don't allow certain characters in file
>> names, and `*' is one of these characters.  So a file name such as
>> `#*scratch*#20913s5z#' is not allowed.
>> 
>> To properly fix such a problem, Emacs needs to know the type of
>> filesystem of a file.  Then we could employ the same technique as the
>> Windows port does now, but conditioned by the filesystem, not the OS.
>> 
>> However, I don't think we have infrastructure for querying the file
>> about its filesystem type, do we?

> Alternatively, we could limit the filenames we generate for autosaving the
> scratch buffer (and any others like it) to use characters that are valid on
> all the filesystems we know about.

That's indeed what we should do.  If and when we ever get support for
filesystem-knowledge in the code, we may revisit this choice, but for
now, please someone change the code that auto-generates those filenames
to avoid characters known to be problematic.  Or better yet: to only
use those chars expected to be always work.


        Stefan




  reply	other threads:[~2008-02-24 15:39 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 [this message]
2008-02-24 15:44       ` Miles Bader
2008-02-24 16:01         ` Jason Rumney
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=jwvlk5a2wmy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    /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).