The Type field in the catalog custom folder's Source options tab seems broken (and is somehow easy to crash). For example if I add .lua to index only files ending in .lua, it doesn't work.
Besides for exclusion/and or inclusion I think it would be better if path patterns (or alternatively directory names) could be specified. Manual exclusion doesn't really scale in practice if you are dealing with huge file hierarchies.
Thanks.
The text was updated successfully, but these errors were encountered:
A user on the mailing list pointed out that excluding by extension (like .asd) doesn’t work. This appears to only be a problem for extensions that the system can’t map to a specific UTI.
The pattern thing isn’t addressed, but you can now include and exclude using UTIs, which is a hierarchical system allowing you to take care of entire categories at once. Including and excluding folders recursively will be addressed separately. (See #9)
The
Type
field in the catalog custom folder'sSource options
tab seems broken (and is somehow easy to crash). For example if I add.lua
to index only files ending in.lua
, it doesn't work.Besides for exclusion/and or inclusion I think it would be better if path patterns (or alternatively directory names) could be specified. Manual exclusion doesn't really scale in practice if you are dealing with huge file hierarchies.
Thanks.
The text was updated successfully, but these errors were encountered: