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
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
After using the Atom editor for a while, it will refuse to open files and pop open the debugging console with an error: Uncaught TypeError: Unable to watch path
The editor usually works fine, but then will stop opening files once this starts.
I noticed a similar issue on Linux, but this is happening on Windows.
If the file watching fails, I'd expect a subtle warning (or no warning at all) and for the file I tried to open to open - not for it to refuse to open the file.
Potentially relevant information - this is on Windows 8.1 update 1, and the directory that is open is on a network drive. Also, it generally works (often for days) - but then stops working, so it must be able to watch these files sometimes.
The text was updated successfully, but these errors were encountered:
Just ran into the same issue with Atom 0.141.0 / Windows 7 Home Premium x64. I don't know if it matters, but in this case I'm also trying to open a file from a network drive (samba share).
After using the Atom editor for a while, it will refuse to open files and pop open the debugging console with an error: Uncaught TypeError: Unable to watch path
The editor usually works fine, but then will stop opening files once this starts.
I noticed a similar issue on Linux, but this is happening on Windows.
If the file watching fails, I'd expect a subtle warning (or no warning at all) and for the file I tried to open to open - not for it to refuse to open the file.
Potentially relevant information - this is on Windows 8.1 update 1, and the directory that is open is on a network drive. Also, it generally works (often for days) - but then stops working, so it must be able to watch these files sometimes.
The text was updated successfully, but these errors were encountered: