Open fbroeren opened 6 years ago
Do you see this after a fresh reboot? ENOSPC
refers to there being too many watched files, so possibly the file tracking is is not being correctly cleaned up. Would you mind disabling other packages and see if you still get the error? (in case it is some interaction between autocomplete bibtex and other packages)?
I just disabled all packages apart from markdown-preview-plus and autocomplete-bibtex but the error is still there. I restarted atom and checked that all processes called atom were closed.
Ok I will have a look when I can, it might take a while before I can get round to it i'm afraid :( Most likely due to too many file watches (it can also be if you are low on disk space, but i assume you are not). No idea why though, might be a linux-specific bug.
There may be a workaround by changing the max watches for nodejs, something like $ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
(although whether this will work for Atom's embedded node i do not know).
Thank you, the workaround did the job! I now enabled all packages again and bibtex autocompletion works as before.
I'm getting this error as soon as I open Atom. The file does exist and the error persists when I change the path to start with a tilde.
Atom: 1.24.0 x64 Electron: 1.6.16 OS: Ubuntu 17.10 Thrown From: autocomplete-bibtex package 1.2.0
Stack Trace
Failed to activate the autocomplete-bibtex package
Commands
Non-Core Packages