-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Textmate on Lion: PeepOpen does not find some files #4
Comments
I believe I'm seeing the same thing. Fresh Lion install, fresh TextMate, fresh PeepCode. Searching for 'pdf_test' in a project which most definitely matches 'pdf_test' doesn't find any test files. In fact the entire test directory seems to be missing from search results and I'm not sure why. |
Do you have "documents to track" set to all? That bit me the first time. |
Yeah I forgot to update this after figuring it out. I felt kinda dumb when I did. I had a project with 3,000 files or so and PeepOpen defaults to only showing 1,000. Perhaps the default settings should be changed to show all (correct by default) and leave it up to the user to restrict to fewer files if necessary. |
That would make sense to me. A ended up not using PeepOpen for quite some time because it wasn't finding everything TextMate was finding. Then I found the silly "documents to track" setting. To be honest, I don't think that setting should exist at all. It doesn't make sense to restrict the files in such an arbitrary way. It may make sense to have a fixed cap if PeepOpen would totally choke on 10,000+ files. Beyond that, the various filters are a useful way to restrict how much is being indexed. |
I'm using PeepOpen 0.3.5 on OS X Lion, and I'm having some strange issues with it. It simple does not find some files that are obviously there. I've made a little screen recording to illustrate what I'm talking about: http://www.screenr.com/7mds . And although it's not shown in the video I also tried to refresh using Cmd-R. Anyone else experiencing something similar? Any suggestions?
The text was updated successfully, but these errors were encountered: