From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: mail@bradyt.com, rpluim@gmail.com, npostavs@gmail.com,
31636@debbugs.gnu.org
Subject: bug#31636: 27.0.50; lockfile syntax searchable from info manual
Date: Wed, 30 May 2018 05:42:33 +0300 [thread overview]
Message-ID: <83h8mpvp7q.fsf@gnu.org> (raw)
In-Reply-To: <52c8c394-add3-63c9-a62a-bea85e9d006e@cs.ucla.edu> (message from Paul Eggert on Tue, 29 May 2018 12:20:48 -0700)
> Cc: npostavs@gmail.com, mail@bradyt.com, 31636@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 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.
prev parent reply other threads:[~2018-05-30 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 7:33 bug#31636: 27.0.50; lockfile syntax searchable from info manual Brady Trainor
2018-05-29 8:40 ` Robert Pluim
2018-05-29 11:24 ` Noam Postavsky
2018-05-29 13:17 ` Robert Pluim
2018-05-29 16:46 ` Eli Zaretskii
2018-05-29 19:06 ` Robert Pluim
2018-05-30 2:42 ` Eli Zaretskii
2018-05-31 10:29 ` Robert Pluim
2018-06-01 8:52 ` Eli Zaretskii
2018-06-01 10:47 ` Robert Pluim
2018-06-01 13:00 ` Eli Zaretskii
2018-06-01 13:24 ` Robert Pluim
2018-06-01 13:25 ` Robert Pluim
2018-05-29 19:20 ` Paul Eggert
2018-05-30 2:42 ` Eli Zaretskii [this message]
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=83h8mpvp7q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31636@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=mail@bradyt.com \
--cc=npostavs@gmail.com \
--cc=rpluim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).