Respect config in scheme when treesitter is disabled - #781
Merged
Conversation
…r is disabled in config
Contributor
|
After a quick look, it seems to me that this should work fine. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Currently the scheme and guile clients will call tree-sitter facilities when validating a string to be evaluated by the repl even if
#extract#tree_sitter#enabledis false in the config. Furthermore the treesitter completions will also call some facilities if it is disabled (this has been harmless due to failure checks) but should also respect the config.Added a
ts.enabled?guard aroundget-completions-at-cursorwith testsAdded a
ts.enabled?check aroundvalid-str?which returns true of tree-sitter is disabled with tests