neovim-ui VS aniseed

mjlbach/neovim-ui

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.

Yep, I started working on this awhile ago https://github.com/mjlbach/neovim-ui but put it on hold for 0.5 stabilization.

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.

aniseed

You don't need to transpile it if you use https://github.com/Olical/aniseed

Something similar: Fennel (https://fennel-lang.org/) is a lisp that compiles into Lua, which nvim can use as plugins, so you can write nvim plugins in a lisp. Aniseed (https://github.com/Olical/aniseed) makes this really easy.

Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim.

1: https://github.com/Olical/aniseed

2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/

I use Aniseed to write my configs in Fennel, and I can't seem to find a way to get Aniseed bootstrapped and managed by lazy. Folke has said that fennel isn't supported in issues about hotpot and tangerine, but neither of them particularly help me solve my issue

:!git clone https://github.com/Olical/aniseed /home/USER/.local/share/nvim/site/pack/packer/start/aniseed Cloning into '/home/USER/.local/share/nvim/site/pack/packer/start/aniseed'...

Have you tried aniseed ?

Aniseed: mostly an environment, it does handle configuration. It adds a lot of clojure features (another modern Lisp) such as a module system. It does seem to be slower to startup though, but I really like how its module system works and still use it for that reason alone. There's not much boilerplate code, just add it to the header

The easiest would be to use aniseed: https://github.com/Olical/aniseed, it has a bootstrap script that downloads all the needed dependencies: https://github.com/Olical/aniseed, it also adds some syntax niceties and testing support. Here's an example of a plugin: https://github.com/katawful/kat.nvim