freezing
when i open it in one project (not so big) it makes emacs freeze. i can not tell you much more because i don't get any error message or whatever..
I've got 9224 files in project, because of node_modules i use
$ find . -type f | wc -l
$ 9224
Can you try making a copy and removing files to figure out the culprit? There's probably something unusual going on that I haven't considered.
Enabling M-x toggle-debug-on-error and pressing C-g when it freezes might also reveal something.
I'll probably add node_modules to the default pe/omit-regex, since it's mentioned in many tickets.
If it's something inside node_modules, I might be able reproduce it with a list of installed modules.
i just noticed #4 issue. what are the functionalities that can't make it "lazy" ?
There's a bunch. It shouldn't freeze with ~1000 files.
For me as well, it renders Emacs unresponsive.
I've described above how you might help me debug this.
I couldn't get any useful information out of toggle-debug-on-error + C-g, but I confirm that removing node_modules from the project directory and recaching the tree fixes the problem.
What modules do you have installed? What is your OS?
@sabof sorry for the delay! In my node_modules there are 50 modules, bower, grunt, karma, coffee-script and the rest are various grunt and karma plugins.
I have to say on a more recent laptop the problem is less pronounced, but it still makes Emacs almost unusable. The OS is OS X.
But eventually it finishes indexing, and everything works as usual?
It is indexing OK, I understand it's expected to take some time. The problem is exactly after, when you do regular stuff in Emacs like opening fils or even moving cursor.
I've added node_modules to pe/omit-regex. I could limit the number of overlays used, but I'm not sure that the problem is prevalent enough.
Thanks! It does work fast now.
Super-old issue, but figured I figured I'd chime in--If the issue crops up again, M-x toggle-debug-on-quit + C-g should give more information than M-x toggle-debug-on-error since it doesn't need an error to show you the current stack trace.
Alternatively, pkill -USR2 emacs from a terminal will get you a stack trace from an unresponsive Emacs that won't even respond to C-g. (And even unfreeze it for you..!)
This also turns on debug-on-quit, so after you get a stack trace, you might want to run M-x toggle-debug-on-quit again, or else it might get a bit annoying.