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

Add a way to extend file-types key in languages.toml #6896

Closed
benjamineskola opened this issue Apr 27, 2023 · 1 comment
Closed

Add a way to extend file-types key in languages.toml #6896

benjamineskola opened this issue Apr 27, 2023 · 1 comment
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements

Comments

@benjamineskola
Copy link

Currently if I want to add a new filetype pattern for a language it seems that I have to duplicate the entire existing file-type setting from the base languages.toml into ~/.config/helix/languages.toml and then add my own in addition to that. That seems less than ideal: some filetypes have a relatively long list to begin with which clutters the user config, and if the base setting is changed in a future version the user config needs to be updated each time. I'd like instead to be able to specify new extensions while retaining the ones set in the base config.

Merging the two lists would be one way. However there's obviously a downside in simply appending to the list, as a user might also want to set the list in order to override the base setting (i.e., remove something that exists in the base config's list). I'm not sure how common that latter situation might be.

Otherwise perhaps an additional-file-types key that would be merged into the file-types?

@pascalkuthe
Copy link
Member

closing in favor of #10389

@pascalkuthe pascalkuthe closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements
Projects
None yet
Development

No branches or pull requests

3 participants