Allow for custom binaries #26
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for starting this. I'll try to get a new release out next week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #25
@jdkato
I am still being asked for the ability to set custom binary locations with the LSP-based VSCode extension and I made a very vague stab at this… I know no rust, so this was a bunch of copy and pasting and AI coding, resulting in something that doesn't error, but also doesn't seem to work as if I specify
valeBinaryPathin the VSCode extension with a non-existent binary, it still works…I just wanted to see if we could push this forward and maybe you throw this code out, but it's hopefully the vaguest of starts.