hlargs.nvim
tree-sitter
hlargs.nvim | tree-sitter | |
---|---|---|
12 | 62 | |
438 | 16,690 | |
- | 3.1% | |
6.0 | 9.8 | |
4 days ago | 1 day ago | |
Lua | Rust | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hlargs.nvim
-
This is why your higlights look different in 9.0
Am I correct to assume that hlargs.nvim is basically obsolete with semantic highlights?
-
Support for semantic token modifiers merged!
Does this effectively remove the need for something like hlargs?
-
Need help with C/C++ setup for proper highlighting and LSP features
Do I need 'hlargs.nvim' plugin?
-
Detailed syntax highlighting
There is also the hlargs plugin, which achieves the exact same highlighting as the screenshot you posted using treesitter instead of the lsp. However, it appears csharp support has only recently been requested. You can follow it here. https://github.com/m-demare/hlargs.nvim/issues/56
-
Is there plugin like hlargs.nvim desirable tree-sitter based but for methods arguments which called? Python for example.
I added the option, it requires some configuration you can find in :h hlargs-extras
-
How do I get good/ complete syntax highlighting in nvim? The tree-sitter one seems suboptimal compared to the VScode's complete and fleshed highlighting. Let me know of any plugins or extensions which can improve the situation for me.
hlargs does this. https://github.com/m-demare/hlargs.nvim
-
I must be missing something
m-demare/hlargs.nvim: Highlight arguments of function/method, because some language servers don't support semantic tokens.
-
hlargs.nvim update
If you haven't seen the previous post, hlargs.nvim allows you to highlight functions' arguments (definitions and usages)
-
hlargs.nvim: Highlight function arguments
Something like these, with lambda functions, nested functions, etc
-
Need help diagnosing slowness in Treesitter related plugin
Here's the WIP, to try it out you just install it and run require('hlargs').setup() Thanks!
tree-sitter
-
Lezer: A Parsing System for CodeMirror, Inspired by Tree-Sitter
I learned from a google search that these days upstream tree-sitter provides WebAssembly bindings.
Source: https://github.com/tree-sitter/tree-sitter/tree/master/lib/b...
NPM: https://www.npmjs.com/package/web-tree-sitter
Download from the latest Github release: js file (https://github.com/tree-sitter/tree-sitter/releases/download...) and wasm file (https://github.com/tree-sitter/tree-sitter/releases/download...)
-
Difftastic, a structural diff tool that understands syntax
Tree-sitter optimizes for performance (to use in editors), not for correctness. In fact even TS' core developers advocate for not bothering too much with correctness of grammars[1]. I imagine this constraint would be a deal-breaker for GitHub or anyone else in their position.
[1] https://github.com/tree-sitter/tree-sitter/issues/130#issuec...
-
Effective Neovim Setup. A Beginner’s Guide
This is a plugin that provides a simple way to use the tree-sitter in Neovim and also provides functionalities like highlighting, etc.
- An incremental parsing system for programming tools
-
Topiary: A code formatting engine leveraging Tree-sitter
From the tree-sitter side, I am tracking https://github.com/tree-sitter/tree-sitter/issues/1942
-
Shiki Syntax Highlighter
Is tree-sitter really slower than TextMate grammars? Some benchmarks indicate that this isn't really the case [1]. On the other hand, breaking parse trees is a real issue, because the error-recovery in tree-sitter is pretty rudimentary [2][3], but as you said, it's not an issue for Shiki.
Several TextMate grammars suffer from inaccuracy bugs, and issues of maintainability. Perhaps the biggest hindrance in the adoption of tree-sitter, is that the most popular editor, VSCode, still doesn't support it.
[1]: https://github.com/microsoft/vscode/pull/161479
[2]: https://github.com/tree-sitter/tree-sitter/issues/1870
[3]: https://github.com/tree-sitter/tree-sitter/issues/224
-
It seems that some BIG improvements of Treesitter on BIG FILEs have been merged into Nightly! (minutes ago!)
u/lewis6991 I think the biggest performance gain was made by tree-sitter itself: https://github.com/tree-sitter/tree-sitter/pull/2085
-
Looking for Tree-sitter query documentations and guides
I asked on the repo's discussions but responses are limited and not explanatory (I'm not shaming anyone here, discussions aren't a place for detailed how-tos and documentations anyway).
-
Will Treesitter ever be stable on big files?
The following discussion here. TS query cannot be incremental, that is why I regard it as design fault.
-
Detailed syntax highlighting
Hi, so I've recently decided to give Neovim yet another try, this time using some predefined plugins with kickstart.nvim, for syntax it uses tree-sitter.
What are some alternatives?
markid - A Neovim extension to highlight same-name identifiers with the same color.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
emmylua-nvim - Neovim emmylua library
Visual Studio Code - Visual Studio Code
vim-lsp-cxx-highlight - Vim plugin for C/C++/ObjC semantic highlighting using cquery, ccls, or clangd
indent-blankline.nvim - Indent guides for Neovim
nvim
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
gitsigns.nvim - Git integration for buffers
language-server-protocol - Defines a common protocol for language servers.
nvim-config
coc-explorer - 📁 Explorer for coc.nvim