all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: CLASH_DETECTION option in configure
Date: Sun, 3 Feb 2013 16:36:59 -0700	[thread overview]
Message-ID: <20130203233659.GA30144@hysteria.proulx.com> (raw)
In-Reply-To: <20130203151143.b0e727fa15c48fccee3a4dbc@lavabit.com>

rh wrote:
> It seems like an antiquated feature and it doesn't make sense to
> have it enabled by default. Since version control systems are every
> where now I can't see why anyone would want or use this feature.
> What's the use case?

If you as a single user try to edit a file from two different
terminals then it will be detected and a collision avoided.  I often
run into cases where emacs notifies me that I am already editing a
file in another terminal.  The use case is far from antiquated and has
nothing to do with version control.  Because unintended data loss can
result if it were disabled the feature is enabld by default.

I will turn the same question around on you.  Why would you ever want
to disable this feature?  Why is it causing you difficulty?  If as you
say you would never hit this issue then you should also by that same
reasoning never know it is there either.

Bob



  parent reply	other threads:[~2013-02-03 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130130145503.54e2572bafd6283f61956823@lavabit.com>
2013-01-30 23:16 ` CLASH_DETECTION option in configure Glenn Morris
     [not found]   ` <20130203151143.b0e727fa15c48fccee3a4dbc@lavabit.com>
2013-02-03 23:36     ` Bob Proulx [this message]
     [not found]       ` <20130204163259.69cffecc682fa6d6390d66cb@lavabit.com>
2013-02-12 20:55         ` Bob Proulx
     [not found]   ` <mailman.18953.1359933124.855.help-gnu-emacs@gnu.org>
2013-02-04  2:56     ` 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

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

  git send-email \
    --in-reply-to=20130203233659.GA30144@hysteria.proulx.com \
    --to=bob@proulx.com \
    --cc=help-gnu-emacs@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.