From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: jsynacek@redhat.com, 24656@debbugs.gnu.org
Subject: bug#24656: 25.1; Emacs leaves lock files on a CIFS share
Date: Tue, 11 Oct 2016 19:29:05 +0300 [thread overview]
Message-ID: <83d1j6df3i.fsf@gnu.org> (raw)
In-Reply-To: <51995fbe-7230-48c4-2744-ad248202a830@cs.ucla.edu> (message from Paul Eggert on Tue, 11 Oct 2016 08:59:41 -0700)
> Cc: 24656@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 11 Oct 2016 08:59:41 -0700
>
> On 10/10/2016 11:49 PM, Eli Zaretskii wrote:
> > Paul, do you see any reasons not to make this change? Could the comma
> > be problematic in some cases? If so, can we try some other character,
> > perhaps?
>
> If we're going to change it, I suggest choosing a character from the
> POSIX portable file name character set
> <http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_266#tag_03_276>,
> as this is the most likely to work across a wide variety of POSIXish
> file systems. So, how about using "." instead of ":"?
Fine with me, I thought we wanted a different character to minimize
the risk of errors in parsing the link name.
> More important, how will a new Emacs interoperate with an old one?
I guess we will have to check for both the colon and the new
character?
next prev parent reply other threads:[~2016-10-11 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 11:30 bug#24656: 25.1; Emacs leaves lock files on a CIFS share Jan Synáček
2016-10-10 12:14 ` Eli Zaretskii
2016-10-10 13:49 ` Jan Synacek
2016-10-10 15:49 ` Eli Zaretskii
2016-10-11 6:32 ` Jan Synacek
2016-10-11 6:49 ` Eli Zaretskii
2016-10-11 6:52 ` Jan Synacek
2016-10-11 15:59 ` Paul Eggert
2016-10-11 16:29 ` Eli Zaretskii [this message]
2016-10-11 16:53 ` Paul Eggert
2016-10-11 17:07 ` Eli Zaretskii
2016-10-11 20:15 ` Paul Eggert
2016-10-11 20:58 ` Eli Zaretskii
2016-10-11 22:46 ` Paul Eggert
2016-10-12 6:40 ` Eli Zaretskii
2016-10-12 16:21 ` Paul Eggert
2016-10-12 16:53 ` Eli Zaretskii
2016-10-11 17:43 ` Achim Gratz
2016-10-11 18:16 ` 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=83d1j6df3i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24656@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jsynacek@redhat.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).