Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes from editor do not trigger watchman #43

Closed
AntonioCS opened this issue Jul 4, 2014 · 1 comment
Closed

Changes from editor do not trigger watchman #43

AntonioCS opened this issue Jul 4, 2014 · 1 comment

Comments

@AntonioCS
Copy link

I have a vm running centos. I have compiled and installed watchman.
I have this trigger:

{
"version": "2.9.9",
"triggers": [
{
"name": "compilets",
"append_files": true,
"command": [
"make"
],
"stdin": [
"name",
"exists",
"new",
"size",
"mode"
],
"expression": [
"anyof",
[
"match",
"*.ts",
"wholename"
]
]
}
]
}

If I am in the terminal and use vim to change the files this gets triggered, but if I am using notepad++ (from my windows 7 machine) this does not trigger.

Is this the expected behaviour? I thought watchman would watch for changes in the folder independently of where does changes were coming from.

This folder is a shared folder from windows to linux (virtualbox does all the mouting stuff).
I was hoping that watchman would still work :)

@sunshowers
Copy link
Contributor

No, that won't work. From the documentation at https://facebook.github.io/watchman/docs/install.html:

Watchman relies on the operating system facilities for file notification, which means that you will likely have very poor results using it on any kind of remote or distributed filesystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants