You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1985: Command-T ignores directories that start with lowercase letters

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

I have two directories: foo with blah.cc inside, and Bar with blah2.cc inside. If I try to find "blah", the only thing I find is Bar/blah2.cc. No matter what I put inside a directory whose name starts with a lowercase character, it's not picked up.

I tried flushing. Note that it happens on MacOS X on a case-sensitive system mounted from a .dmg file.

Comments

  1. Greg Hurrell

    Command-T is itself case-agnostic; I think the most likely explanation of what you're seeing is that you're hitting the CommandTMaxFiles limit (default to 10,000) before getting to "foo/blah.cc.

    If you have a large number of files in the project, try upping CommandTMaxFiles to something bigger. (If that doesn't work, it may be that you have something pathological in your hierarchy, like a circular symlink.)

    Finally, one other possibility is that something in your 'wildignore' setting is causing that file or directory to be excluded from consideration.

  2. Greg Hurrell

    Closing due to inactivity.

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
  4. anonymous

    Thanks a lot, Wincent! It indeed worked for me; I had over 20000 files. It would be great, however, if the plugin issued some kind of warning when the number of files exceeds the maximum; otherwise, it's very confusing.

  5. Greg Hurrell

    Yep, ticket #1839 is the one for that.

Add a comment

Comments are now closed for this issue.

Menu