I am using Sublime Text 2.0.2 on OS X (10.8.5). Most of the times, when I work on a project, I open the according folder so that it shows in the sidebar. Until now this has always been working perfectly.
Now I cloned a really big repository with lots and lots of folders and files, deeply nested within each other. To be exact: It's 20894 files within 4326 folders.
When I open the top-most folder of this repository, everything looks normal - but some folders appear as empty folders. Hence it looks like as if there were no files, although there definitely are some, even folders will not be shown.
It looks as if Sublime cuts everything below a certain folder and refuses to show it.
Does anybody know what causes this behavior and how to fix it?
Just waiting doesn't help: Although it may be that Sublime works in the background to read the tree, even after two hours of waiting nothing happened to the not-shown files and folders. So apparently there must be another problem.
And there is no exclusion pattern.
In Sublime's console it says:
scan: /some/folder has been seen before, skipping (using inode) previous path: /some/other/folder inode: 27425614.
The folder /some/folder is missing. It may be that this is correlated, but I'm not sure. Any ideas?