From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 4197@emacsbugs.donarmstrong.com
Subject: bug#4197: 23.1; error when try to run `server-start': directory .emacs.d/server is unsafe
Date: Fri, 21 Aug 2009 21:28:44 +0300 [thread overview]
Message-ID: <838whdggwz.fsf@gnu.org> (raw)
In-Reply-To: <CACF9392E6804A61B2F604F4D53005C4@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <4197@emacsbugs.donarmstrong.com>, <lennart.borgman@gmail.com>
> Date: Fri, 21 Aug 2009 11:12:16 -0700
>
> OK, but FAT32 is very common. I wonder about the default for the variable being
> non-nil, even after the bug is fixed, but especially before then.
The variable does more than just influence server.el. It makes
file-attributes more accurate, which has its own benefits, most
prominently in Dired.
> > Can you perhaps convert the drive to NTFS?
>
> No. Is it a joke?
No, I tried to help you work around the problem (and get a better
filesystem while at that).
> This is not my personal laptop. This is the standard issue for my
> company.
I couldn't know that, could I?
> I think Emacs should be able to coexist and behave nicely with FAT32 - don't
> you?
I do, and it does -- mostly.
> It doesn't make sense to make the default behavior dependent on assuming that
> users do not have FAT32 and are not in the local Administrators group. IMO.
> That's a crippling assumption.
The code in server.el assumes a Posix filesystem. We are trying to
get it to work nicely on Windows, when some of these assumptions don't
hold. IOW, no one specifically assumed users do not have FAT32.
> Beyond the message text, what does it mean? Where is this notion of "unsafe
> directory" documented in the manuals?
It is a more or less common knowledge in the Posix world. But I do
agree that the message text should be more self-explanatory.
> I think this should be explained in the manual(s) - we shouldn't simply improve
> the message (though that too should be done). It is especially important to
> document things that concern safety (if this really does).
If the message is explicit enough, it will explain itself.
next prev parent reply other threads:[~2009-08-21 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 3:25 bug#4197: 23.1; error when try to run `server-start': directory .emacs.d/server is unsafe Drew Adams
2009-08-21 9:24 ` Eli Zaretskii
2009-08-21 14:30 ` Drew Adams
2009-08-21 17:43 ` Eli Zaretskii
2009-08-21 18:12 ` Drew Adams
2009-08-21 18:28 ` Eli Zaretskii [this message]
2009-08-21 18:55 ` Drew Adams
2009-08-21 20:35 ` Eli Zaretskii
2009-08-21 21:03 ` Drew Adams
2009-08-22 10:07 ` Eli Zaretskii
2009-08-22 4:49 ` Stefan Monnier
2009-08-22 8:07 ` Eli Zaretskii
2009-08-23 1:57 ` Stefan Monnier
2009-08-23 3:21 ` Eli Zaretskii
2009-08-23 22:30 ` Stefan Monnier
2009-08-22 9:53 ` Jason Rumney
2009-08-22 10:35 ` Eli Zaretskii
2009-08-22 16:59 ` Jason Rumney
2009-08-22 17:10 ` Lennart Borgman
2009-08-23 1:57 ` Stefan Monnier
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=838whdggwz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=4197@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
/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).