From: Michael Albinus <michael.albinus@gmx.de>
To: zhang cc <ccsmile2008@outlook.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: auto-revert error on macOS when auto-revert-use-notify is t
Date: Sat, 20 Jan 2018 16:34:06 +0100 [thread overview]
Message-ID: <874lngfssx.fsf@gmx.de> (raw)
In-Reply-To: <SG2PR0601MB140513EDCA36C2C764FF0A8AA81C0@SG2PR0601MB1405.apcprd06.prod.outlook.com> (zhang cc's message of "Fri, 5 Jan 2018 14:47:33 +0000")
zhang cc <ccsmile2008@outlook.com> writes:
Hi,
> I will put it in my TODO. If time permits, I'll work on this, if
> nobody beats me.
>
> Thank you for your attention and your work.
> My English is poor. I’m afraid I can’t discribe it clearly. Maybe
> someone else can do it?
I've pushed a patch to the master branch. It recreates a file
notification in autorevert, if a file was deleted and recreated
afterwards.
Since autorevert watches directories, the solution was simpler than
expected. The `create' event for the file from the directory is a
perfect trigger.
Could you, pls, check whether it works for you? I have extended the
`auto-revert-test02-auto-revert-deleted-file', which runs OK in my
environment. Testing on macOS (kqueue) is not possible for me.
Best regards, Michael.
next prev parent reply other threads:[~2018-01-20 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 5:08 auto-revert error on macOS when auto-revert-use-notify is t zhang cc
2017-12-29 10:02 ` Michael Albinus
2017-12-29 10:13 ` Eli Zaretskii
2017-12-29 15:45 ` zhang cc
2018-01-02 13:23 ` Michael Albinus
2018-01-05 14:47 ` zhang cc
2018-01-20 15:34 ` Michael Albinus [this message]
2018-01-21 11:01 ` zhang cc
2018-01-21 20:16 ` Alan Third
2018-01-22 8:17 ` Michael Albinus
2018-01-22 23:05 ` Alan Third
2018-03-11 4:26 ` zhang cc
[not found] ` <18101cae-50ff-44a2-af65-f77b9039f461@Spark>
2018-03-11 4:29 ` zhang cc
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=874lngfssx.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ccsmile2008@outlook.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).