From: Eli Zaretskii <eliz@gnu.org>
To: Olli Helenius <liff@iki.fi>
Cc: 35171@debbugs.gnu.org
Subject: bug#35171: 26.1; file-locked-p does not respect file-name-coding-system
Date: Sat, 06 Apr 2019 17:55:24 +0300 [thread overview]
Message-ID: <83h8bb9o9v.fsf@gnu.org> (raw)
In-Reply-To: <510095545.132397.1554545837223@office.mailbox.org> (message from Olli Helenius on Sat, 6 Apr 2019 13:17:17 +0300 (EEST))
> Date: Sat, 6 Apr 2019 13:17:17 +0300 (EEST)
> From: Olli Helenius <liff@iki.fi>
>
> The ‘file-locked-p’ function does not call ‘ENCODE_FILE’ on its argument
> and thus can end up looking for a different file name than that which
> was generated by ‘lock-buffer’. Below is an Elisp expression that
> demonstrates the issue.
Thanks, fixed on the master branch.
prev parent reply other threads:[~2019-04-06 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 10:17 bug#35171: 26.1; file-locked-p does not respect file-name-coding-system Olli Helenius
2019-04-06 14:55 ` 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=83h8bb9o9v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35171@debbugs.gnu.org \
--cc=liff@iki.fi \
/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).