From: HaiJun Zhang <netjune@outlook.com>
To: Michael Albinus <michael.albinus@gmx.de>, Eli Zaretskii <eliz@gnu.org>
Cc: "38287@debbugs.gnu.org" <38287@debbugs.gnu.org>
Subject: bug#38287: 26.3.50; filenotify.el: the Chinese file name in the event is messy code
Date: Thu, 21 Nov 2019 00:35:14 +0000 [thread overview]
Message-ID: <PS1PR03MB3606EE7EC5638D2489238F7BB74E0@PS1PR03MB3606.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <83imnez9q9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
在 2019年11月21日 +0800 AM2:24,Eli Zaretskii <eliz@gnu.org>,写道:
Btw, I don't think I understand the nature of the problem yet: where
were the unibyte strings shown in the report printed? Did some Emacs
code print them, and if so, where is that code?
It’s my fault. I didn’t describe the problem clearly. I have added some debug messages to notify.el.
Auto-revert doesn’t work for many files on my machine, so I want to find the cause and added the debug messages. Finally I find that it is because the messy code.
The scenario:
1. Low level file event comes, there is a file name in the event which has messy code int it.
2. In file notify.el, it receives the event, extracts the file name in the event and compares it with the one it has stored when adding the watch. The extracted on is messy code, and the stored one is good string. They are not equal. So the event is discarded.
3. Then no auto-revert for the file forever.
[-- Attachment #2: Type: text/html, Size: 1565 bytes --]
next prev parent reply other threads:[~2019-11-21 0:35 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PS1PR03MB3606EE7EC5638D2489238F7BB74E0@PS1PR03MB3606.apcprd03.prod.outlook.com \
--to=netjune@outlook.com \
--cc=38287@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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.