unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23033@debbugs.gnu.org, Michael Sloan <mgsloan@gmail.com>
Subject: bug#23033: 24.5; Lock file uses the same extension as the file it's locking
Date: Sat, 9 Nov 2019 10:12:11 +0100	[thread overview]
Message-ID: <CADwFkmmRgDqA-f2Ls=jxFVPyD_nzy82Z3WMORhdLQTELrBAUvA@mail.gmail.com> (raw)
In-Reply-To: <83imnta3y6.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> > I propose keeping the traditional `.#` prefix but adding a `.lock` suffix.

OK, if that works on Windows it's better than what I proposed.

> I think we should only consider adding punctuation characters, because
> that would ensure these lock files are displayed right next to the
> files they lock, like today.  Moving the lock files away of the files
> they lock in the directory listing would be a disadvantage, IMO.

On this MacOS machine, I see the following:

$ ls -al
total 8
drwxr-xr-x  11 skangas  staff   352 Nov  9 10:05 .
lrwxr-xr-x   1 skangas  staff    33 Nov  9 10:05 .#foo ->
skangas@example.org.795
drwxr-xr-x  50 skangas  staff  1600 Nov  9 10:03 ..
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 a
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 e
-rw-r--r--   1 skangas  staff     3 Nov  9 10:05 foo
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 i
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 z

In other words, the lock file is not next to the file it locks.  Are
you seeing something else?

How would the ordering differ with a suffix like ".lock" compared to
"#" or some other punctuation character?  I would have thought that it
would be very similar.  Maybe I'm missing something.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-09  9:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 21:35 bug#23033: 24.5; Lock file uses the same extension as the file it's locking Michael Sloan
2016-03-19  2:09 ` Glenn Morris
2019-11-08  5:00   ` Stefan Kangas
2019-11-08  6:17     ` Michael Sloan
2019-11-08 13:29       ` Eli Zaretskii
2019-11-08 14:03         ` Stefan Kangas
2019-11-08 14:31           ` Eli Zaretskii
2019-11-08 13:24     ` Eli Zaretskii
2019-11-08 14:10       ` Stefan Kangas
2019-11-08 19:19         ` Eli Zaretskii
2019-11-09  6:17         ` Michael Sloan
2019-11-09  7:45           ` Eli Zaretskii
2019-11-09  9:12             ` Stefan Kangas [this message]
2019-11-09  9:24               ` Eli Zaretskii
2019-11-09 23:37                 ` Michael Sloan
2019-11-14  9:17                   ` Eli Zaretskii
2019-11-16 23:23                     ` Michael Sloan
2021-09-25  0:06                 ` Stefan Kangas
2021-09-25  1:49                   ` Lars Ingebrigtsen
2021-09-25  2:10                     ` Stefan Kangas
2021-09-25  2:27                       ` Lars Ingebrigtsen
2021-09-25  2:59                         ` Stefan Kangas
2021-09-25  3:05                           ` Lars Ingebrigtsen
2021-09-25  3:45                             ` Stefan Kangas
2021-09-26  5:28                               ` Lars Ingebrigtsen
2021-09-26  6:31                                 ` Stefan Kangas
2021-09-26  6:34                                   ` Lars Ingebrigtsen
2021-09-26  7:17                                     ` Stefan Kangas
2021-09-26  8:24                                       ` Eli Zaretskii
2021-09-26  8:37                                         ` Andreas Schwab
2022-04-18 11:30                                 ` Lars Ingebrigtsen

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='CADwFkmmRgDqA-f2Ls=jxFVPyD_nzy82Z3WMORhdLQTELrBAUvA@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=23033@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mgsloan@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).