Linux: folders created via `mkdir -p` not watched recursively about watcher HOT 2 OPEN

I'm the reporter on microsoft/vscode#142694. Just to be clear, this issue manifests itself as any change made to a deeply-nested file not being reflected in VSCode. The mkdir -p demo was just a simple case. I'm seeing this in real projects with deeply-nested structures, most of which were created from within VSCode itself. My last comment on microsoft/vscode#142694 has a demo of this happening.

from watcher.

similar issuer encountered with rust analyzer not being able to detect file changes. setting up watcher in rust analyzer instead seems to work maybe taking a look at what they are doing might help

rust-lang/rust-analyzer#15603 (comment)

Reproduce steps:

1. create an empty project, with a module file like tmp.rs
2. in root file(main.rs or lib.rs), write mod tmp;
3. open project with VSCode, no error
4. in terminal, create another module, like cp ./tmp.rs ./tmp2.rs
5. in root file, write mod tmp2;
6. You would find it reports an error unresolved module, can't find module file: tmp2.rs or...

Open the file tmp2.rs in VSCode would load the module.

And I found that

• RA does respect change/deletion from other tools
• once we opened tmp2.rs file once, then RA respects creation with steps 4-6 after we delete tmp2.rs

Maybe this is a bug of VSCode? Not sure...

from watcher.