From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#34911: 26.1; doc about lock file names Date: Tue, 19 Mar 2019 07:54:48 -0700 (PDT) Message-ID: References: <> <<83bm27uzbr.fsf@gnu.org>> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="22459"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 34911@debbugs.gnu.org To: Eli Zaretskii , Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 19 16:00:44 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6GEN-0005hZ-MQ for geb-bug-gnu-emacs@m.gmane.org; Tue, 19 Mar 2019 16:00:44 +0100 Original-Received: from localhost ([127.0.0.1]:58599 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h6GEM-0002Mo-GL for geb-bug-gnu-emacs@m.gmane.org; Tue, 19 Mar 2019 11:00:42 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:41441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h6GBn-0000AO-By for bug-gnu-emacs@gnu.org; Tue, 19 Mar 2019 10:58:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h6G8v-0004kU-6P for bug-gnu-emacs@gnu.org; Tue, 19 Mar 2019 10:55:06 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37226) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h6G8u-0004eX-Ar for bug-gnu-emacs@gnu.org; Tue, 19 Mar 2019 10:55:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h6G8t-00073n-QK for bug-gnu-emacs@gnu.org; Tue, 19 Mar 2019 10:55:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 19 Mar 2019 14:55:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34911 X-GNU-PR-Package: emacs Original-Received: via spool by 34911-submit@debbugs.gnu.org id=B34911.155300730127125 (code B ref 34911); Tue, 19 Mar 2019 14:55:02 +0000 Original-Received: (at 34911) by debbugs.gnu.org; 19 Mar 2019 14:55:01 +0000 Original-Received: from localhost ([127.0.0.1]:50770 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h6G8q-00073R-Rx for submit@debbugs.gnu.org; Tue, 19 Mar 2019 10:55:01 -0400 Original-Received: from aserp2130.oracle.com ([141.146.126.79]:43880) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h6G8n-00073C-DN for 34911@debbugs.gnu.org; Tue, 19 Mar 2019 10:54:57 -0400 Original-Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x2JEmu8Q090669; Tue, 19 Mar 2019 14:54:51 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=eVUCc7tr+nYCvu/MAs2hb+PspElaS49I1U2WFPKyQYM=; b=P6fqfe65v51h0YCMVjFsFctw0ZD4n9rt/tcvPlUsTq50PL4zVUlvp6aArngCgBJYdvS/ 8SomYAb/wWxHCj7qT27wkZA9bv2TheFhSd3Xg+mbz5BVNxX1zjWgVA3UZTaZ6viiaLnI UxktqD3yQJcGLtOoW+NoD1qr8tgvdL7+JUXMiTd4O8p/WOeN+R/NgV3GdweFxu9p5w5D j1Zfc5N3Iroqv7XFgPNTcR81Q9MI5IwmSVRTOt9SGQ7LCPgLHMCqmajMTTwopCzmznZd EZkyo4d8qmJZ/p5a8ZBmSXc0igV8hrhGuSBNhzl730fXH0+VMwfc3Vu3FkeeRc1CT4Pc XQ== Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2130.oracle.com with ESMTP id 2r8pneneqe-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 19 Mar 2019 14:54:51 +0000 Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id x2JEsokd028937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 19 Mar 2019 14:54:50 GMT Original-Received: from abhmp0020.oracle.com (abhmp0020.oracle.com [141.146.116.26]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id x2JEsnTA010667; Tue, 19 Mar 2019 14:54:49 GMT In-Reply-To: <<83bm27uzbr.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4822.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9199 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903190110 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: 209.51.188.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:156502 Archived-At: > > I don't see documented anywhere what a lock file name looks like. > > I looked through both the Emacs manual and the Elisp manual. Did I mis= s > > it somehow, or is it defined/described nowhere? >=20 > It is described in the node "File Locks" in the ELisp manual. I started there. I see nothing in that node that says what the name looks like. I'm using Emacs 26. Did someone perhaps add a description of it since that release? > > Please let users know what how lock files are named. Thx. If this is > > already done somewhere, please refer to that location from node (elisp) > > `File Locks'. >=20 > The node "Interlocking" in the user manual, where file locking is > described on the user level, has a cross-reference to the above node > pf ELisp manual. So I'm unsure how you missed that. Please explain how that replies to the text you quote, or to any of the text in the bug report? AFAICT, there is nothing in the Emacs manual (including of course the node you cite) or in the Elisp manual (including the node you cite) that tells you how lock files are named. That's what this bug report is about (and its near-duplicate, #25469, also touches on this lack). =20 > > Please also update the doc of `dired-omit-files' to make clear that its > > default value only approximately matches auto-save files (and lock > > files?), and that even this is true only for the default naming regime > > for auto-save files. >=20 > I don't understand this part. Concretely, what is missing in the doc > string, and why do you think it is necessary to add whatever is > missing? The default value is "^\\.?#\\|^\\.$\\|^\\.\\.$". \\.?# matches only the first char of an auto-save file name, and the first two chars of a lock file name. It does not match the full name, requiring it to end with `#'. That means that (1) it cannot be used as is for, say, font-locking such a (complete) name, and (2) as it is now, it can falsely identify files that are not auto-save or lock files. And it does not necessarily match auto-save file names at all, as they can be nearly anything, it seems: (elisp) `Auto-Saving' makes a point of saying that each of `auto-save-file-name-p' and `make-auto-save-file-name' exists "so that you can customize it if you wish to change the naming convention for auto-save files". And for each it reminds us "If you redefine it, be sure to redefine the [other] function ... correspondingly." IOW, apparently the `#...#' is conventional but users are practically invited to adopt alternative naming schemes. While those two functions go together, so that changing the naming scheme for one calls for changing it also for the other, there are other functions and variables that presume the standard naming convention. Their doc does not, so far, speak to the possibility of a naming change. Also, please add a doc string for `dired-omit-regexp', referring to `dired-omit-files' (where this missing doc will hopefully be added) and `dired-omit-extensions', as is done for `dired-mark-omitted', for example. Does this clarify what I meant by "the default value only approximately matches auto-save files (and lock files?)"?