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

Custom CLI binary path setting #1

Open
Moshyfawn opened this issue May 31, 2024 · 1 comment
Open

Custom CLI binary path setting #1

Moshyfawn opened this issue May 31, 2024 · 1 comment

Comments

@Moshyfawn
Copy link

I have a setup where my tooling is sandboxed in a way that may require providing a custom path to some of the binaries. In the case of vale, when I start the LSP I get this server log:

initialized!
configuration changed!
Vale CLI not installed!

I tried to specify the path to the CLI binary in both the binary and settings lsp Zed settings fields, but to no avail.

"lsp": {
  "vale": {
    "binary": {
      "path": "/<absolute-path-to-vale-dir>/bin/vale"
    },
    "settings": {
      "valeCLI": {
        "path": "/<absolute-path-to-vale-dir>/bin/vale"
      }
    }
  }
}

Do you think the extension would need to handle this in addition to the current setup?

@koozz
Copy link
Owner

koozz commented Jun 3, 2024

Hi @Moshyfawn, that is a good question.

Do you know any other extensions that support this feature?
I would like to see what the best practices are around configuring this.

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

2 participants