unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 34911@debbugs.gnu.org
Subject: bug#34911: 26.1; doc about lock file names
Date: Mon, 18 Mar 2019 15:47:52 -0700 (PDT)	[thread overview]
Message-ID: <db8aca56-6185-4e1a-a627-53aed26103c2@default> (raw)

I started from the doc of `dired-omit-files', which says:

  The default is to omit `.', `..', auto-save files and lock files.
                                                        ^^^^^^^^^^

And the default value is this: "^\\.?#\\|^\\.$\\|^\\.\\.$"

I can only guess that a lock file has either the same syntax as (the
default syntax of) an auto-save file: `#...#', or that prefixed by `.':
`.#...#'.  In fact, it's a stretch to guess even that, as the ^\.?#
doesn't necessarily match even an auto-save file (no # appended).

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 miss
it somehow, or is it defined/described nowhere?

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'.

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.

In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
 of 2018-05-30
Repository revision: 07f8f9bc5a51f5aa94eb099f3e15fbe0c20ea1ea
Windowing system distributor `Microsoft Corp.', version 10.0.17134
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''





             reply	other threads:[~2019-03-18 22:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 22:47 Drew Adams [this message]
2019-03-18 23:17 ` bug#34911: 26.1; doc about lock file names Glenn Morris
2019-03-19  0:28   ` Drew Adams
2019-03-19  7:07   ` Eli Zaretskii
2019-03-19  6:56 ` Eli Zaretskii
2019-03-19 11:49   ` Eli Zaretskii
     [not found] <<db8aca56-6185-4e1a-a627-53aed26103c2@default>
     [not found] ` <<83bm27uzbr.fsf@gnu.org>
2019-03-19 14:54   ` Drew Adams
2019-03-19 18:23     ` Eli Zaretskii
2019-05-12 16:34     ` Noam Postavsky
2019-05-19 14:43       ` Noam Postavsky
2019-05-19 15:04         ` Drew Adams
2019-05-19 15:11           ` Noam Postavsky
2019-05-19 16:29             ` Drew Adams
2019-05-19 17:22               ` Noam Postavsky
2019-05-19 19:49                 ` Drew Adams
2020-08-26 10:39       ` Lars Ingebrigtsen
2020-08-26 16:55         ` Drew Adams
     [not found] <<<db8aca56-6185-4e1a-a627-53aed26103c2@default>
     [not found] ` <<<83bm27uzbr.fsf@gnu.org>
     [not found]   ` <<a916e9f9-e66e-40b8-b02d-1d697108774e@default>
     [not found]     ` <<83r2b2u3j4.fsf@gnu.org>
2019-03-19 20:15       ` Drew Adams
2019-03-19 20:23         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db8aca56-6185-4e1a-a627-53aed26103c2@default \
    --to=drew.adams@oracle.com \
    --cc=34911@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).