From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#31636: 27.0.50; lockfile syntax searchable from info manual Date: Wed, 30 May 2018 05:42:02 +0300 Message-ID: <83in75vp8l.fsf@gnu.org> References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> <87r2lufvo9.fsf@gmail.com> <83r2luv28h.fsf@gnu.org> <87a7sib7ty.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1527648075 25007 195.159.176.226 (30 May 2018 02:41:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 30 May 2018 02:41:15 +0000 (UTC) Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com To: Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed May 30 04:41:10 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNr30-0006OI-7n for geb-bug-gnu-emacs@m.gmane.org; Wed, 30 May 2018 04:41:10 +0200 Original-Received: from localhost ([::1]:35878 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNr57-0004fa-9w for geb-bug-gnu-emacs@m.gmane.org; Tue, 29 May 2018 22:43:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNr4r-0004eN-2Z for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 22:43:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNr4o-0003bb-0T for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 22:43:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46618) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fNr4n-0003bU-T3 for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 22:43:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fNr4n-0006X3-KN for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 22:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 30 May 2018 02:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31636 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31636-submit@debbugs.gnu.org id=B31636.152764814025031 (code B ref 31636); Wed, 30 May 2018 02:43:01 +0000 Original-Received: (at 31636) by debbugs.gnu.org; 30 May 2018 02:42:20 +0000 Original-Received: from localhost ([127.0.0.1]:54512 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNr47-0006Vf-Vv for submit@debbugs.gnu.org; Tue, 29 May 2018 22:42:20 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:36344) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNr45-0006VQ-KO for 31636@debbugs.gnu.org; Tue, 29 May 2018 22:42:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNr3z-0003Be-D4 for 31636@debbugs.gnu.org; Tue, 29 May 2018 22:42:12 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47597) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNr3v-0003AA-P4; Tue, 29 May 2018 22:42:07 -0400 Original-Received: from [176.228.60.248] (port=2266 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fNr3v-00068a-6Z; Tue, 29 May 2018 22:42:07 -0400 In-reply-to: <87a7sib7ty.fsf@gmail.com> (message from Robert Pluim on Tue, 29 May 2018 21:06:01 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:146732 Archived-At: > From: Robert Pluim > Cc: Paul Eggert , mail@bradyt.com, 31636@debbugs.gnu.org, npostavs@gmail.com > Date: Tue, 29 May 2018 21:06:01 +0200 > > > Hmm... I'm okay with describing this in the doc string (and then > > perhaps also describe the info recorded in the symlink? it doesn't > > sound like it is less important than the exact file name). > > I understood the OP's concern to be that there was no obvious link > from '.#' files and the fact that those files are used for locking. I > donʼt see a need to put all the details about that locking in the doc > string. My reasoning was that if someone wants to know about these funny file names, someone else would like to know more. E.g., the symlink points to a specially-formatted target, and that target records important info. > >> 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 > > > > "Contains the string" is again a half-truth. It sounds like this bug > > report is against telling half-truths. > > How is it a half-truth? Is the lockfile name not constructed by > prepending '.#' to the filename? It is, but you don't actually say that. The whole truth would be It does this by creating a symlink whose name is @file{.#@var{fname}}, where @var{fname} is the name of the locked file. Given Paul's comments, perhaps we should simply say It does this by creating a symlink whose name begins with @file{.#} and leave the rest to the ELisp manual. > > As I said above, I think if we are describing this in more detail, why > > not describe also the information recorded in the lockfile? If > > someone looked up the lockfile name, someone else may wish to look up > > the data it records and understand what that is, no? > > Didnʼt you make the point just now that this kind of detail could > change and weʼd forget to update the documentation? Or did you want > this in the elisp manual? The latter.