Simplify adding new debugger templates to an existing language #10236
Unanswered
HealsCodes
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As of helix 22.12 - if I understand the sources correctly - TOML configurations are merged in a way that after a certain depth values are replaced instead of combined (ref in helix-loader).
For debugger configurations this seems to always be the case, if present in a users
languages.toml
they will be merged as replacement for the built-in debugger configuration. While this feels like a good idea for most other settings scenarios in this case it causes a lot of extra work for the user.An example - Let's say I want to add an extra c or c++ debugger configuration that opens the application in an external terminal.
Ideally I'd have to write something like this and the rest would be merged in from defaults:
Sadly, this isn't even a valid configuration because
[language.debugger]
already replaces the built-in in table values completely.Writing it like this creates a valid configuration, but only leaves one available debugger configuration because the rest is discarded during merge as well:
So to add a single extra template the user has to grab the original
languages.toml
from github or their sources, copy paste the full debugger section into their custom configuration and add the new template:Is there really no easier way this could be done?
Beta Was this translation helpful? Give feedback.
All reactions