HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nvim-lua
neovim-ui
Lua2021–2021
nvim-lua / neovim-ui · Archived

neovim-ui

Vaporware -- nothing to see here

2Distinct people
2Mentions
0Explicit recommenders
78GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Vaporware -- nothing to see here

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2021-05-26 19:48:03 UTC to 2021-07-02 22:43:14 UTC. Weeks start Monday, UTC.

012021-05-24 00:00:00 UTC to 2021-05-31 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 242021-05-31 00:00:00 UTC to 2021-06-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-07 00:00:00 UTC to 2021-06-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 72021-06-14 00:00:00 UTC to 2021-06-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-21 00:00:00 UTC to 2021-06-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-28 00:00:00 UTC to 2021-07-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 28

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 242021-05-24 00:00:00 UTC2021-05-31 00:00:00 UTC101
May 312021-05-31 00:00:00 UTC2021-06-07 00:00:00 UTC000
Jun 72021-06-07 00:00:00 UTC2021-06-14 00:00:00 UTC000
Jun 142021-06-14 00:00:00 UTC2021-06-21 00:00:00 UTC000
Jun 212021-06-21 00:00:00 UTC2021-06-28 00:00:00 UTC000
Jun 282021-06-28 00:00:00 UTC2021-07-05 00:00:00 UTC101

What Hacker News says

2 sources
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). T
Read the rest
he 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.
In Neovim v0.5
Yup! We want to create interfaces to make this simpler for people to use. One example is here: https://github.com/mjlbach/neovim-ui which is just in a separate repo to make it easier to work on rather than one huge PR. This is an extension of the ideas that I started in https://github.com/nvim-lua/popup.nvim and a few other places. The idea would to be to create interfaces that users, plugins and/or GUIs could override to provide a unified experience while still being customizable for users. (and as a self plug, I think we have a lot of interesting ideas in telescope.nvim about UI that could be upstreamed over time)
In Neovim 0.5 is overpowering

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.