From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
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 09:53:40 -0700 [thread overview]
Message-ID: <09fc9aec-1a11-6249-36a7-555b23a53cb0@cs.ucla.edu> (raw)
In-Reply-To: <83d1j6df3i.fsf@gnu.org>
On 10/11/2016 09:29 AM, Eli Zaretskii wrote:
> I thought we wanted a different character to minimize
> the risk of errors in parsing the link name.
Ah, OK, perhaps it's due to worries about interoperating with an older
Emacs scheme that used just "USER@DOMAIN" without the trailing
".PID:BOOT". If so, we should use some string that cannot be interpreted
as a valid domain name by an ancient Emacs. So, how about using '..'
instead of ':'? That is, "USER@DOMAIN.PID..BOOT". This should work since
a valid domain name cannot contain "..".
The complete set of allowed characters here, if '..' doesn't work for
some reason, is '(', ')', '<', '>', '[', ']', ':', ';', '@', '\', ',',
'.', '"', according to Internet RFC 5322 section 3.2.3. Of these
characters only '.' is allowed in a POSIX portable file name.
next prev parent reply other threads:[~2016-10-11 16:53 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
2016-10-11 16:53 ` Paul Eggert [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09fc9aec-1a11-6249-36a7-555b23a53cb0@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=24656@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.