Repository metrics
- Stars
- (2,224 stars)
- PR merge metrics
- (PR metrics pending)
Description
Hello! Love the concept of vivid - big value add in a compact tool.
I was planning to open a PR adding entries in the filetype database for common iOS files, e.g. .pbxproj Xcode project files (and others). While exploring that, however, I realized that .m, the extension for Objective-C implementation files, was already used in the default filetype database for Matlab files.
How will vivid handle the same file extension being associated with multiple filetypes, e.g. if I added an entry for Objective-C files ending in .m? What behavior would we want to see for that kind of conflict?
One workaround would be for me to maintain my own custom filetype database with Matlab removed in favor of ObjC, but since this is a scenario that I can imagine coming up in other scenarios as well I'm curious if this is something you'd like to handle in a specific way. Happy to contribute the changes if there's action to be taken, if that helps.
Thanks in advance!