From: Eli Zaretskii <eliz@gnu.org>
To: jsynacek@redhat.com (Jan Synáček)
Cc: 24656@debbugs.gnu.org
Subject: bug#24656: 25.1; Emacs leaves lock files on a CIFS share
Date: Mon, 10 Oct 2016 15:14:32 +0300 [thread overview]
Message-ID: <83bmyse6zb.fsf@gnu.org> (raw)
In-Reply-To: <m6f37k4l9v3.fsf@jsynacek-ntb.brq.redhat.com>
> From: jsynacek@redhat.com (Jan Synáček)
> Date: Mon, 10 Oct 2016 13:30:24 +0200
>
> # ls -la /mnt/tmp/
> total 9
> drwxrwxrwx+ 2 root root 0 Oct 10 13:21 .
> drwxr-xr-x. 1 root root 20 Jul 15 10:33 ..
> lrwxrwxrwx. 1 nfsnobody nfsnobody 54 Oct 10 13:21 .#test.txt -> jsynacek@jsynacek-ntb.brq.redhat.com.57671476081527
> -rw-rw-rw-+ 1 jsynacek users 10 Oct 10 13:16 test.txt
>
> When I save the file and quit emacs, the lock file stays there. It
> should be removed. Maybe it's because of the weird 0xF022 sequence in
> the file name?
That 0xF022 should have been a colon ':'.
Can you step with a debugger through lock_file_1 and see how this file
name happens to come up? Is it possible that Samba doesn't allow the
colon characters in its file names, and the network re-director
replaces the colon with that strange character? If so, would using a
different character, like comma, fix the problem?
Thanks.
next prev parent reply other threads:[~2016-10-10 12:14 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 [this message]
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
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=83bmyse6zb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24656@debbugs.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.