ENOENT, no such file or directory about watch HOT 9 CLOSED

Turns out the files that watch is tripping over aren't related to emacs' auto save/backup; rather watch is tripping on the symlinks created automatically by emacs for "interlocking".

They show up when you open and start editing a file, and disappear once you save the buffer to disk. They look like this:

$ ls -lad .*
lrwxr-xr-x   1 michael  staff    28 Dec 18 21:05 .#index.js -> [email protected]

I'm hunting for an option to disable the "interlocking" stuff. But I'm wondering if watch could / should support an option such that encountering these kinds of files won't cause it to throw an exception.

from watch.

Related: http://stackoverflow.com/questions/5738170/why-does-emacs-create-temporary-symbolic-links-for-modified-files

from watch.

if you do a straight up require('fs').watchFile() on the symlink does it still blow up?

from watch.

@maxogden no, it does not.

from watch.

To be more specific, sorry I was not earlier, the error is thrown in the context of my using watch.createMonitor... in a directory where emacs has created one of these interlocking-symlink files.

from watch.

Attempted a fix in the walk function in main.js:

https://github.com/michaelsbradleyjr/watch/blob/check-ENOENT/main.js#L21

Seems to be working.

from watch.

can i get a pull request?

from watch.

Pull request sent: #26

from watch.

merged fix, looks good.

from watch.