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

feat: Add support for vim script #354

Closed
wants to merge 1 commit into from

Conversation

alcroito
Copy link
Contributor

@alcroito alcroito commented Jan 3, 2025

This adds support for vim script files.

It's using the 0.3.0 git tag instead of 0.5.4, because the latter depends on tree-sitter 0.21, which is not compatible with the 0.20 that is currently used.

Unfortunately, It's using the github url, instead of the published crate, because the 0.3.0 tag was never released on crates.io :(
This causes slightly long cloning times during the build.
I'm not sure what's the best way to go forward here, unless the tree-sitter version is bumped to one that is compatible with tree-sitter-vim 0.4.0, which is published on crates.io.

@@ -27,6 +27,7 @@ tree-sitter-lua = "0.0.19"
tree-sitter-bash = "0.20.0"
tree-sitter-java = "0.20.0"
tree-sitter-nix = "0.0.1"
tree-sitter-vim = { git = "https://github.com/tree-sitter-grammars/tree-sitter-vim.git", tag = "v0.3.0" }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't depend on git repositories. They are unfortunately not allowed by crates.io.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a shame.

Please check my comment in the PR description. None of the published crates are currently buildable with tree-sitter 0.20, which is the current requirement for harper.

Unless there is some other way, I guess this PR can be closed, and re-opened whenever the tree-sitter version is bumped.

harper-comments/src/comment_parser.rs Outdated Show resolved Hide resolved
@elijah-potter
Copy link
Collaborator

Looks pretty straightforward. Same stuff as #353 applies here.

@alcroito
Copy link
Contributor Author

alcroito commented Jan 7, 2025

I'll close the PR for now, because i'm not sure how to get rid of the git dependency.

@alcroito alcroito closed this Jan 7, 2025
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

Successfully merging this pull request may close these issues.

2 participants