From: Robert Pluim <rpluim@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Brady Trainor <mail@bradyt.com>, 31636@debbugs.gnu.org
Subject: bug#31636: 27.0.50; lockfile syntax searchable from info manual
Date: Tue, 29 May 2018 15:17:26 +0200 [thread overview]
Message-ID: <87r2lufvo9.fsf@gmail.com> (raw)
In-Reply-To: <87tvqqd7rp.fsf@gmail.com> (Noam Postavsky's message of "Tue, 29 May 2018 07:24:26 -0400")
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
Noam Postavsky <npostavs@gmail.com> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> This does mean that if the implementation of locking ever changes,
>> weʼd need to update those docs, but I donʼt think thereʼs much chance
>> of that.
>
> Yes, that's usually the case. I think you can drop the word "currently"
> from your patch.
OK. V2 attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Add-more-discoverable-documentation-for.patch --]
[-- Type: text/x-patch, Size: 1952 bytes --]
From 03525a8319ba7a1fb9d1375fa989db0bf9f7feb1 Mon Sep 17 00:00:00 2001
From: Robert Pluim <rpluim@gmail.com>
Date: Tue, 29 May 2018 10:19:16 +0200
Subject: [PATCH] Add more discoverable documentation for '.#'
To: emacs-devel@gnu.org
* doc/emacs/files.texi (Interlocking): Add index entry for '.#' and
mention its use in lockfile names.
* src/filelock.c (Flock_buffer): Mention '.#' string, add reference to
Interlocking info node.
---
doc/emacs/files.texi | 4 +++-
src/filelock.c | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 1ced7ca07c..72d538161a 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -766,9 +766,11 @@ Interlocking
@findex ask-user-about-lock
@cindex locking files
+@cindex .#
When you make the first modification in an Emacs buffer that is
visiting a file, Emacs records that the file is @dfn{locked} by you.
-(It does this by creating a specially-named symbolic link@footnote{If
+(It does this by creating a specially-named symbolic link, whose name
+contains the string @code{.#} @footnote{If
your file system does not support symbolic links, a regular file is
used.} with special contents in the same directory.) Emacs removes the lock
when you save the changes. The idea is that the file is locked
diff --git a/src/filelock.c b/src/filelock.c
index f2dc723407..042fe9e00b 100644
--- a/src/filelock.c
+++ b/src/filelock.c
@@ -773,7 +773,9 @@ DEFUN ("lock-buffer", Flock_buffer, Slock_buffer,
FILE defaults to current buffer's visited file,
or else nothing is done if current buffer isn't visiting a file.
-If the option `create-lockfiles' is nil, this does nothing. */)
+If the option `create-lockfiles' is nil, this does nothing.
+The name of the lockfile used contains '.#', see
+Info node `(emacs)Interlocking' for more information. */)
(Lisp_Object file)
{
if (NILP (file))
--
2.17.0.775.ge144d126d7
next prev parent reply other threads:[~2018-05-29 13:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 7:33 bug#31636: 27.0.50; lockfile syntax searchable from info manual Brady Trainor
2018-05-29 8:40 ` Robert Pluim
2018-05-29 11:24 ` Noam Postavsky
2018-05-29 13:17 ` Robert Pluim [this message]
2018-05-29 16:46 ` Eli Zaretskii
2018-05-29 19:06 ` Robert Pluim
2018-05-30 2:42 ` Eli Zaretskii
2018-05-31 10:29 ` Robert Pluim
2018-06-01 8:52 ` Eli Zaretskii
2018-06-01 10:47 ` Robert Pluim
2018-06-01 13:00 ` Eli Zaretskii
2018-06-01 13:24 ` Robert Pluim
2018-06-01 13:25 ` Robert Pluim
2018-05-29 19:20 ` Paul Eggert
2018-05-30 2:42 ` 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
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=87r2lufvo9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31636@debbugs.gnu.org \
--cc=mail@bradyt.com \
--cc=npostavs@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 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).