lspsaga.nvim
nvim-treesitter
lspsaga.nvim | nvim-treesitter | |
---|---|---|
64 | 300 | |
2,697 | 9,537 | |
- | 3.3% | |
9.3 | 9.9 | |
about 1 year ago | 2 days ago | |
Lua | Scheme | |
MIT License | 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.
lspsaga.nvim
- [Neovim] Quels plugins dois-je utiliser avec le LSP intégré?
-
winbar below lualine buffers
Just like this? If yes, you can try lspsaga.nvim, nvim-navic, or barbecue.nvim.
-
Cannot find setting to get linter errors on type with Rust Analyzer
I am not 100% sure if that is what he is using but you can achieve the same thing using Lspsaga, specifically the on_insert and on_insert_follow options
-
Ideas to practice lua and neovim plugin development
Participating — I'd like to see more contributors for LSP Saga, the various ChatGPT plugins, and pets!
-
Any recommended plugins to frictionlessly see lsp references in a perhaps a popup window?
Maybe Lspsaga could help
-
Is it possible to see peek the documentation for a symbol within an LSP hover window?
I think the LspSaga plugin has a hover_doc function! it's been really useful for me :D
-
Has anyone encountered this buf error in lspsaga when working with svelte files?
Yo, good question.. Yes i have. It's actually working now i filed an issue on lspsaga and the owner created a quick fix for it: https://github.com/glepnir/lspsaga.nvim/issues/866
-
How do I get this little tree like hierarchy of the code on the top?
You might like this: https://github.com/glepnir/lspsaga.nvim.
-
[ HELP ] - LSPsaga hover window stuck
I already did, but you closed it 🫡 here is the link
-
My lspsaga's lsp_finder will cause weird behavior
Did you post an issue on GitHub? The library author has been exceptionally quick to respond to bugs and reports like this in my experience.
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?
nvim-lspconfig - Quickstart configs for Nvim LSP
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
navigator.lua - Code analysis & navigation plugin for Neovim. Navigate codes like a breeze🎐 Exploring LSP and 🌲Treesitter symbols a piece of 🍰 Take control like a boss 🦍
nvim-lightbulb - VSCode 💡 for neovim's built-in LSP.
vim-polyglot - A solid language pack for Vim.
vim-python-pep8-indent - A nicer Python indentation style for vim.
lsp_signature.nvim - LSP signature hint as you type
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
tree-sitter - An incremental parsing system for programming tools