You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any directory (recursively) under /tmp is ignored from watching. I can understand watching the full /tmp is problematic, but it's reasonable to create a /tmp/some-test-project/ and use coc.nvim in it for testing. We should allow this case.
EDIT: vscode watches files successfully and can correctly emit change events for /tmp/some-dir/some-file.
But it never generates any notifications since the watched files are under /tmp.
Expected behavior
/tmp can be an invalid watching directory, but /tmp/some-dir should not.
If coc.nvim cannot fulfill the watching request (eg. invalid watching directory, or watchman is not installed), it should return an error response for easier debugging. It also allows the server to fallback to server-side watching mechanism.
The text was updated successfully, but these errors were encountered:
Result from CocInfo
Describe the bug
In the code:
coc.nvim/src/core/watchman.ts
Line 180 in 3014125
Any directory (recursively) under
/tmp
is ignored from watching. I can understand watching the full/tmp
is problematic, but it's reasonable to create a/tmp/some-test-project/
and use coc.nvim in it for testing. We should allow this case.EDIT:
vscode
watches files successfully and can correctly emit change events for/tmp/some-dir/some-file
.Reproduce the bug
Language server request:
Success response from coc.nvim:
But it never generates any notifications since the watched files are under
/tmp
.Expected behavior
/tmp
can be an invalid watching directory, but/tmp/some-dir
should not.watchman
is not installed), it should return an error response for easier debugging. It also allows the server to fallback to server-side watching mechanism.The text was updated successfully, but these errors were encountered: