Replies: 1 comment
-
I'm realising now that the workspace config is probably being ignored because it's in the parent folder of my git repository; because I am making use of |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
I'm having a problem where Helix is only recognising
vscode-eslint-language-server
settings in~/.config/helix/languages.toml
, and it seems to be ignoring any additional config that I put in workspace directories. I know that Helix is supposed to merge configs up along the working directory path, but it's very hard to tell what actually gets merged and what gets overwritten (how are arrays merged for instance, are they merged at all?), and where I'm going wrong with my config.How do the rest of you get by debugging your configs? I'm surprised there aren't more facilities for debugging it, because I find it very frustrating.
hx --health <lang>
is quite brief, I can't learn anything about how each of the language servers are configured.hx -v
and looking through the logs is possible, but quite tedious and difficult to understand.Anyway, I think it would be quite useful (and simple to implement? (I would have a go myself if I had any familiarity with Helix's source code)) to have a command that takes the fully merged config that Helix is using and just prints it to stdout as JSON, or something like that. I just want to be able to see what is and isn't reaching the final configuration from my workspace config.
I'm thinking something like
docker compose config
: https://docs.docker.com/engine/reference/commandline/compose_config/Beta Was this translation helpful? Give feedback.
All reactions