nvim-metals
nvim-treesitter
Our great sponsors
nvim-metals | nvim-treesitter | |
---|---|---|
12 | 300 | |
429 | 9,487 | |
3.0% | 5.4% | |
7.6 | 9.9 | |
3 days ago | 4 days ago | |
Lua | Scheme | |
Apache License 2.0 | 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.
nvim-metals
-
Seeking input from Metals users about build importing.
By multiple subprojects are they independent builds? Or just one big build with nested build files? I actually have a discussion related to this in here. Please to jump in there if that's the same issue you're having and comment on your situation. It'll be helpful to determine how to address it.
-
Neovim & Scala. Metals LSP not found when using :LspInstall
Use nvim-metals
-
elixir.nvim
elixir.nvim is a langauge plugin for Elixir. It is similar to nvim-metals in that is manages ElixirLS (Elixir's language server) and provides a complete experience over nvim-lspconfig.
-
Use Vim as a Scala IDE
Install https://github.com/scalameta/nvim-metals
-
debugpy.nvim: Command and API frontend to nvim-dap and Debugpy (debugging Python)
But I haven't yet set up anything properly other than Debugpy. nvim-dap is very barebones, so I feel that the best way is to have an extra configuration plugin on top. Debugpy.nvim is a very specific frontend plugin, but there are also more general plugins like nvim-metals and vim-ultest which also offer integration with nvim-dap.
-
What's your preferred setup/process (IDE, settings, etc) for working in Scala?
Yeah it's pretty good already and getting newer features everyday. I didn't want to hook up the vim I use everyday to a heavy editor so installed neovim alongside vim on my system and use this https://github.com/scalameta/nvim-metals (which I believe is the metals official way) and it's super straight forward to use.
-
How do you deal with poorly documented plugins?
Every software project is WIP to some extent, but that doesn't stop Neovim itself from having really high standards in documentation. A lot of Neovim plugins also have really high standards, such as nvim-metals.
-
sidebar.nvim - A generic and modular lua sidebar
nvim-metals (really thorough manual)
- Tree Sitter support
- Scala - what is best development setup?
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?
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-lua-guide - A guide to using Lua in Neovim
nvim-lspconfig - Quickstart configs for Nvim LSP
neovim - Vim-fork focused on extensibility and usability
vim-polyglot - A solid language pack for Vim.
tree-sitter-scala - Scala grammar for tree-sitter
vim-python-pep8-indent - A nicer Python indentation style for vim.
nvim-cmp - A completion plugin for neovim coded in Lua.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
nvim-dap - Debug Adapter Protocol client implementation for Neovim
tree-sitter - An incremental parsing system for programming tools