all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: rms@gnu.org
Cc: eliz@gnu.org, emacs-devel@gnu.org, jasonr@gnu.org,
	cyd@stupidchicken.com, miles@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: Mon, 25 Feb 2008 10:57:20 -0500	[thread overview]
Message-ID: <jwvk5kt58sc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1JTb1Y-0007oW-U8@fencepost.gnu.org> (Richard Stallman's message of "Mon, 25 Feb 2008 05:57:32 -0500")

>> 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...

>     A good reason to save those non-file-buffers in a separate directory.

> There are disadvantages to that.

> If that separate directory is under the user's home dir, other people
> who can edit the same file will have trouble finding it.

> It could be under the same directory as the file being edited,
> but that involves creating a directory for this under each directory
> where you edit files.

What "file being edited"?  I'm talking about "non-file-buffers".


        Stefan




  reply	other threads:[~2008-02-25 15:57 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=jwvk5kt58sc.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 \
    --cc=miles@gnu.org \
    --cc=rms@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.