Re: OSX FSEvents file watching support

[Michael Albinus]

Eli Zaretskii <address@hidden> writes:

>> Tramp doesn't. Injection the event would trigger the call of the
>> respective handler from special-event-map. Instead, Tramp calls this
>> handler directly.
>
> That only works if (a) Tramp knows in advance what handler to call,
> and (b) that handler is callable from Lisp.
>
> I don't think it's reasonable to base a native notification back-end
> on these assumptions, they are too shaky, and it's unnecessary in the
> first place.

We can change it, of course. But see also the comment in both filter
functions directly before the call of the handler: I tried it the other
way, and there were problems.

And yes, both (a) and (b) are fulfilled. Likely (a) is fulfilled
because it is the same guy who has written Tramp and the filenotify
event handler. (b) is fulfilled, because it is a Lisp function, which is
given by special-event-map as handler for file notification events.

I don't recommend to apply this technique for other events. But for file
notifications, it works for years.

Best regards, Michael.