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

Resolve syntax highlighting group in neovim/treesitter #160

Merged
merged 6 commits into from
Apr 13, 2024

Conversation

j-xella
Copy link
Contributor

@j-xella j-xella commented Apr 8, 2024

As the SUBJ says, it should now detect the highlighting group even when the syntax highlighting is managed by treesitter in neovim. This should partially address #159

Also, I moved the highlighting detection logic into a separate function, and added end-user interface for it - now it is possible to detect the highlighting group name (or the absence of such) for any position in a file. This possibility exists as vim function only - I deliberately decided against creating command binding for it. This is a debug functionality, I'd rather prefer it not to show up in command completion.

autoload/easy_align.vim Outdated Show resolved Hide resolved
autoload/easy_align.vim Outdated Show resolved Hide resolved
autoload/easy_align.vim Outdated Show resolved Hide resolved
autoload/easy_align.vim Outdated Show resolved Hide resolved
To prepare a place for the future complexity that can be reused.
autoload/easy_align.vim Outdated Show resolved Hide resolved
@j-xella
Copy link
Contributor Author

j-xella commented Apr 12, 2024

I hope everything is OK now :)

* Remove line-number only example that is not going to be very useful
* Use get() to simplify the code
* Use lowercase dictionary keys for consistency
@junegunn junegunn merged commit 9815a55 into junegunn:master Apr 13, 2024
@junegunn
Copy link
Owner

Thanks, merged it with a few small changes. I haven't actually tested the Neovim part as I'm not a Neovim user, I just hope it works :)

@robyurkowski
Copy link

I'm another neovim user and I can confirm that this fixes the issue upon updating. What a relief! Thanks @j-xella and @junegunn :)

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.

3 participants