Syntax highlighting and outline support for empirical fun definitions#196
Open
joeldrapper wants to merge 1 commit intozed-extensions:mainfrom
Open
Syntax highlighting and outline support for empirical fun definitions#196joeldrapper wants to merge 1 commit intozed-extensions:mainfrom
fun definitions#196joeldrapper wants to merge 1 commit intozed-extensions:mainfrom
Conversation
joeldrapper
force-pushed
the
push-rpuwplpkxxop
branch
from
df0d227 to
c21b0a2
Compare
joeldrapper
force-pushed
the
push-rpuwplpkxxop
branch
from
c21b0a2 to
e6b71bb
Compare
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
1 participant
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.
I realise this is a very unusual use of Ruby so completely understand if you’d rather not merge it here. I’ve written TreeSitter queries to support
fundefinitions from Empirical with syntax highlighting and outline support.https://github.com/yippee-fun/empirical
These queries are so specific, it’s extremely unlikely that they would be triggered for anyone who isn’t using Empirical. You would need to have a call pattern like this in your code.