Skip to content
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

Folders that that appear to have file extension are not filtered as folders. #1742

lgarron opened this issue Jan 5, 2014 · 3 comments


Copy link

@lgarron lgarron commented Jan 5, 2014

Create a folder test with the following folders in it:

  • normal
  • folder.js
  • folder.txt
  • folder.blabla

Then include contents and filter the type "folder" (in the "Types" field next to the depth slider). folder.js and folder.txt will not be indexed, but the other two will.

  • Excluding instead of including also gets it wrong (the opposite way).
  • Files are not detected as folders, even without an extension.

Presumably, a folder name ending with a "file extension" is heuristically treated as a file. This may make sense (certain packages like .app are basically folders, but are supposed to look like files to users), but there are valid reasons to have a "file extension" in a folder name.

In particular, such folder names are common with Javascript projects (think node.js). I personally came across this when I noticed that certain Javascript projects in my code folders were not being indexed.

Copy link
Contributor Author

@lgarron lgarron commented Jan 5, 2014

I note that mdls reports kMDItemContentType = "public.folder"

Copy link

@skurfer skurfer commented Jan 7, 2014

I think this comes down to a bug in QSUTIWithLSInfoRec(). Possibly fixed (or further obscured) by #1708.

Copy link

@pjrobertson pjrobertson commented Jan 15, 2014

I can confirm that #1708 does NOT fix this. Looking into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

3 participants