From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17389@debbugs.gnu.org
Subject: bug#17389: 24.4.50; REGRESSION: extraneous file locking
Date: Fri, 02 May 2014 18:40:22 +0300 [thread overview]
Message-ID: <83lhuk195l.fsf@gnu.org> (raw)
In-Reply-To: <4f6a766a-0bfa-4d0c-a4f9-2a085a5b2063@default>
> Date: Fri, 2 May 2014 08:15:16 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> With this build I am seeing file locking that prevents two Emacs
> sessions from editing the same buffer. Emacs pops up annoying questions
> etc.
That's the intended behavior.
> Previously, it was only if you tried to save a buffer that Emacs
> let you know about possible conflicts.
That's not true, this works like that since file locking was ported to
Windows more than a year ago. I just tried that in a very old build,
and saw exactly what you describe, as expected.
Unless you didn't describe the recipe in enough details, that is.
> In Emacs 24.3, emacs -Q:
> C-x C-f iii.el
> Type some text. Do not save the buffer. Do not exit Emacs.
>
> Do the same thing again. No problem. Emacs does not annoy you, telling
> you in the second session that some other user/session has file iii.el
> locked.
Indeed, this is a new feature (on Windows) in Emacs 24.4. On other
platforms, Emacs behaved like that since a very long time ago.
etc/NEWS tells how to turn this feature off, if you don't want it.
next prev parent reply other threads:[~2014-05-02 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:15 bug#17389: 24.4.50; REGRESSION: extraneous file locking Drew Adams
2014-05-02 15:40 ` Eli Zaretskii [this message]
[not found] <<4f6a766a-0bfa-4d0c-a4f9-2a085a5b2063@default>
[not found] ` <<83lhuk195l.fsf@gnu.org>
2014-05-02 15:57 ` Drew Adams
2014-05-02 16:15 ` Eli Zaretskii
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=83lhuk195l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17389@debbugs.gnu.org \
--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 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.