hlargs.nvim
nvim-treesitter
hlargs.nvim | nvim-treesitter | |
---|---|---|
12 | 300 | |
442 | 9,631 | |
- | 4.2% | |
6.0 | 9.9 | |
4 days ago | 6 days ago | |
Lua | Scheme | |
GNU General Public License v3.0 only | Apache License 2.0 |
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!
nvim-treesitter
-
JetBrains' unremovable AI assistant meets irresistible outcry
I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.
These two plugins are the bare minimum in my view.
https://github.com/nvim-treesitter/nvim-treesitter
Treesitter gives you much better syntax highlighting based on a parser for a given language.
https://github.com/neovim/nvim-lspconfig
This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...
For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.
pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server
Best of luck! Happy hacking.
-
Help needed with Treesitter sql injection
It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
- Problem with highlighting when attempting to create own treesitter parser
-
neorg problem, all other plugins deactivate when added to init.lua
vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```
-
Getting Treesitter to work for Windows 10
Change the compiler to use 'llvm' and install visual studio build tools command line stuff - at least that is what worked for me without problems. If you are using c++ then I would assume you have visual studio installed already. If you need more info follow the treesitter windows support
-
Just come back up out of the rabbit hole - TS unsets syntax variable by design!
After a lot of time spent yesterday I took a fresh look today and then thought to myself - what if this is what TS does by design? A few clicks later and I found this https://github.com/nvim-treesitter/nvim-treesitter/issues/1327
- What is this color scheme
-
nvim-treesitter erroring on Windows 11 Pro
I've followed the official guide for nvim-treesitter support on Windows, but I'm having problems making it work. I keep getting a compilation error for any parser I try to install using TSInstall. If instead I use TSInstallSync I don't get errors but the parser is not correctly installed. My setup uses lazyvim and I installed LLVM using winget to have a C compiler.
-
Neovim can't find C compiler
I have read that gcc in windows doesn't always provide the necessary support for treesitter. I have seen ppl prefer clang over gcc in Windows. Please see also Windows support in treesitter's repo. Unfortunately I cannot help further as I don't use Windows for coding, but hope you can deduce something to solve your problem from the above link (if you haven't already read through it).
What are some alternatives?
markid - A Neovim extension to highlight same-name identifiers with the same color.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
emmylua-nvim - Neovim emmylua library
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-lsp-cxx-highlight - Vim plugin for C/C++/ObjC semantic highlighting using cquery, ccls, or clangd
vim-polyglot - A solid language pack for Vim.
nvim
vim-python-pep8-indent - A nicer Python indentation style for vim.
gitsigns.nvim - Git integration for buffers
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
nvim-config
tree-sitter - An incremental parsing system for programming tools