From: Dave Abrahams <dave@boostpro.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: johnw@newartisans.com, rms@gnu.org,
Lennart Borgman <lennart.borgman@gmail.com>,
emacs-devel@gnu.org, schwab@linux-m68k.org, stephen@xemacs.org
Subject: Re: Proposed patch: allow user to disable lockfile creation
Date: Thu, 28 Jul 2011 20:51:41 -0400 [thread overview]
Message-ID: <m2d3gt7vtu.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <CAC=50j-GXR-QNtn+W9Qp8f0nVJGmpZFJTxc3xMzxdxVDUH_XXQ@mail.gmail.com> (Tim Cross's message of "Fri, 29 Jul 2011 10:12:11 +1000")
on Thu Jul 28 2011, Tim Cross <theophilusx-AT-gmail.com> wrote:
> It seems that the issue isn't really about conflict detection per se,
> but rather how emacs implements it via symlinks.
It's actually more than that. The scheme is simultaneously
over-cautious and yet full of holes. It's predicated on the idea that
everybody who might touch the file simultaneously is using Emacs, but
that's obviously a fallacy. Any program that doesn't respect Emacs'
convention and look for the lock file (e.g. every command-line tool in
existence) will happily write the file even when I have a lock on it.
Furthermore, Emacs is perfectly capable of telling me when that has
happened before I save... at least it seems to work pretty darned
reliably. So I think this feature made sense once upon a time but is
now just a vestigial flipper.
Am I missing something? I could be.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-07-29 0:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 2:42 Proposed patch: allow user to disable lockfile creation Dave Abrahams
2011-07-27 15:32 ` Andreas Schwab
2011-07-27 16:25 ` Dave Abrahams
2011-07-27 18:56 ` John Wiegley
2011-07-28 1:57 ` Stephen J. Turnbull
2011-07-28 16:46 ` Richard Stallman
2011-07-28 16:54 ` Lennart Borgman
2011-07-28 23:00 ` Richard Stallman
2011-07-29 0:12 ` Tim Cross
2011-07-29 0:51 ` Dave Abrahams [this message]
2011-07-29 23:40 ` Richard Stallman
2011-07-30 3:29 ` Dave Abrahams
2011-07-30 7:21 ` Eli Zaretskii
2011-07-30 12:32 ` Dave Abrahams
2011-07-30 18:12 ` Richard Stallman
2011-07-31 2:13 ` Tim Cross
2011-07-29 23:40 ` Richard Stallman
2011-07-30 12:46 ` Dave Abrahams
2011-07-28 18:22 ` chad
2011-07-28 23:00 ` Richard Stallman
2011-07-28 19:21 ` Paul Eggert
2011-07-29 17:31 ` Richard Stallman
2011-07-29 19:59 ` David Kastrup
2011-07-30 4:35 ` Richard Stallman
2011-07-30 7:36 ` David Kastrup
2011-07-29 3:31 ` Stephen J. Turnbull
2011-07-28 21:20 ` Evil Boris
2011-07-30 14:20 ` Daniel Colascione
2011-07-30 18:12 ` Richard Stallman
2011-07-31 2:22 ` Tim Cross
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=m2d3gt7vtu.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.com \
--cc=lennart.borgman@gmail.com \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stephen@xemacs.org \
--cc=theophilusx@gmail.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 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.