verktyg | neovim-ui | |
---|---|---|
1 | 5 | |
2 | 83 | |
- | - | |
7.2 | 0.0 | |
4 months ago | about 3 years ago | |
Python | Lua | |
- | GNU General Public License v3.0 or later |
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.
verktyg
neovim-ui
- Posibility of UI library for neovim?
-
Neovim - Build UI using nui.nvim
mjlbach/neovim-ui
-
Neovim v0.5
I understand the frustration (making neovim more cohesive is definitely a goal). It sounds like coc provides the UI you are used to, so there's no harm in sticking with that!
Many of our users explicitly don't want automatically called functions that would slow down the editor (autocommands that map signature requests to the language server, for example), so by nature neovim's core implementation is extremely conservative.
One thing I would like to do, is make the automatic pop-ups for signature easier to implement with our current handler, which means a plugin like signature-x could use our upcoming lsp.config option to configure it's borders (https://github.com/neovim/neovim/pull/14681), and match the rest of the UI.
I also have another project I was working on before the 0.5 stabilization phase (https://github.com/mjlbach/neovim-ui). The goal with this is to have composable/overridable UI elements built into core (which we would use for our internal lsp functions), that can be used (or overridden) by UI plugins.
In summary, I think the likelihood of autocompletion (and generally auto-anything) being built-into core is very small, but providing the APIs in neovim core to make snippets - autocompletion - automated UI elements easier for plugin authors is a high priority.
-
Plugin unification
Yep, I started working on this awhile ago https://github.com/mjlbach/neovim-ui but put it on hold for 0.5 stabilization.
-
status of neovim popup windows
I am working on this, but it will probably have to wait until after the 0.5 release (I don't know when this will be). This is part of the larger UI effort in neovim-ui which is currently glorified vaporware. As far as I know, TJ, Smolck, and I are the only ones who have expressed interest in fixing this.
What are some alternatives?
kickstart.nvim - A launch point for your personal nvim configuration
popup.nvim - [WIP] An implementation of the Popup API from vim in Neovim. Hope to upstream when complete
moonscript - :crescent_moon: A language that compiles to Lua
nui.nvim - UI Component Library for Neovim.
guihua.lua - A GUI library for Neovim plugin developers
TypeScriptToLua - Typescript to lua transpiler. https://typescripttolua.github.io/
nvim-lspconfig - Quickstart configs for Nvim LSP
nvim-lsputils - Better defaults for nvim-lsp actions
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
nvim-treesitter-textobjects
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
vscode-neovim - Vim mode for VSCode, powered by Neovim