Bump file picker limit

[hovsater]

As a quick fix before we decide what to do next in #52, I've bumped the limit.

[pickfire]

What if we just remove the limit?

[archseer]

It would be really bad if you triggered space+f in / then, since it would load your entire filesystem metadata into memory. I think having an upper bound, even if very large one is good. This bound is also applied after processing .gitignored files (build/, target/, etc. etc.) so hopefully there shouldn't be millions of files.

[pickfire]

It would be really bad if you triggered space+f in / then, since it would load your entire filesystem metadata into memory. I think having an upper bound, even if very large one is good. This bound is also applied after processing .gitignored files (build/, target/, etc. etc.) so hopefully there shouldn't be millions of files.

Okay, what about this. We only apply a the upper bound if .git isn't found. Even though the project have like millions of file it's still under the project and excluding those git-ignored. At least in this case it's the project file. Maybe we should try running it (both debug and release) without upper bound in linux and rust repository and see if it's good.

[hovsater]

@pickfire I find that a compelling alternative. Especially since I believe the ignore crate reads .ignore files in addition to the .gitignore.

[pickfire]

I never heard about .ignore but I think .gitignore should be good enough but we should also have a way to show those ignored files.

[hovsater]

@pickfire .ignore files have the same semantics as gitignore files and are supported by search tools such as ripgrep and The Silver Searcher. Allowing searching ignored files would be possible using the WalkBuilder.