Colliding file type extensions

I'm developing a plugin for a language which uses "txt" as it's file extension. This is obviously a problem because by default the Text Files file type has the "*.txt" pattern registered and I wouldn't want to steal that file type registration completely.

What are the best practises for working with colliding file extensions? Can the user somehow trigger a decision along the lines of "this directory contains language x and therefore associate txt with file type X"?

1 comment
Comment actions Permalink

There is no UI for the user to configure that, but you can use the LanguageSubstitutor API to replace the language with your own for specific .txt files (and provide your own configuration UI if necessary).

0

Please sign in to leave a comment.