unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Carlos Pita <carlosjosepita2@gmail.com>
Cc: 51146@debbugs.gnu.org
Subject: bug#51146: 29.0.50; file-notify-add-watch not reporting changes of files
Date: Wed, 13 Oct 2021 09:45:23 +0200	[thread overview]
Message-ID: <87k0ihxt9o.fsf@gmx.de> (raw)
In-Reply-To: <CAEOO5TfioushgQwkiK7sN79HcyBLzkkY8WLpdDWJq2fxnYMRVw@mail.gmail.com> (Carlos Pita's message of "Tue, 12 Oct 2021 11:52:20 -0300")

Carlos Pita <carlosjosepita2@gmail.com> writes:

> That was about kqueue, but in macOS there is the FSEvents monitor:
>
>    The FSEvents monitor, available only on Apple macOS, has no known
>    limitations and scales very well with the number of files being
>    observed. In fact, I observed no performance degradation when testing
>    fswatch observing changes on a filesystem of 500 GB over long periods
>    of time. This is the default monitor on Apple macOS.
>
> So this seems to be an option, either directly or through fswatch.

Of course. I wrote the Emacs kqueue support on top of FreeBSD. Likely, I
won't write something macOS specific, since I have no respective
machine, and I'm not interested in. Somebody else must do the job, if
required.

(And I will analyze your bug report in detail next days, as time permits).

Best regards, Michael.





  reply	other threads:[~2021-10-13  7:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  4:16 bug#51146: 29.0.50; file-notify-add-watch not reporting changes of files Carlos Pita
2021-10-12  4:30 ` Carlos Pita
2021-10-12  4:52   ` Carlos Pita
2021-10-12 13:54     ` Eli Zaretskii
2021-10-12 14:41       ` Carlos Pita
2021-10-12 14:52         ` Carlos Pita
2021-10-13  7:45           ` Michael Albinus [this message]
2021-10-15 12:06 ` Michael Albinus
2021-10-15 18:43   ` Carlos Pita
2021-10-16  6:53     ` Michael Albinus

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=87k0ihxt9o.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=51146@debbugs.gnu.org \
    --cc=carlosjosepita2@gmail.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).