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

[Question] Behaviour Regarding Multiple Suffixes #84

Open
kevinmatthes opened this issue Aug 3, 2022 · 1 comment
Open

[Question] Behaviour Regarding Multiple Suffixes #84

kevinmatthes opened this issue Aug 3, 2022 · 1 comment

Comments

@kevinmatthes
Copy link
Contributor

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).

kevinmatthes added a commit to kevinmatthes/zee that referenced this issue Aug 3, 2022
…#6)

* [Enhancement] Add Support for Common 2nd Suffixes

* Remove obsolete suffixes from Python entry
@kevinmatthes
Copy link
Contributor Author

#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.

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

No branches or pull requests

1 participant