info.vim
By HiPhish
nvim-metals
A Metals plugin for Neovim (by scalameta)
info.vim | nvim-metals | |
---|---|---|
5 | 12 | |
- | 429 | |
- | 3.5% | |
- | 7.6 | |
- | 6 days ago | |
Lua | ||
- | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
info.vim
Posts with mentions or reviews of info.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-28.
-
vimscript over lua
As for writing plugins though, Lua beats Vim script any time of the day. I wrote info.vim back in the early days and it was a major pain to write in Vim script. If I had to redo it today I would 100% write it in Lua.
-
plugin annoncement - nvlime
Yeah, mapping a function instead of a mapping is even better. I just don't like if a predefined mapping is hard to remember or (even worse) conflicts with one of my existing mappings. Personally I like it the way Neovim's LSP client does it: you get a Lua (or Vim script) API that you can map yourself. In my info.vim I provide the commands :InfoNext, :InfoPrev and :InfoUp, but I also have a code snippet of reasonable default bindings in my README that people can just copy-past into their configuration. If they disagree with my defaults they can then change that snippet instead of having to fight my plugin to scrub away the defaults.
-
sidebar.nvim - A generic and modular lua sidebar
info.vim (my own)
-
Man pages in color, with links
I think we're all aware of the Man plugin, What I really want is info.vim being distributed by default aswell.
-
Future plans for Autotools
A wiki is not adequate documentation and I hate this trend of making documentation HTML only. Not everyone uses or even can use a web browser. GNU software has this great tool called Texinfo which lets you write a proper book-sized documentation with proper table of contents, chapters, and indexes. You can generate HTML, PDF, and most importantly info files. You can read info files in your terminal, in Emacs, or even in Vim (wrote a plugin for that).
nvim-metals
Posts with mentions or reviews of nvim-metals.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-13.
-
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?
What are some alternatives?
When comparing info.vim and nvim-metals you can also consider the following projects:
vlime - A Common Lisp dev environment for Vim (and Neovim)
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
vinfo - Vim info documentation reader, lets you read info pages within Vim or start it from the shell prompt (instead of Info)
nvim-lua-guide - A guide to using Lua in Neovim
sidebar.nvim - A generic and modular lua sidebar for Neovim
neovim - Vim-fork focused on extensibility and usability
Vim - The official Vim repository
tree-sitter-scala - Scala grammar for tree-sitter
nvim-cmp - A completion plugin for neovim coded in Lua.
nvlime - A Common Lisp development environment for Neovim
nvim-dap - Debug Adapter Protocol client implementation for Neovim