The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Neovim-ui Alternatives
Similar projects and alternatives to neovim-ui
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
lspsaga.nvim
Discontinued improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim] (by glepnir)
-
popup.nvim
[WIP] An implementation of the Popup API from vim in Neovim. Hope to upstream when complete
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
neovim-ui reviews and mentions
- 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.
-
A note from our sponsor - WorkOS
workos.com | 26 Apr 2024
Stats
nvim-lua/neovim-ui is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of neovim-ui is Lua.
Sponsored