System details

• Microsoft Windows 10 Pro 10.0.19041 Build 19041
• notify = "5.0.0-pre.3"
• Running Windows Subsystem for Linux (WSL)
• WSL: Linux DESKTOP-HHHHH 4.4.0-19041-Microsoft Update to Rust master #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

What you did (as detailed as you can)

let mut water : RecommendedWatcher = Watcher::new_immediate(move |res| tx.send(res).unwrap()).unwrap();

water.configure(Config::PreciseEvents(true)).unwrap();
water.watch(file_watch, RecursiveMode::Recursive).unwrap();

loop {
     match rx.recv() {
        Ok(event) => println!("{:?}", event),
        Err(e) => println!("watch error: {:?}", e),
    }
}

Running this code and setting file_watch to a specific text file and then editing it in vim and saving it only prints the first 3 events, but nothing after that.

What you expected

Editing it in vim and saving it only prints the first 3 events for the first save, but nothing after that. I expected that making additional edits and saving them would print more events, but this did not happen.

What happened

Only the first 3 events when editing with vim are printed.

Additional Notes

When setting file_watch to the text file's directory, the program actually prints that events where the paths attribute contains the specific file when writing multiple times with vim. I think there's an issue in the library with filtering out specific events.