From: Michael Albinus <michael.albinus@gmx.de>
To: HaiJun Zhang <netjune@outlook.com>
Cc: 38287@debbugs.gnu.org
Subject: bug#38287: 26.3.50; filenotify.el: the Chinese file name in the event is messy code
Date: Wed, 20 Nov 2019 17:32:24 +0100 [thread overview]
Message-ID: <87y2wa7bl3.fsf@gmx.de> (raw)
In-Reply-To: <SG2PR03MB36112850221322E33C05C93DB74F0@SG2PR03MB3611.apcprd03.prod.outlook.com> (HaiJun Zhang's message of "Wed, 20 Nov 2019 03:50:26 +0000")
HaiJun Zhang <netjune@outlook.com> writes:
Hi,
> So file name comparing in the event callback of filenotify.el always
> fails. And there is no autorevert for this file.
Well, it is hard to analyse based on a .png file. Could you please
uncomment the line 93 in filenotify.el (it is a message call), and rerun
the test? There shall be debug output in the *Messages* buffer then.
> In GNU Emacs 26.3.50 (build 1, x86_64-apple-darwin17.7.0, NS
> appkit-1561.61 Version 10.13.6 (Build 17G8037))
> of 2019-10-30 built on jundeMac
> Repository revision: 3ee8ee8476fef2a5e8159f7597e36e0953295ce2
It's a Mac. That means, kqueue is the file-notify backend.
Does the underlying file system supports utf8? Is it enabled? Maybe
there's something to convert, when getting a kevent from the system?
> Important settings:
> value of $LANG: zh_CN.UTF-8
> locale-coding-system: utf-8-unix
That looks OK, although I'm not sure whether the coding system shall be
utf-8-hfs or something like this.
Unfortunately, I'm not able to debug on Mac :-(
Best regards, Michael.
next prev parent reply other threads:[~2019-11-20 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aeef7181-2c14-4b93-90fd-dd71993ed3c8@Spark>
2019-11-20 3:50 ` bug#38287: 26.3.50; filenotify.el: the Chinese file name in the event is messy code HaiJun Zhang
2019-11-20 16:32 ` Michael Albinus [this message]
2019-11-20 17:35 ` Eli Zaretskii
2019-11-20 17:49 ` Michael Albinus
2019-11-20 18:25 ` Eli Zaretskii
2019-11-20 18:45 ` Michael Albinus
2019-11-21 0:35 ` HaiJun Zhang
2019-11-21 2:33 ` HaiJun Zhang
2019-11-21 14:42 ` 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=87y2wa7bl3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=38287@debbugs.gnu.org \
--cc=netjune@outlook.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).