From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 03:42:09 2018 Received: (at submit) by debbugs.gnu.org; 29 May 2018 07:42:09 +0000 Received: from localhost ([127.0.0.1]:53066 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNZGi-0007eo-LF for submit@debbugs.gnu.org; Tue, 29 May 2018 03:42:09 -0400 Received: from eggs.gnu.org ([208.118.235.92]:57832) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNZ8N-0007S0-Dm for submit@debbugs.gnu.org; Tue, 29 May 2018 03:33:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNZ8H-0007WI-1g for submit@debbugs.gnu.org; Tue, 29 May 2018 03:33:26 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,T_DKIM_INVALID autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:47027) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fNZ8G-0007WE-Uu for submit@debbugs.gnu.org; Tue, 29 May 2018 03:33:24 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48801) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNZ8B-0007wX-JJ for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 03:33:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNZ86-0007PR-Fm for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 03:33:19 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:43861) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fNZ86-0007OV-8a for bug-gnu-emacs@gnu.org; Tue, 29 May 2018 03:33:14 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 829A421B8D; Tue, 29 May 2018 03:33:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 29 May 2018 03:33:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=HNGFdePe+ivXhqRGLzFoWyrI2CaXDK07c7U5mxWcmd4=; b=V36ySmOh 5iHMA0ycxYY+pjrFPya32PPPstVy68Rfkltv7mfxje7Oq8+BGOqSPLwAt87JBhOp rIuG7MMQqNfqAqkm/kM4JCrUSqQzO+Uh6mgDUxYS/hPe+3prbwrrujb3ebagEKQf 5uLk1XcQ7P8M1iuaADJC+oFnXYIogX/gB10ibW6K4Pl+496xwhti4udc+/smwziE 2XrieF4TDg6G3wbOylhzeFiwkjwMIZh31d2yxOdP7jVCRyjEfY11vjKQed/f08Pz uxvfSpsaYUXv7kQmHsloXIoA/TjIGmxGW9eb/lh5ZwXAyyRUTYqnsD/MQ5i+ByVT nDM0kizTA4vrKQ== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: From: Brady Trainor To: bug-gnu-emacs@gnu.org Subject: 27.0.50; lockfile syntax searchable from info manual Date: Tue, 29 May 2018 00:33:10 -0700 MIME-Version: 1.0 Content-Type: text/plain Message-Id: <20180529073311.EEA09102DA@mailuser.nyi.internal> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -4.1 (----) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Tue, 29 May 2018 03:42:07 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.1 (-----) I had hoped to find about files such as `/tmp/.#fileA` by searching in the info manual for ".#". But I did not find such a string there, nor via `apropos-documentation`. If a user encounters such a file in a directory, I think it would lead to good discoverability if a manual or docstring had some mention of the string ".#", so that one might search for it. I'm sending this report without having spent a lot of time on it now, not sure if this ".#" convention comes from outside of emacs. Thank you! -- Brady In GNU Emacs 27.0.50 (build 1, x86_64-apple-darwin17.4.0, NS appkit-1561.20 Version 10.13.3 (Build 17D102)) of 2018-04-11 built on computer Repository revision: 57442b6812e9ec565efc39f722e84079dd71d8c0 System Description: Mac OS X 10.13.3 Recent messages: For information about GNU Emacs and the GNU system, type C-h C-a. Making completion list... Configured using: 'configure --disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs/HEAD-57442b6/share/info/emacs --prefix=/usr/local/Cellar/emacs/HEAD-57442b6 --without-x --with-xml2 --with-dbus --with-gnutls --with-imagemagick --with-modules --with-rsvg --without-pop --with-ns --disable-ns-self-contained' Configured features: RSVG IMAGEMAGICK DBUS NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS Important settings: value of $LANG: en_US.UTF-8 locale-coding-system: utf-8-unix Major mode: Lisp Interaction Minor modes in effect: tooltip-mode: t global-eldoc-mode: t eldoc-mode: t electric-indent-mode: t mouse-wheel-mode: t tool-bar-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Load-path shadows: None found. Features: (shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv bytecomp byte-compile cconv dired dired-loaddefs format-spec rfc822 mml easymenu mml-sec password-cache epa derived epg epg-config gnus-util rmail rmail-loaddefs mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loaddefs cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils term/screen term/xterm xterm time-date elec-pair tooltip eldoc electric uniquify ediff-hook vc-hooks lisp-float-type mwheel term/ns-win ns-win ucs-normalize mule-util term/common-win tool-bar dnd fontset image regexp-opt fringe tabulated-list replace newcomment text-mode elisp-mode lisp-mode prog-mode register page menu-bar rfn-eshadow isearch timer select scroll-bar mouse jit-lock font-lock syntax facemenu font-core term/tty-colors frame cl-generic cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese composite charscript charprop case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer cl-preloaded nadvice loaddefs button faces cus-face macroexp files text-properties overlay sha1 md5 base64 format env code-pages mule custom widget hashtable-print-readable backquote dbusbind kqueue cocoa ns multi-tty make-network-process emacs) Memory information: ((conses 16 208559 10343) (symbols 48 20073 1) (miscs 40 33 124) (strings 32 29281 1750) (string-bytes 1 769239) (vectors 16 33056) (vector-slots 8 675093 10872) (floats 8 51 470) (intervals 56 232 0) (buffers 992 12)) From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 04:40:35 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 08:40:35 +0000 Received: from localhost ([127.0.0.1]:53117 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNaBH-0000ZR-Cz for submit@debbugs.gnu.org; Tue, 29 May 2018 04:40:35 -0400 Received: from mail-wm0-f41.google.com ([74.125.82.41]:50476) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNaBG-0000ZE-7z for 31636@debbugs.gnu.org; Tue, 29 May 2018 04:40:34 -0400 Received: by mail-wm0-f41.google.com with SMTP id t11-v6so38169387wmt.0 for <31636@debbugs.gnu.org>; Tue, 29 May 2018 01:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version; bh=3DMkeQCkrUbskcIstzVTCcQzT25Hn7kA9FkJ0LrVdMM=; b=WMEjdXS1IT9XZprMI4TtFwrjZlakb+iw4tWfsFw5UFa9ue/a7dtWHXEtuCbIHIjpCM q84MB/ZuFMxwYZIoOG0ifVs/1lZ64ELxQk5rdUqw9mXkLYzAWPYlU0Euy2pxIeRpTPgl mnDxnYiBYy0ZHgJSJO5236F45thy7FtlNFNrMcaPRvwBPQlr0+de7zFuMosLljcRRSN+ Rni1vZlzYMdEm5J6PIOPKfQlWdn3Z2QzBBjh8RihjvnsGUQoUzMFxKuanT8lUKPfrDh+ effPkBeF2ZmigzR2FVpej9ZB7lnZ9SQ8iR6ie43Jr00tY4bWenOEF7Clnjq39nDC+qkE 83xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version; bh=3DMkeQCkrUbskcIstzVTCcQzT25Hn7kA9FkJ0LrVdMM=; b=TfOKl2LbdmXBFrutwq3iIq5tbi+ccSUoV4aVmW/K0/6JPxSwfdWUxCsU6T8BUv5/IM ifX+IpFK0fG7cz1EjgP+Wk0q7G/2cOq8/ODaqyIZ96KYTttXd85zbCizsWqiG1n4kapD rlupJntl0jj0hnoFnTLHkE+QJevvQ1UQum3OTbZ6Qso6QiF6Ag65IxE5RJkr8o3oU1v3 kfPQK3CGhQ/CMuiNe0YHzs3u1HzC1CIJHg21K/8LmoVI259kE5T9lwJd8TX/7FHU8RQe DwVkR7hi3ORIR/zy20lEHjTmx5yDbkS67jo/x/PH5YoZe8xyy999RSsxJN8jlPQ30MAv N+TA== X-Gm-Message-State: ALKqPwe87OwRdqhpTnLaj8gPCDQOXFWFKPDh8tZku2Cf9QLacnN3QyuO XFsK4gq7rNZjPzk5x9wCHZt6CPmcr80= X-Google-Smtp-Source: ADUXVKL+tM8QVim4i+xjgBCh5ZnZ30hBer1P+qeUhL9RA4JAe9zene9wM3Yf4nHBPj9BBLaQEY9UHQ== X-Received: by 2002:a1c:4249:: with SMTP id p70-v6mr10790718wma.17.1527583228062; Tue, 29 May 2018 01:40:28 -0700 (PDT) Received: from rpluim ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id u8-v6sm12371177wmc.40.2018.05.29.01.40.26 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 01:40:26 -0700 (PDT) From: Robert Pluim To: Brady Trainor Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Tue, 29 May 2018 10:40:25 +0200 In-Reply-To: <20180529073311.EEA09102DA@mailuser.nyi.internal> (Brady Trainor's message of "Tue, 29 May 2018 00:33:10 -0700") Message-ID: <876036hn2e.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 31636 Cc: 31636@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Brady Trainor writes: > I had hoped to find about files such as `/tmp/.#fileA` by searching in > the info manual for ".#". But I did not find such a string there, nor > via `apropos-documentation`. > > If a user encounters such a file in a directory, I think it would lead > to good discoverability if a manual or docstring had some mention of the > string ".#", so that one might search for it. > > I'm sending this report without having spent a lot of time on it now, > not sure if this ".#" convention comes from outside of emacs. We could add an index entry to the info manual. Adding a reference inside the docstring of 'lock-buffer' would enable 'apropos-documentation' to find it as well. This does mean that if the implementation of locking ever changes, we=CA=BCd need to update those docs, but I don=CA=BCt think there=CA=BCs mu= ch chance of that. Proposed patch (for emacs-26?) --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-Add-more-discoverable-documentation-for.patch >From 2655d523a8136365e00076e1162598913f58277c Mon Sep 17 00:00:00 2001 From: Robert Pluim 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..f80ad5bbd7 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 +currently 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..d93adf8e81 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 currently contains '.#', see +Info node `(emacs)Interlocking' for more information. */) (Lisp_Object file) { if (NILP (file)) -- 2.17.0.775.ge144d126d7 --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 07:24:36 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 11:24:36 +0000 Received: from localhost ([127.0.0.1]:53191 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNck0-0004WE-Ak for submit@debbugs.gnu.org; Tue, 29 May 2018 07:24:36 -0400 Received: from mail-io0-f181.google.com ([209.85.223.181]:39694) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNcjy-0004W2-CX for 31636@debbugs.gnu.org; Tue, 29 May 2018 07:24:34 -0400 Received: by mail-io0-f181.google.com with SMTP id 200-v6so16117485ioz.6 for <31636@debbugs.gnu.org>; Tue, 29 May 2018 04:24:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=5Gd7SGWklJIvZRYm062CnTvUrkVBEK/FPXzMatL8rSo=; b=fAW+fBiIV0vii/IAJYF9uH6Vu3HGn3n72r2lfr5jKwt4135uxzTgblsESbws9zqhFt CXeQDJM5yahzfSs/oTuiusMoGUgBLoBVUBqBJQtN9ubTBvfzg3spdjM6sp6qr9XWJLya ij3kSuUnwh8/weZpa7Z4CHCQHjC156HAFFrzgS7Ce5sX0ybqTjwN8Jl30CQOntM34ubf PfQ6IvqUN6ycSfaDhAoRQjFnttOn2ff0Zd7zWn1lTrZh3EuP7CKh9S8EXPED0G3/S2OH ULHkxpCVPU9bUCg+rweIibTlo9/oUFOtOo4NQkwrKpwPfKkZEO0S6W+ZTDqBUHnH7+dl rqZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=5Gd7SGWklJIvZRYm062CnTvUrkVBEK/FPXzMatL8rSo=; b=CqJHIsAfZb7LUckhwvwDSnel8DFPOzqknMIYrKVsIli6fHEW/0hHIzqFQujwlaLWt2 ET5EirSXbFEfp0r0DPBf2lBl3CTCk3Wc0jPoHrhAZne9HwMC1AnbiCv/Vgq4i6E5KJmA 3S+N2v2JYKG1HWdn2oj60FvtP8FK5k6Gw8pLbLlTcqSyxN6hum3GllSUoMsOWCqzhPqA zh8u8Ifhc98VI4mwQ3HR6smeretnvIfpm+UDROWjp/uP4skdIz87a++V9cnYDnUwoitG 7AR18EodVSQM0Mj9bx5a55T5TBIRwYURrXDS+am/ouOK27GdnI+1miy9VYMcxNv0lCZm bgBg== X-Gm-Message-State: ALKqPwew6nzbN7JoyBdrEVTNNsuqTpw8bi5D2tqJvDzQY1ZZNsQVJRz5 9Wx/20ncZp6PxyJNBVMPyN/CiA== X-Google-Smtp-Source: ADUXVKLrfsckWzKi8HqacesJ9A4TFG5Vr0unfXwjdNQOXBJz1NJ+R3dfoQJ7oEQFgVcFLFqsakVBUw== X-Received: by 2002:a6b:5301:: with SMTP id h1-v6mr14774427iob.73.1527593068839; Tue, 29 May 2018 04:24:28 -0700 (PDT) Received: from zebian (cbl-45-2-119-34.yyz.frontiernetworks.ca. [45.2.119.34]) by smtp.googlemail.com with ESMTPSA id e139-v6sm10539883ite.1.2018.05.29.04.24.27 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 04:24:28 -0700 (PDT) From: Noam Postavsky To: Brady Trainor Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> Date: Tue, 29 May 2018 07:24:26 -0400 In-Reply-To: <876036hn2e.fsf@gmail.com> (Robert Pluim's message of "Tue, 29 May 2018 10:40:25 +0200") Message-ID: <87tvqqd7rp.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.7 (-) X-Debbugs-Envelope-To: 31636 Cc: 31636@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.7 (--) Robert Pluim writes: > This does mean that if the implementation of locking ever changes, > we=CA=BCd need to update those docs, but I don=CA=BCt think there=CA=BCs = much chance > of that. Yes, that's usually the case. I think you can drop the word "currently" from your patch. From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 09:17:35 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 13:17:36 +0000 Received: from localhost ([127.0.0.1]:53288 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNeVL-0004jI-LX for submit@debbugs.gnu.org; Tue, 29 May 2018 09:17:35 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:56004) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNeVJ-0004j5-Sl for 31636@debbugs.gnu.org; Tue, 29 May 2018 09:17:34 -0400 Received: by mail-wm0-f48.google.com with SMTP id a8-v6so40456132wmg.5 for <31636@debbugs.gnu.org>; Tue, 29 May 2018 06:17:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version; bh=XaXC5tcaSiQ7u/xJR9zDvbcfJDjTINBy2tQhp4oxjYM=; b=kNi7FprN/p2sHyTxtUWRtUhim/30fzx6xNmFtBM1mHN76mv4gfWjUgIPSxaLb25l0T td44wLk5kl3PCIjae7qSv4n/RmgtN9YSoRm8Nf14tGzmWFmWZ4h9U++rIHm3LCZIOgPl WNKT2FS6vOdC4QOJf7qS85H9Smyuer5kT8YVtfZcEO+94yJWgWr+xtuncoByFaR1IENz V0mIwpZGInr2Aqu6UCdW+Q2b4M4AmJAPauAVBKyB3u3lnNwa4TIbx2x5KlKYLtRO/ueF uFSZOyuotN6wyrx7Xiv8gwKVC0KeYDVCwjvWUR/AsdQvp+IqPvS+31MWFF6Unk8vAzD+ AEBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version; bh=XaXC5tcaSiQ7u/xJR9zDvbcfJDjTINBy2tQhp4oxjYM=; b=fIigV//LuYoS8hctXRIQFJPX3G72nlRQuz6v5YQuswBT1cQ0S4tSyuhz91pWIuNH4a Ta0e8NJSLnsooIPScyixBtA9DfLAijZWelBCFNy8nDdzLW/XZjNIYX3Kew63bsnMSNaD 8G7nyi8OWJ3nNOtJgPORyPFq7HqF6+jURAPoUAK5cY9tQNMW7oiqMAzg8XO3bKyCOxKh UOLO1A+6ESchcSZZuZnrbaeV23PZb0eK+ShSvO4ALc8DXFUpEvGVw1OlkwQ273+1u7AK JoAH0QiHl3H07QIopdbDff8pUo2mMdTDRxKrI4WbCuRe1fkU1sEJYo58pHTAzsI/3+d4 L1rA== X-Gm-Message-State: ALKqPwdEeviNUUgNIFEAFxlRLb3m5ab0lJyDcV7LVqqMQvhtFMmlJ2kk 0WKBR5+KJ4tuJ3Atl4TzIzszwtHu6B4= X-Google-Smtp-Source: ADUXVKLxCxS+BHaLPYiPwtWaUBSJXraU500bLdlglMJ8v2VCaRTJRAJlUZUYSD2aRNxsOsEskqTSDg== X-Received: by 2002:a1c:e182:: with SMTP id y124-v6mr12634187wmg.57.1527599847868; Tue, 29 May 2018 06:17:27 -0700 (PDT) Received: from rpluim ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id m134-v6sm16403796wmg.13.2018.05.29.06.17.26 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 06:17:26 -0700 (PDT) From: Robert Pluim To: Noam Postavsky Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Tue, 29 May 2018 15:17:26 +0200 In-Reply-To: <87tvqqd7rp.fsf@gmail.com> (Noam Postavsky's message of "Tue, 29 May 2018 07:24:26 -0400") Message-ID: <87r2lufvo9.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 31636 Cc: Brady Trainor , 31636@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Noam Postavsky writes: > Robert Pluim writes: > >> This does mean that if the implementation of locking ever changes, >> we=CA=BCd need to update those docs, but I don=CA=BCt think there=CA=BCs= much chance >> of that. > > Yes, that's usually the case. I think you can drop the word "currently" > from your patch. OK. V2 attached. --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-Add-more-discoverable-documentation-for.patch >From 03525a8319ba7a1fb9d1375fa989db0bf9f7feb1 Mon Sep 17 00:00:00 2001 From: Robert Pluim 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 --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 12:46:57 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 16:46:57 +0000 Received: from localhost ([127.0.0.1]:54238 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNhlw-0001Sx-Pw for submit@debbugs.gnu.org; Tue, 29 May 2018 12:46:57 -0400 Received: from eggs.gnu.org ([208.118.235.92]:58192) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNhlu-0001Si-IY for 31636@debbugs.gnu.org; Tue, 29 May 2018 12:46:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNhlk-0006rU-HQ for 31636@debbugs.gnu.org; Tue, 29 May 2018 12:46:49 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36099) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNhlk-0006rQ-E6; Tue, 29 May 2018 12:46:44 -0400 Received: from [176.228.60.248] (port=1414 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fNhlj-0000N3-Th; Tue, 29 May 2018 12:46:44 -0400 Date: Tue, 29 May 2018 19:46:38 +0300 Message-Id: <83r2luv28h.fsf@gnu.org> From: Eli Zaretskii To: Robert Pluim , Paul Eggert In-reply-to: <87r2lufvo9.fsf@gmail.com> (message from Robert Pluim on Tue, 29 May 2018 15:17:26 +0200) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> <87r2lufvo9.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > From: Robert Pluim > Date: Tue, 29 May 2018 15:17:26 +0200 > Cc: Brady Trainor , 31636@debbugs.gnu.org > > From: Robert Pluim > 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(-) 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). But I'm not sure we want to add this to the manual. First, the current text clearly tries not to divulge the exact way of computing the name of the lockfile. Second, if and when this changes (and we've seen changes there just a year or two ago), someone will need to remember to go back and update the manual, which they will surely forget, which then will leave outdated information in the manual. Finally, this is not really a user-level stuff, so the user manual is not a good place for it to begin with. I'd be interested to hear Paul's take on this, as someone who worked on the related code not too long ago. Paul? Below I comment on the manual part of the patch, in case I will be outvoted eventually (whaat? how??). > 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 .# This index entry is not useful. Imagine a reader looking at the entry in the index -- will they understand what it's about? Probably not. Instead, I'd use this: @cindex .#, lock file names > 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. > 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. */) The place where you describe the form of the file name is sub-optimal. I'd instead do this in the doc string of create-lockfiles, it seems much more natural there. And I'd also add there a link to the doc string of lock-buffer. 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? Thanks. From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 15:06:11 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 19:06:11 +0000 Received: from localhost ([127.0.0.1]:54333 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNjwg-0006hW-S4 for submit@debbugs.gnu.org; Tue, 29 May 2018 15:06:11 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:55369) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNjwf-0006hK-Fh for 31636@debbugs.gnu.org; Tue, 29 May 2018 15:06:09 -0400 Received: by mail-wm0-f46.google.com with SMTP id a8-v6so43326070wmg.5 for <31636@debbugs.gnu.org>; Tue, 29 May 2018 12:06:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version:content-transfer-encoding; bh=4UnGrElk/zUJp8vdJaUKKkkU+cI9TqQlrJs1qW6Ngy4=; b=LF1L3ghBnz2wriVb7QhYulQuZwBejv8uFLLpYAGD82jHVuvtZYw4BFaFyVP/G56+zk k+A6kNM8nDzFW4GZu+r/gXrh59pxZl+LEmbfMC75GWBxZtNOWN5ULt1k5hwQGnoTSFrV j46KsWPvsRYaJg5X2NLzkPkkMJchGXAOVWV3E9bS8pcuk0qTocdH787ZOSg9xPNFfQdi VMVOdIYA+fjTTWKiTseI1cbp5mQ2VdPGvNu8EmANl8ccwmpvcyOZvq7qsmPWLlyeAqFe CmzIWdmLUCxQ5SnDV1aLxmT0HSkHtKrrCXXDoHlX9K1dcqfk9cisloVEsmIXbaS6DWSM iZaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=4UnGrElk/zUJp8vdJaUKKkkU+cI9TqQlrJs1qW6Ngy4=; b=pKfCqyKlBtq/TPNWkjD0D3LmTZA4Q9p9FKw8qnCA2tTQS3+REU8lfjajZ5XFS1wXWL Je/5MyvQzv/OOE3U2HyCW30X0zAvUyeTCfM9V+YKxWsSuoUJ3Ta0Rq9I+CiIJU+UgWbW 1nwnhyQ8EO+Cnb3ZpjhYhfYw/CiGjKTJ3Za6bwnW/3TmlaZGWT6x1hOnkm+bu2/axicx uNBojjwDti6nn36jpzs7K4hD8zhPOArbIGEgOnciVliEodro3Swa3aU+0kLDXSbVi9JJ AUibQnaXkSup6ccoQW5reRvEEgAJhHUYqsbNf7P0RCfTWudRJ/d0eD4f+rYCKyhfF0GT fGlg== X-Gm-Message-State: ALKqPwezgFNc5n5v4/nebqCDV5sjSOL29KjqMqN4UzFKbu6zoQcXHwCr Guz1GPOe4gyrxxBrgBM445s= X-Google-Smtp-Source: ADUXVKK+9ulVh1IZuBUGqOGxzdfsEGIO6tCoDS3DZMKWn6D0gVQY4XxRGlQ1SJSGcKdFfvt6s4gayA== X-Received: by 2002:a1c:7309:: with SMTP id d9-v6mr97078wmb.60.1527620763748; Tue, 29 May 2018 12:06:03 -0700 (PDT) Received: from rpluim (vav06-1-78-207-202-134.fbx.proxad.net. [78.207.202.134]) by smtp.gmail.com with ESMTPSA id s15-v6sm40414569wrg.70.2018.05.29.12.06.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 12:06:02 -0700 (PDT) From: Robert Pluim To: Eli Zaretskii Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> <87r2lufvo9.fsf@gmail.com> <83r2luv28h.fsf@gnu.org> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Tue, 29 May 2018 21:06:01 +0200 In-Reply-To: <83r2luv28h.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 May 2018 19:46:38 +0300") Message-ID: <87a7sib7ty.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, Paul Eggert , npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: > > 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=CA=BCt see a need to put all the details about that locking in the doc string. > But I'm > not sure we want to add this to the manual. First, the current text > clearly tries not to divulge the exact way of computing the name of > the lockfile. Second, if and when this changes (and we've seen > changes there just a year or two ago), someone will need to remember > to go back and update the manual, which they will surely forget, which > then will leave outdated information in the manual. Finally, this is > not really a user-level stuff, so the user manual is not a good place > for it to begin with. See my previous paragraph: the goal is to inform the user that file locking is occurring, so the user manual is a good place to make that clear (without necessarily going into the gory details). > I'd be interested to hear Paul's take on this, as someone who worked > on the related code not too long ago. Paul? > > Below I comment on the manual part of the patch, in case I will be > outvoted eventually (whaat? how??). Not by me: I trust your taste. >> 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 >>=20=20 >> @findex ask-user-about-lock >> @cindex locking files >> +@cindex .# > > This index entry is not useful. Imagine a reader looking at the entry > in the index -- will they understand what it's about? Probably not. > > Instead, I'd use this: > > @cindex .#, lock file names See, I=CA=BCve learnt something from you again, and the end result will be better for it :-) > >> 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? >> 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. >>=20=20 >> -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. */) > > The place where you describe the form of the file name is > sub-optimal. I'd instead do this in the doc string of > create-lockfiles, it seems much more natural there. And I'd also add > there a link to the doc string of lock-buffer. Makes sense. > 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=CA=BCt you make the point just now that this kind of detail could change and we=CA=BCd forget to update the documentation? Or did you want this in the elisp manual? Robert From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 15:20:59 2018 Received: (at 31636) by debbugs.gnu.org; 29 May 2018 19:20:59 +0000 Received: from localhost ([127.0.0.1]:54338 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNkB1-00072L-8d for submit@debbugs.gnu.org; Tue, 29 May 2018 15:20:59 -0400 Received: from zimbra.cs.ucla.edu ([131.179.128.68]:36446) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNkAz-000728-S4 for 31636@debbugs.gnu.org; Tue, 29 May 2018 15:20:58 -0400 Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D4DE91606C8; Tue, 29 May 2018 12:20:51 -0700 (PDT) Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id r0kwkjW4pxZn; Tue, 29 May 2018 12:20:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 184EE1606CA; Tue, 29 May 2018 12:20:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kyOFrzPvVouc; Tue, 29 May 2018 12:20:51 -0700 (PDT) Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id E9E431606C8; Tue, 29 May 2018 12:20:50 -0700 (PDT) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual To: Eli Zaretskii , Robert Pluim References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> <87r2lufvo9.fsf@gmail.com> <83r2luv28h.fsf@gnu.org> From: Paul Eggert Openpgp: preference=signencrypt Autocrypt: addr=eggert@cs.ucla.edu; prefer-encrypt=mutual; keydata= xsFNBEyAcmQBEADAAyH2xoTu7ppG5D3a8FMZEon74dCvc4+q1XA2J2tBy2pwaTqfhpxxdGA9 Jj50UJ3PD4bSUEgN8tLZ0san47l5XTAFLi2456ciSl5m8sKaHlGdt9XmAAtmXqeZVIYX/UFS 96fDzf4xhEmm/y7LbYEPQdUdxu47xA5KhTYp5bltF3WYDz1Ygd7gx07Auwp7iw7eNvnoDTAl KAl8KYDZzbDNCQGEbpY3efZIvPdeI+FWQN4W+kghy+P6au6PrIIhYraeua7XDdb2LS1en3Ss mE3QjqfRqI/A2ue8JMwsvXe/WK38Ezs6x74iTaqI3AFH6ilAhDqpMnd/msSESNFt76DiO1ZK QMr9amVPknjfPmJISqdhgB1DlEdw34sROf6V8mZw0xfqT6PKE46LcFefzs0kbg4GORf8vjG2 Sf1tk5eU8MBiyN/bZ03bKNjNYMpODDQQwuP84kYLkX2wBxxMAhBxwbDVZudzxDZJ1C2VXujC OJVxq2kljBM9ETYuUGqd75AW2LXrLw6+MuIsHFAYAgRr7+KcwDgBAfwhPBYX34nSSiHlmLC+ KaHLeCLF5ZI2vKm3HEeCTtlOg7xZEONgwzL+fdKo+D6SoC8RRxJKs8a3sVfI4t6CnrQzvJbB n6gxdgCu5i29J1QCYrCYvql2UyFPAK+do99/1jOXT4m2836j1wARAQABzSBQYXVsIEVnZ2Vy dCA8ZWdnZXJ0QGNzLnVjbGEuZWR1PsLBfgQTAQIAKAUCTIByZAIbAwUJEswDAAYLCQgHAwIG FQgCCQoLBBYCAwECHgECF4AACgkQ7ZfpDmKqfjRRGw/+Ij03dhYfYl/gXVRiuzV1gGrbHk+t nfrI/C7fAeoFzQ5tVgVinShaPkZo0HTPf18x6IDEdAiO8Mqo1yp0CtHmzGMCJ50o4Grgfjlr 6g/+vtEOKbhleszN2XpJvpwM2QgGvn/laTLUu8PH9aRWTs7qJJZKKKAb4sxYc92FehPu6FOD 0dDiyhlDAq4lOV2mdBpzQbiojoZzQLMQwjpgCTK2572eK9EOEQySUThXrSIz6ASenp4NYTFH s9tuJQvXk9gZDdPSl3bp+47dGxlxEWLpBIM7zIONw4ks4azgT8nvDZxA5IZHtvqBlJLBObYY 0Le61Wp0y3TlBDh2qdK8eYL426W4scEMSuig5gb8OAtQiBW6k2sGUxxeiv8ovWu8YAZgKJfu oWI+uRnMEddruY8JsoM54KaKvZikkKs2bg1ndtLVzHpJ6qFZC7QVjeHUh6/BmgvdjWPZYFTt N+KA9CWX3GQKKgN3uu988yznD7LnB98T4EUH1HA/GnfBqMV1gpzTvPc4qVQinCmIkEFp83zl +G5fCjJJ3W7ivzCnYo4KhKLpFUm97okTKR2LW3xZzEW4cLSWO387MTK3CzDOx5qe6s4a91Zu ZM/j/TQdTLDaqNn83kA4Hq48UHXYxcIh+Nd8k/3w6lFuoK0wrOFiywjLx+0ur5jmmbecBGHc 1xdhAFHOwU0ETIByZAEQAKaF678T9wyH4wjTrV1Pz3cDEoSnV/0ZUrOT37p1dcGyj/IXq1x6 70HRVahAmk0sZpYc25PF9D5GPYHFWlNjuPU96rDndXB3hedmBRhLdC4bAXjI4DV+bmdVe+q/ IMnlZRaVlm9EiMCVAR6w13sReu7qXkW9r3RwY2AzXskp/tAe4BRKr1Zmbvi2nbnQ6epEC42r Rbx0B1EhjbIQZ5JHGk24iPT7LdBgnNmos5wYjzwNlkMQD5T0Ydzhk7J+UxwA5m46mOhRDC2r FV/A0gm5TLy8DXjv/Esc4gYnYai6SQqnUEVh5LuV8YCJBnijs+Tiw71x1icmn6xGI45EugJO gec+rLypYgpVp4x0HI5T88qBRYCkxH3Kg8Qo+EWNA9A4LRQ9DX8njona0gf0s03tocK8kBN6 6UoqqPtHBnc4eMgBymCflK12eKfd2YYxnyg9cZazWA5VslvTxpm76hbg5oiAEH/Vg/8MxHyA nPhfrgwyPrmJEcVBafdspJnYQxBYNco2LFPIhlOvWh8r4at+s+M3Lb26oUTczlgdW1Sf3SDA 77BMRnF0FQyE+7AzV79MBN4ykiqaezQxtaF1Fy/tvkhffSo8u+dwG0EgJh+te38gTcISVr0G IPplLz6YhjrbHrPRF1CN5UuL9DBGjxuN35RLNVEfta6RUFlR6NctTjvrABEBAAHCwWUEGAEC AA8FAkyAcmQCGwwFCRLMAwAACgkQ7ZfpDmKqfjSrHA/+KzAKvTxRhA9MWNLxIyJ7S5uJ16gs T3oCjZrBKGEhKMOGX4O0GA6VOEryO7QRCCYah3oxSG38IAnNeiwJXgU9Bzkk85UGbPEd7HGF /VSeHCQwWou6jqUDTSDvn9YhNTdG0KXPM74aC+xr2Zow1O2mhXihgWKD0Dw+0LYPnUOsQ0KO FxHXXYHmRrS1OZPU59BLvc+TRhIhafSHKLwbXK+6ckkxBx6h8z5ccpG0Qs4bFhdFYnFrEieD LoGmnE2YLhdV6swJ9VNCS6pLiEohT3fm7aXm15tZOIyzMZhHRSAPblXxQ0ZSWjq8oRrcYNFx c4W1URpAkBCOYJoXvQfD5L3lqAl8TCqDUzYxhH/tJhbDdHrqHH767jaDaTB1+Talp/2AMKwc XNOdiklGxbmHVG6YGl6g8Lrbsu9NZEI4yLlHzuikthJWgz+3vZhVGyNlt+HNIoF6CjDL2omu 5cEq4RDHM44QqPk6l7O0pUvN1mT4B+S1b08RKpqm/ff015E37HNV/piIvJlxGAYz8PSfuGCB 1thMYqlmgdhd9/BabGFbGGYHA6U4/T5zqU+f6xHy1SsAQZ1MSKlLwekBIT+4/cLRGqCHjnV0 q5H/T6a7t5mPkbzSrOLSo4puj+IToNjYyYIDBWzhlA19avOa+rvUjmHtD3sFN7cXWtkGoi8b uNcby4U= Organization: UCLA Computer Science Department Message-ID: <52c8c394-add3-63c9-a62a-bea85e9d006e@cs.ucla.edu> Date: Tue, 29 May 2018 12:20:48 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <83r2luv28h.fsf@gnu.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) On 05/29/2018 09:46 AM, Eli Zaretskii wrote: > I'd be interested to hear Paul's take on this, as someone who worked > on the related code not too long ago. Paul? On the one hand this is low-level detail. On the other, it is user-visible detail, e.g., when I use dired or 'ls' on a directory I'll see the symlinks. So I'd be mildly inclined to see a brief mention in the user manual with details as necessary in the elisp manual. The user manual could say something simple like 'lock files are directory entries whose names begin with ".#"'. If more details are needed, they could be in the elisp manual (e.g., MS-Windows lock names are independent of lock names of other systems). From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 22:42:20 2018 Received: (at 31636) by debbugs.gnu.org; 30 May 2018 02:42:20 +0000 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 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 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 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.2 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 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 Date: Wed, 30 May 2018 05:42:02 +0300 Message-Id: <83in75vp8l.fsf@gnu.org> From: Eli Zaretskii To: Robert Pluim In-reply-to: <87a7sib7ty.fsf@gmail.com> (message from Robert Pluim on Tue, 29 May 2018 21:06:01 +0200) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > 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. From debbugs-submit-bounces@debbugs.gnu.org Tue May 29 22:42:47 2018 Received: (at 31636) by debbugs.gnu.org; 30 May 2018 02:42:47 +0000 Received: from localhost ([127.0.0.1]:54515 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNr4Z-0006Wc-E7 for submit@debbugs.gnu.org; Tue, 29 May 2018 22:42:47 -0400 Received: from eggs.gnu.org ([208.118.235.92]:36410) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fNr4X-0006WF-Sw for 31636@debbugs.gnu.org; Tue, 29 May 2018 22:42:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNr4P-0003NL-MQ for 31636@debbugs.gnu.org; Tue, 29 May 2018 22:42:40 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNr4P-0003NF-Hu; Tue, 29 May 2018 22:42:37 -0400 Received: from [176.228.60.248] (port=2267 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fNr4P-0006Bw-4V; Tue, 29 May 2018 22:42:37 -0400 Date: Wed, 30 May 2018 05:42:33 +0300 Message-Id: <83h8mpvp7q.fsf@gnu.org> From: Eli Zaretskii To: Paul Eggert In-reply-to: <52c8c394-add3-63c9-a62a-bea85e9d006e@cs.ucla.edu> (message from Paul Eggert on Tue, 29 May 2018 12:20:48 -0700) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual References: <20180529073311.EEA09102DA@mailuser.nyi.internal> <876036hn2e.fsf@gmail.com> <87tvqqd7rp.fsf@gmail.com> <87r2lufvo9.fsf@gmail.com> <83r2luv28h.fsf@gnu.org> <52c8c394-add3-63c9-a62a-bea85e9d006e@cs.ucla.edu> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, rpluim@gmail.com, npostavs@gmail.com, 31636@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > Cc: npostavs@gmail.com, mail@bradyt.com, 31636@debbugs.gnu.org > From: Paul Eggert > Date: Tue, 29 May 2018 12:20:48 -0700 > > On the one hand this is low-level detail. On the other, it is > user-visible detail, e.g., when I use dired or 'ls' on a directory I'll > see the symlinks. So I'd be mildly inclined to see a brief mention in > the user manual with details as necessary in the elisp manual. The user > manual could say something simple like 'lock files are directory entries > whose names begin with ".#"'. If more details are needed, they could be > in the elisp manual (e.g., MS-Windows lock names are independent of lock > names of other systems). OK, let's do it this way. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Thu May 31 06:30:06 2018 Received: (at 31636) by debbugs.gnu.org; 31 May 2018 10:30:07 +0000 Received: from localhost ([127.0.0.1]:55648 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOKqM-0004Mj-Gq for submit@debbugs.gnu.org; Thu, 31 May 2018 06:30:06 -0400 Received: from mail-wm0-f54.google.com ([74.125.82.54]:56228) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOKqK-0004Kx-3v for 31636@debbugs.gnu.org; Thu, 31 May 2018 06:30:04 -0400 Received: by mail-wm0-f54.google.com with SMTP id a8-v6so53045005wmg.5 for <31636@debbugs.gnu.org>; Thu, 31 May 2018 03:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version:content-transfer-encoding; bh=upnTFDeMGlYDwrdbOEb3SZyzghiG+ZDT/TegrnpeAMI=; b=VPW7jVRnJxpyRAb6PIBoQuGBNelUQK6OnA73MdIrpEwXA2dgEBamJyjhZGpYOL70lx vsZ8IGiOkNxwIFYVMWIZuK5jgMwfgU6Hh9PiuFv3/ZHH56mWwRRMAcQaeGeFwapuk0EK AVtzICbpIxNP4aqT8PM0o+DGxveiDlXaXj+4lPrTA7eWOKDWKXfKelk5nHanU3nUAIlr MSmUbSL4M4AFwNJZQEVnZpM2h2Mlh7BGoe2uXs5T5IVObjNXHKhbUywZrtIn/IpJuN+E c2BEJPcnDYxAV9iwlINiDCG6FozraV6Ni62a0ytbIPA9NfuJoIup5WU7tWsgOOlkKmLi IERQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=upnTFDeMGlYDwrdbOEb3SZyzghiG+ZDT/TegrnpeAMI=; b=DAdkSP9+52kfDf1WBZ/fT9Y/RCsaLt0SxG2ByLcFKIn40e6YxEadJQ/fzw9X1ZwvFc m3j5HWSNRTb1tx69q/FNJrebl71j8EuH7EdETDGIQPld+Ptvh4obyjkJP2i627WZunsF vRMH+Kx/XZHTqpkNWj6AXo8aB80XTd+UOkrBu3jK5MFpEIfUzUZupCL2EAGpkEmOrpp9 GxCP4PuCqgcuQrALSPTUDEU74DUqKrYBRRKCzQJ8bcS2Tnk/SEIDnxDrXwbOLi45hamw Nj12p4M2eK7g3ZLh3F2fxE/ygDdjKHteTNE/z7f/5J9+p1d/o+2G3lc1B30+TqIIG1BV D5lQ== X-Gm-Message-State: APt69E1rxIw7F3e5BkGPaLu8rEEVs4+wgv0X6WtqKIX/oDyrN3wgD22Q VsrMYXpMAZfYkONGjW8221k= X-Google-Smtp-Source: ADUXVKLHq/nmsPSITy6pw5fsuoi3iaqiHdPkiN1THdDJRhxwvraAMqJ1IHa/tt9jC4Rw2Y9I8Qqejg== X-Received: by 2002:a1c:824b:: with SMTP id e72-v6mr3874150wmd.64.1527762598372; Thu, 31 May 2018 03:29:58 -0700 (PDT) Received: from rpluim ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id a69-v6sm800196wma.7.2018.05.31.03.29.56 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 03:29:57 -0700 (PDT) From: Robert Pluim To: Eli Zaretskii Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> <83in75vp8l.fsf@gnu.org> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Thu, 31 May 2018 12:29:54 +0200 In-Reply-To: <83in75vp8l.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 30 May 2018 05:42:02 +0300") Message-ID: <87wovkyv6l.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> > 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? >>=20 >> Didn=CA=BCt you make the point just now that this kind of detail could >> change and we=CA=BCd forget to update the documentation? Or did you want >> this in the elisp manual? > > The latter. So what I currently have is below. create-lockfiles references the user manual (and 'lock-buffer') which in turn references the lisp reference manual. Do we want a '.#' index entry in the lispref as well? Do I need to explain that USER will be replaced by the current user, etc? Let the wordsmithing begin! 2018-05-31 Robert Pluim * src/filelock.c (create-lockfiles): Add cross reference to file locking in user manual and to 'lock-buffer'. Add string '.#' to help users find the doc string. * doc/emacs/files.texi (Interlocking): Point user at detailed file locking description in lisp reference manual. Add index entry for '.#' to improve disoverability of information about locking. * doc/lispref/files.texi (File Locks): Describe in detail what the form of the lock file is. diff --git i/doc/emacs/files.texi w/doc/emacs/files.texi index 1ced7ca07c..406e7d980c 100644 --- i/doc/emacs/files.texi +++ w/doc/emacs/files.texi @@ -766,13 +766,16 @@ Interlocking =20 @findex ask-user-about-lock @cindex locking files +@cindex .#, lock file names +@cindex file locking 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 your file system does not support symbolic links, a regular file is -used.} with special contents in the same directory.) Emacs removes the lo= ck -when you save the changes. The idea is that the file is locked -whenever an Emacs buffer visiting it has unsaved changes. +used.} with special contents in the same directory. @xref{File +Locks,,, elisp} for more details.) Emacs removes the lock when you +save the changes. The idea is that the file is locked whenever an +Emacs buffer visiting it has unsaved changes. =20 @vindex create-lockfiles You can prevent the creation of lock files by setting the variable diff --git i/doc/lispref/files.texi w/doc/lispref/files.texi index f62b670f47..89a98bd588 100644 --- i/doc/lispref/files.texi +++ w/doc/lispref/files.texi @@ -720,8 +720,13 @@ File Locks Emacs can then detect the first attempt to modify a buffer visiting a file that is locked by another Emacs job, and ask the user what to do. The file lock is really a file, a symbolic link with a special name, -stored in the same directory as the file you are editing. (On file -systems that do not support symbolic links, a regular file is used.) +stored in the same directory as the file you are editing. The name is +constructed by prepending @file{.#} to the filename of the buffer. +The target of the symbolic link will be of the form +@code{USER@@HOST.PID:BOOT}. @code{:BOOT} is omitted if the boot time +is unavailable. (On file systems that do not support symbolic links, +a regular file is used instead, with contents of the form +@code{USER@@HOST.PID:BOOT}.) =20 When you access files using NFS, there may be a small probability that you and another user will both lock the same file simultaneously. diff --git i/src/filelock.c w/src/filelock.c index f2dc723407..4f7ec414f5 100644 --- i/src/filelock.c +++ w/src/filelock.c @@ -849,7 +849,9 @@ syms_of_filelock (void) Vtemporary_file_directory =3D Qnil; =20 DEFVAR_BOOL ("create-lockfiles", create_lockfiles, - doc: /* Non-nil means use lockfiles to avoid editing collisions. = */); + doc: /* Non-nil means use lockfiles to avoid editing collisions. +The names of the lockfiles will start with `.#'. See also +`lock-buffer' and Info node `(emacs)Interlocking'. */); create_lockfiles =3D 1; =20 defsubr (&Sunlock_buffer); From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 01 04:53:00 2018 Received: (at 31636) by debbugs.gnu.org; 1 Jun 2018 08:53:00 +0000 Received: from localhost ([127.0.0.1]:56790 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOfnw-0006I4-3H for submit@debbugs.gnu.org; Fri, 01 Jun 2018 04:53:00 -0400 Received: from eggs.gnu.org ([208.118.235.92]:57332) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOfnu-0006Hr-8e for 31636@debbugs.gnu.org; Fri, 01 Jun 2018 04:52:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fOfno-0001jj-1R for 31636@debbugs.gnu.org; Fri, 01 Jun 2018 04:52:53 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37636) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fOfnh-0001fs-6g; Fri, 01 Jun 2018 04:52:45 -0400 Received: from [176.228.60.248] (port=3953 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fOfng-0008JD-Cz; Fri, 01 Jun 2018 04:52:44 -0400 Date: Fri, 01 Jun 2018 11:52:42 +0300 Message-Id: <83tvqmga79.fsf@gnu.org> From: Eli Zaretskii To: Robert Pluim In-reply-to: <87wovkyv6l.fsf@gmail.com> (message from Robert Pluim on Thu, 31 May 2018 12:29:54 +0200) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> <83in75vp8l.fsf@gnu.org> <87wovkyv6l.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > From: Robert Pluim > Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com > Date: Thu, 31 May 2018 12:29:54 +0200 > > Do we want a '.#' index entry in the lispref as well? Yes. > Do I need to explain that USER will be replaced by the current user, > etc? Yes, I think so. > --- i/doc/emacs/files.texi > +++ w/doc/emacs/files.texi > @@ -766,13 +766,16 @@ Interlocking > > @findex ask-user-about-lock > @cindex locking files > +@cindex .#, lock file names > +@cindex file locking > 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 > 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 > -whenever an Emacs buffer visiting it has unsaved changes. > +used.} with special contents in the same directory. @xref{File > +Locks,,, elisp} for more details.) Emacs removes the lock when you > +save the changes. The idea is that the file is locked whenever an > +Emacs buffer visiting it has unsaved changes. This is OK. > --- i/doc/lispref/files.texi > +++ w/doc/lispref/files.texi > @@ -720,8 +720,13 @@ File Locks > Emacs can then detect the first attempt to modify a buffer visiting a > file that is locked by another Emacs job, and ask the user what to do. > The file lock is really a file, a symbolic link with a special name, > -stored in the same directory as the file you are editing. (On file > -systems that do not support symbolic links, a regular file is used.) > +stored in the same directory as the file you are editing. The name is > +constructed by prepending @file{.#} to the filename of the buffer. > +The target of the symbolic link will be of the form > +@code{USER@@HOST.PID:BOOT}. @code{:BOOT} is omitted if the boot time > +is unavailable. (On file systems that do not support symbolic links, > +a regular file is used instead, with contents of the form > +@code{USER@@HOST.PID:BOOT}.) This should use @var{user}, @var{host} etc. for the components of the target file name, and it should explain shortly what each component stands for. > diff --git i/src/filelock.c w/src/filelock.c > index f2dc723407..4f7ec414f5 100644 > --- i/src/filelock.c > +++ w/src/filelock.c > @@ -849,7 +849,9 @@ syms_of_filelock (void) > Vtemporary_file_directory = Qnil; > > DEFVAR_BOOL ("create-lockfiles", create_lockfiles, > - doc: /* Non-nil means use lockfiles to avoid editing collisions. */); > + doc: /* Non-nil means use lockfiles to avoid editing collisions. > +The names of the lockfiles will start with `.#'. See also > +`lock-buffer' and Info node `(emacs)Interlocking'. */); Here I would say that the name of the lockfile is constructed by prepending a '.#' to the name of the file being locked. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 01 06:48:03 2018 Received: (at 31636) by debbugs.gnu.org; 1 Jun 2018 10:48:04 +0000 Received: from localhost ([127.0.0.1]:56845 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOhbH-0000dr-GE for submit@debbugs.gnu.org; Fri, 01 Jun 2018 06:48:03 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:54848) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOhbG-0000dH-0G for 31636@debbugs.gnu.org; Fri, 01 Jun 2018 06:48:02 -0400 Received: by mail-wm0-f68.google.com with SMTP id o13-v6so2159315wmf.4 for <31636@debbugs.gnu.org>; Fri, 01 Jun 2018 03:48:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:message-id:mime-version:content-transfer-encoding; bh=LPejr6STdSOIqGsE1B4PoP0wrIW11420hk+GwChMKEQ=; b=BceoqXEIhbaC97TRzpb4PyLhJmD5iT7KThHHcYorJXNI4ctDEbYR/hUvsqeZWCIc7L msj5pqM4a5iW8bUCX1zPmstpVoEsezNa1exR5RX901skDWyVY0lDqHJO4Ht5WxqzbSIr +VVseJozGBeoXWCxDOFerx/5qwViLXG6k3EqBbTAHPU+PN7ldcQVNL9DA+HIMRbGHz+X QxIH991ewkUnWe3tyqPI1s246BpNdLEdFxsZol47Y9qfmoKEvUlLmK992ALepIHF6iOn nGIXWvhHMr9WsCHGYBZ18wlL7385BKYpp9X672EZJBYA1KCWbxeZUVj45EoEbMoh32V1 Ymbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:message-id:mime-version :content-transfer-encoding; bh=LPejr6STdSOIqGsE1B4PoP0wrIW11420hk+GwChMKEQ=; b=g2kEJPwrX57YOnnzuVGvJCYyy1OPNBcB+dc60g5ZFQIvpOvWFsNFLURRflZ4WD6/Ix xiBExzovcJbxyRPe1aBzpeBumFEdyJpNgJXnUcRk9rmoR4FApAZPupIophBr5VdrFass jMA9Qng+lYJlBUagphJAFsSmqTkUGHhkXddjn6YLv8seJyFmFKZWlJoDT93KsFwhb9Oo teq5pjPZ5EM1St5paiQcGeA2K0UCProf/DUYV2sGdos4yRR7EZQOqAODvRgq+Ox+hi1U vqw/lct2zw0UXq0t+nm8tztyBG9m6iK7w1pWO4nNvGpqJnpsxO2lZxOVJ1VPGfIby5zP OcVA== X-Gm-Message-State: ALKqPwcxFXXPRUnh0MEFPdRLTcjo0hHWmuWnp4E9CpRpn3E3Rwkh4uj7 jkNczg41DvanB4sUJ4QsFOY= X-Google-Smtp-Source: ADUXVKJT2/jImCIdBr6D54WTbnklC8s2zPOQD75D1CW+AuHvF5IH2xcr0L2aL5wJKUVelEpFmsocRw== X-Received: by 2002:a1c:e619:: with SMTP id d25-v6mr2110726wmh.23.1527850075998; Fri, 01 Jun 2018 03:47:55 -0700 (PDT) Received: from rpluim-ubuntu ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id m64-v6sm2995730wmb.12.2018.06.01.03.47.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 03:47:54 -0700 (PDT) From: Robert Pluim To: Eli Zaretskii Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> <83in75vp8l.fsf@gnu.org> <87wovkyv6l.fsf@gmail.com> <83tvqmga79.fsf@gnu.org> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Fri, 01 Jun 2018 12:47:54 +0200 Message-ID: <87h8mmu6jp.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> From: Robert Pluim >> Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npost= avs@gmail.com >> Date: Thu, 31 May 2018 12:29:54 +0200 >>=20 >> Do we want a '.#' index entry in the lispref as well? > > Yes. > Done. >> Do I need to explain that USER will be replaced by the current user, >> etc? > > Yes, I think so. I should have known better than to ask. Done. I even gritted my teeth and wrote "Emacs's". > This should use @var{user}, @var{host} etc. for the components of the > target file name, and it should explain shortly what each component > stands for. I don=CA=BCt see any difference in the visual appearance from using @var, but I made the change anyway, and expanded the explanation (I noticed that texinfo.el has no bindings for inserting @ref, @xref, and @pxref, should I add some? C-cC-c[rp] are free, but x is already used for @example, so 'C-cC-cX'? Or maybe 'C-cC-cC-x' for @xref?) > Here I would say that the name of the lockfile is constructed by > prepending a '.#' to the name of the file being locked. Done. 2018-05-31 Robert Pluim * src/filelock.c (create-lockfiles): Add cross reference to file locking in user manual and to 'lock-buffer'. Add string '.#' to help users find the doc string. * doc/emacs/files.texi (Interlocking): Point user at detailed file locking description in lisp reference manual. Add index entry for '.#' to improve disoverability of information about locking. * doc/lispref/files.texi (File Locks): Describe in detail what the form of the lock file is. Add index entry for '.#' to improve disoverability of information about locking. diff --git i/doc/emacs/files.texi w/doc/emacs/files.texi index 1ced7ca07c..406e7d980c 100644 --- i/doc/emacs/files.texi +++ w/doc/emacs/files.texi @@ -766,13 +766,16 @@ Interlocking =20 @findex ask-user-about-lock @cindex locking files +@cindex .#, lock file names +@cindex file locking 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 your file system does not support symbolic links, a regular file is -used.} with special contents in the same directory.) Emacs removes the lo= ck -when you save the changes. The idea is that the file is locked -whenever an Emacs buffer visiting it has unsaved changes. +used.} with special contents in the same directory. @xref{File +Locks,,, elisp} for more details.) Emacs removes the lock when you +save the changes. The idea is that the file is locked whenever an +Emacs buffer visiting it has unsaved changes. =20 @vindex create-lockfiles You can prevent the creation of lock files by setting the variable diff --git i/doc/lispref/files.texi w/doc/lispref/files.texi index f62b670f47..012a7a0a7c 100644 --- i/doc/lispref/files.texi +++ w/doc/lispref/files.texi @@ -712,6 +712,7 @@ File Locks @section File Locks @cindex file locks @cindex lock file +@cindex .#, lock file names =20 When two users edit the same file at the same time, they are likely to interfere with each other. Emacs tries to prevent this situation @@ -720,8 +721,17 @@ File Locks Emacs can then detect the first attempt to modify a buffer visiting a file that is locked by another Emacs job, and ask the user what to do. The file lock is really a file, a symbolic link with a special name, -stored in the same directory as the file you are editing. (On file -systems that do not support symbolic links, a regular file is used.) +stored in the same directory as the file you are editing. The name is +constructed by prepending @file{.#} to the filename of the buffer. +The target of the symbolic link will be of the form +@code{@var{user}@@@var{host}.@var{pid}:@var{boot}}, where @var{user} +is replaced with the current username (from @code{user-login-name}), +@var{host} with the name of the host where Emacs is running (from +@code{system-name}), @var{pid} with Emacs's process id, and @var{boot} +with the time since the last reboot. @code{:@var{boot}} is omitted if +the boot time is unavailable. (On file systems that do not support +symbolic links, a regular file is used instead, with contents of the +form @code{@var{user}@@@var{host}.@var{pid}:@var{boot}}.) =20 When you access files using NFS, there may be a small probability that you and another user will both lock the same file simultaneously. diff --git i/src/filelock.c w/src/filelock.c index f2dc723407..d33063c879 100644 --- i/src/filelock.c +++ w/src/filelock.c @@ -849,7 +849,10 @@ syms_of_filelock (void) Vtemporary_file_directory =3D Qnil; =20 DEFVAR_BOOL ("create-lockfiles", create_lockfiles, - doc: /* Non-nil means use lockfiles to avoid editing collisions. = */); + doc: /* Non-nil means use lockfiles to avoid editing collisions. +The name of the (per-buffer) lockfile is constructed by prepending a +'.#' to the name of the file being locked. See also `lock-buffer' and +Info node `(emacs)Interlocking'. */); create_lockfiles =3D 1; =20 defsubr (&Sunlock_buffer); From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 01 09:00:40 2018 Received: (at 31636) by debbugs.gnu.org; 1 Jun 2018 13:00:40 +0000 Received: from localhost ([127.0.0.1]:56941 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOjfc-0007jd-Eg for submit@debbugs.gnu.org; Fri, 01 Jun 2018 09:00:40 -0400 Received: from eggs.gnu.org ([208.118.235.92]:56807) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOjfY-0007jO-VK for 31636@debbugs.gnu.org; Fri, 01 Jun 2018 09:00:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fOjfN-0002b5-OP for 31636@debbugs.gnu.org; Fri, 01 Jun 2018 09:00:31 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=BAYES_20 autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53217) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fOjfE-0002Rw-PO; Fri, 01 Jun 2018 09:00:16 -0400 Received: from [176.228.60.248] (port=4445 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fOjfD-0001XP-KC; Fri, 01 Jun 2018 09:00:16 -0400 Date: Fri, 01 Jun 2018 16:00:15 +0300 Message-Id: <83k1rifyqo.fsf@gnu.org> From: Eli Zaretskii To: Robert Pluim In-reply-to: <87h8mmu6jp.fsf@gmail.com> (message from Robert Pluim on Fri, 01 Jun 2018 12:47:54 +0200) Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> <83in75vp8l.fsf@gnu.org> <87wovkyv6l.fsf@gmail.com> <83tvqmga79.fsf@gnu.org> <87h8mmu6jp.fsf@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 31636 Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > From: Robert Pluim > Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com > Date: Fri, 01 Jun 2018 12:47:54 +0200 > > > This should use @var{user}, @var{host} etc. for the components of the > > target file name, and it should explain shortly what each component > > stands for. > > I donʼt see any difference in the visual appearance from using @var, In Info format, you won't see any difference, because @var up-cases its argument in that format. But in the printed manual the visual appearance of @var is very different: it gives the argument the slanted typeface and doesn't up-case it. > (I noticed that texinfo.el has no bindings for inserting @ref, > @xref, and @pxref, should I add some? C-cC-c[rp] are free, but x is > already used for @example, so 'C-cC-cX'? Or maybe 'C-cC-cC-x' for > @xref?) How about using just "C-c C-c r" and letting it intuit the exact form from the context? @xref is only used at the beginning of a sentence, and @pxref should normally follow an open paren. In any case, adding this to texinfo.el would be a welcome addition, I think. The patch LGTM, thanks. From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 01 09:24:29 2018 Received: (at 31636-done) by debbugs.gnu.org; 1 Jun 2018 13:24:29 +0000 Received: from localhost ([127.0.0.1]:56951 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOk2e-0008H1-Qq for submit@debbugs.gnu.org; Fri, 01 Jun 2018 09:24:29 -0400 Received: from mail-wm0-f50.google.com ([74.125.82.50]:37360) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOk2d-0008Gp-E3 for 31636-done@debbugs.gnu.org; Fri, 01 Jun 2018 09:24:27 -0400 Received: by mail-wm0-f50.google.com with SMTP id l1-v6so2638982wmb.2 for <31636-done@debbugs.gnu.org>; Fri, 01 Jun 2018 06:24:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version:content-transfer-encoding; bh=XI/ng88Izj67oMXRQLbAe/yFcIo1RpILhC+Yvfp9wQg=; b=tzdZw3yyUgVTEPlS5r1mIYu63qgS/e1ZtOrlosYU5A/NppvXh+fyl3mcL3U136NsMP 52A4DRidebRV8PvS7Ew5r+8n9dZmYjC0ewZOYVKBCP6ncm05WzyhQRD4CkdfHZ/Cm4la fBR4PxWfhpH0HuAsa8Bh61+B5cN19BD8295bb6GrDz+fJyyYrWy4ReWJAEZLKnMP7hSi LkhOtKao5fKK1xO/1rsMhrqgqcLzlmmrthqLY6MOIqWd2Z2Jm4e0pTi13BImV69+sKes tftcE2PAfLdTKTUrWtZuDE5FyDGQKW1UKpdOvBjwvh6lrc9Tzco2JwmF7bV5FFmbfOQl YUNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=XI/ng88Izj67oMXRQLbAe/yFcIo1RpILhC+Yvfp9wQg=; b=D7+Dk7gVTNLt1Qmn2YRvpn1mwk2UtbW/Ooyf9cxvQCrjGpmMIfxbUHa5QpWBmxPE6H xyOu2ABIEZUzHpKLAURYq53BgdiO8ifXugaCrhFTKTzBdSvlZj7FwVPdXKTYCla/S4+d go02uY1WHSLa3uyWcozyficin0ekGA+fFU3fjir8NMQzKlX4hsOcXyRoJrBX0Ex/2oC7 vMRwG2NmaYA8JAV2DfHceDrWYnrKmuvcyN4d+WpXAhxhMN+fehO1SR1H627fChYTMv5g hhQ9JzXpEkirB2YUNJOiopaa7djm0vcpFfdWnSDNmoqzuRitHMLevQ8n+zZzjKPT3adM +guA== X-Gm-Message-State: ALKqPwf922TG4PvAiOeeD3B/XjeeUVTNxCUQUZhfDtU8PO6mtmw3Kci/ sSoUV/wFEQlM7qjRX5IxoAQ= X-Google-Smtp-Source: ADUXVKJ/lE1IBMhk8aXXiNNnuPoynpTlLMp9TjYRuJW6VyBjxe5IflsIQVeskWFul3ZG68J2k2i6Ng== X-Received: by 2002:a1c:6fce:: with SMTP id c75-v6mr2597832wmi.83.1527859461487; Fri, 01 Jun 2018 06:24:21 -0700 (PDT) Received: from rpluim-ubuntu ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id s132-v6sm1549512wmf.5.2018.06.01.06.24.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 06:24:20 -0700 (PDT) From: Robert Pluim To: Eli Zaretskii Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual 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> <83in75vp8l.fsf@gnu.org> <87wovkyv6l.fsf@gmail.com> <83tvqmga79.fsf@gnu.org> <87h8mmu6jp.fsf@gmail.com> <83k1rifyqo.fsf@gnu.org> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Fri, 01 Jun 2018 15:24:19 +0200 In-Reply-To: <83k1rifyqo.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Jun 2018 16:00:15 +0300") Message-ID: <877enitzb0.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 31636-done Cc: mail@bradyt.com, 31636-done@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> (I noticed that texinfo.el has no bindings for inserting @ref, >> @xref, and @pxref, should I add some? C-cC-c[rp] are free, but x is >> already used for @example, so 'C-cC-cX'? Or maybe 'C-cC-cC-x' for >> @xref?) > > How about using just "C-c C-c r" and letting it intuit the exact form > from the context? @xref is only used at the beginning of a sentence, > and @pxref should normally follow an open paren. > OK. I=CA=BCll think about how best to add that > In any case, adding this to texinfo.el would be a welcome addition, I > think. > > The patch LGTM, thanks. Pushed as 9188291f7a to emacs-26. Thanks Robert From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 01 09:26:08 2018 Received: (at 31636-done) by debbugs.gnu.org; 1 Jun 2018 13:26:08 +0000 Received: from localhost ([127.0.0.1]:56958 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOk4G-0008Jd-5W for submit@debbugs.gnu.org; Fri, 01 Jun 2018 09:26:08 -0400 Received: from mail-wr0-f179.google.com ([209.85.128.179]:33254) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fOk4E-0008JF-KS for 31636-done@debbugs.gnu.org; Fri, 01 Jun 2018 09:26:07 -0400 Received: by mail-wr0-f179.google.com with SMTP id k16-v6so9120837wro.0 for <31636-done@debbugs.gnu.org>; Fri, 01 Jun 2018 06:26:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:mail-copies-to :gmane-reply-to-list:date:message-id:mime-version :content-transfer-encoding; bh=clknWVlkYhl20Asx4LdlgcpV2kKdrvm6sBFesImXdEU=; b=rJ/WQhZCFmcs4ZmzT9FzplMuP245xozTqY/gwqjyhnUjkJPNPSEaD7LpyPHluFZoVE v4h4KMkScbPA8x41SHSyPZz0BYOpxe380XzlOpkImZSs/3NvGicivMn2k24IigbCDCXW V0V79qTosYmFe8ouHOzgdG9827Qb8JhhbH+HqCXjlbslA1Cu5znSVt11D5YmiZMyUD/3 Fx3Pbu6FOMZHZg+a0Qm1vsf7B/0XQ8w5E3Ws4InBil+AEaTDctXljqwPrdVS/QrMoFS2 GgNwSwDTdQWRl01BQ42d6bvwsp3fEbti5T6H4EArrrwueayM7KGX4XVb9MDCcjlxkc1f XJkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :mail-copies-to:gmane-reply-to-list:date:message-id:mime-version :content-transfer-encoding; bh=clknWVlkYhl20Asx4LdlgcpV2kKdrvm6sBFesImXdEU=; b=NduQnPb1RGEFCtOz0MDvXL9/VWw7myHQv3Xku79AAfmbY7sS0Xexv1QcRKAxe6F0+1 0i0mGveishN4eIba07N6/bgJNmJXDVHKFyIQ8bpnaefXklxxO/Sxn9nBGTuSu/RE0/nY fDWYyShDsgP6cO1j8v/Qvu5c5weKeqXAsHoRF+QxbQaP1PPMw7E3VNc/rRk4b1UTzenf T2pF0VJdiq19Z9tFwxt0DbJ17bwP4JiTAP+by8gL60xHZsqX4fXzZ0KYYzsv5RQo+kSe B+IDNOY17jpZaDr21RW2Yz42+52Hj05ZBQ46A4HJnHfPP4z0WmiXTn0TrXS/9N+hDdue DL+g== X-Gm-Message-State: ALKqPwcTZRLC3+gjjFq+j0seJv78mfKrDfNN+evCQa5PnpIpyqWa+g1i A7M7SdNqExr/kutKJPXUlsI= X-Google-Smtp-Source: ADUXVKLHXExskyZvlxRhmihg9bWeLAVRItU8vn+8gSWbbae4aF5i/GRRj1IBaLBBoTFIWF7r1QI0zw== X-Received: by 2002:adf:8854:: with SMTP id e20-v6mr9400142wre.30.1527859560799; Fri, 01 Jun 2018 06:26:00 -0700 (PDT) Received: from rpluim-ubuntu ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id 75-v6sm3007218wmw.37.2018.06.01.06.25.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 06:26:00 -0700 (PDT) From: Robert Pluim To: Eli Zaretskii Subject: Re: bug#31636: 27.0.50; lockfile syntax searchable from info manual In-Reply-To: <83k1rifyqo.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Jun 2018 16:00:15 +0300") 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> <83in75vp8l.fsf@gnu.org> <87wovkyv6l.fsf@gmail.com> <83tvqmga79.fsf@gnu.org> <87h8mmu6jp.fsf@gmail.com> <83k1rifyqo.fsf@gnu.org> X-Debbugs-No-Ack: yes Mail-Copies-To: never Gmane-Reply-To-List: yes Date: Fri, 01 Jun 2018 15:25:59 +0200 Message-ID: <87y3fyskns.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.7 (-) X-Debbugs-Envelope-To: 31636-done Cc: mail@bradyt.com, 31636-done@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.7 (--) Eli Zaretskii writes: >> (I noticed that texinfo.el has no bindings for inserting @ref, >> @xref, and @pxref, should I add some? C-cC-c[rp] are free, but x is >> already used for @example, so 'C-cC-cX'? Or maybe 'C-cC-cC-x' for >> @xref?) > > How about using just "C-c C-c r" and letting it intuit the exact form > from the context? @xref is only used at the beginning of a sentence, > and @pxref should normally follow an open paren. > OK. I=CA=BCll think about how best to add that. > In any case, adding this to texinfo.el would be a welcome addition, I > think. > > The patch LGTM, thanks. Pushed as 9188291f7a to emacs-26. Thanks Robert From unknown Mon Jun 23 06:03:28 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Sat, 30 Jun 2018 11:24:05 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator