Some contexts require source files to have more than one suffix. These second suffixes typically originate from a build system and / or testing suites. For instance, the autotools suite often generates *.in and *.out files. Another example are the mutmut mutation tests for Python projects where the original state will be kept during the processing with *.bak backup copies of the respective source file.
At the moment, the default configuration has dedicated entries for autotools input files in the Python section (*.in). My question is if there is mechanism to automatically "ignore" the second suffix in order to apply the correct syntax highlighting. This would prevent four specifications of each file type (normal, backup, autotools input, and autotools output).
85 is a suggestion how this mechanism might be introduced. I am looking forward for feedback and wishes for further common second suffixes in case I should have forgot some.
kevinmatthes
commented
2 years ago
Some contexts require source files to have more than one suffix. These second suffixes typically originate from a build system and / or testing suites. For instance, the
autotoolssuite often generates*.inand*.outfiles. Another example are themutmutmutation tests for Python projects where the original state will be kept during the processing with*.bakbackup copies of the respective source file.At the moment, the default configuration has dedicated entries for
autotoolsinput files in the Python section (*.in). My question is if there is mechanism to automatically "ignore" the second suffix in order to apply the correct syntax highlighting. This would prevent four specifications of each file type (normal, backup,autotoolsinput, andautotoolsoutput).