From: Dani Moncayo <dmoncayo@gmail.com>
To: 18828@debbugs.gnu.org
Subject: bug#18828: 24.4; Early collision warning when 'create-lockfiles' is set to nil
Date: Sat, 25 Oct 2014 17:07:25 +0200 [thread overview]
Message-ID: <CAH8Pv0i0G9PuzijehnRigXKouBtFSmoykXLrdRnjcqoLsGTT+w@mail.gmail.com> (raw)
Recipe:
0. emacs -Q
1. Eval: (setq create-lockfiles nil)
2. Visit some file
3. With another program, update the visited file.
4. Try to make some change to the buffer.
------------
Without step 1, Emacs does TRT, i.e., it detects that I'm trying to
make the first change to a buffer whose file has already changed since
it was visited, so it warns me with:
foo changed on disk; really edit the buffer? (y, n, r or C-h)
But with step 1, Emacs doesn't warn me until I try to save the buffer;
then it shows me this:
foo has changed since visited or saved. Save anyway? (yes or no)
(BTW: the above message does not get archived in the *Messages*
buffer. Why not? I think it should, as with the first warning)
Well, I think that Emacs should warn me on step 4, regardles of
whether I did step 1 or not.
I set `create-lockfiles' to nil in my init file because I don't want
Emacs to create temporary files of any kind, but obviously I want to
be warned whenever I am about to change a buffer whose file has
changed on disk after it was last read by Emacs.
I observe this bug both with the last 24.4 release and with the trunk.
In GNU Emacs 24.4.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.3.9600
Important settings:
value of $LANG: ENU
locale-coding-system: cp1252
--
Dani Moncayo
next reply other threads:[~2014-10-25 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 15:07 Dani Moncayo [this message]
2015-03-14 4:12 ` bug#18828: 24.4; Early collision warning when 'create-lockfiles' is set to nil Daniel Lopez
2015-04-29 9:59 ` Dani Moncayo
2015-04-29 15:44 ` Glenn Morris
2015-04-29 15:53 ` Dani Moncayo
2015-04-29 15:57 ` Glenn Morris
2015-04-29 16:16 ` Eli Zaretskii
2015-05-04 21:12 ` Dani Moncayo
2015-05-08 9:22 ` 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=CAH8Pv0i0G9PuzijehnRigXKouBtFSmoykXLrdRnjcqoLsGTT+w@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=18828@debbugs.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.