Ticket #6 (new enhancement)
Opened 4 months ago
a higher level process_IN_MOVED for matching moved_from/moved_to events?
| Reported by: | dato@… | Owned by: | |
|---|---|---|---|
| Priority: | minor | Keywords: | |
| Cc: |
Description
Hello,
having event.cookie for MOVED events is great, but I was thinking it'd be very nice if pyinotify offered some handling for events with matching cookies.
At the moment, if you want to do something useful with matching MOVED_FROM/MOVED_TO events, you have to implement your own logic, and if you don't want to lose MOVED events with source or dest outside your watched tree, you have to implement some timeout mechanism to declare events as "unmatched".
If pyinotify were to offer some process_IN_MOVED that would trigger on matching MOVED events, and then process_IN_MOVED_{FROM,TO} would only get called (if present) for unmatched events, that'd be great.
P.S.: Thanks for not requiring registration to file bugs against pyinotify.