From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedz@easesoftware.com, 57536@debbugs.gnu.org
Subject: bug#57536: 28.1; filenotify problems on macOS with symbolic links to directories
Date: Fri, 16 Sep 2022 18:39:10 +0200 [thread overview]
Message-ID: <87wna3xoi9.fsf@gmx.de> (raw)
In-Reply-To: <83pmfv2tzi.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 Sep 2022 18:56:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> I've pushed the changes for inotify and the remote inotifywait. There's
>> also a new testcase file-notify-test11-symlinks. Do you mind to check it
>> on w32?
>
> I don't think I can: I have XP here, where symlinks aren't supported.
>
> Would someone else please see if the new test works on MS-Windows?
Hmm. Somewhere, I have a Windows 10 VM lying around. Perhaps I can
convince it to support symlinks in Emacs, and test then.
Disclaimer: I don't know what I'm doing.
Best regards, Michael.
next prev parent reply other threads:[~2022-09-16 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 23:34 bug#57536: 28.1; filenotify problems on macOS with symbolic links to directories Perry Smith
2022-09-02 6:25 ` Eli Zaretskii
2022-09-04 11:42 ` Michael Albinus
2022-09-04 13:10 ` Eli Zaretskii
2022-09-04 14:26 ` Michael Albinus
2022-09-04 14:49 ` Eli Zaretskii
2022-09-07 12:20 ` Eli Zaretskii
2022-09-07 15:57 ` Michael Albinus
2022-09-16 15:27 ` Michael Albinus
2022-09-16 15:56 ` Eli Zaretskii
2022-09-16 16:39 ` Michael Albinus [this message]
2022-09-17 9:02 ` Michael Albinus
2022-09-17 9:43 ` Eli Zaretskii
2022-09-17 13:16 ` Michael Albinus
2022-09-17 14:07 ` Eli Zaretskii
2022-09-17 15:03 ` Michael Albinus
2022-09-17 13:27 ` Michael Albinus
2022-09-17 13:53 ` Eli Zaretskii
2022-09-17 15:15 ` Michael Albinus
2022-09-17 15:37 ` 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=87wna3xoi9.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=57536@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pedz@easesoftware.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.