bubbly.nvim VS zest.nvim

[lsp-status](https://github.com/nvim-lua/lsp-status.nvim) that's used by the statusline plugin I use ([bubbly.nvim](https://github.com/datwaft/bubbly.nvim)) to populate lsp diagnostic info in the status bar (ex. 2 errors, 50 warnings, etc). I only added it per suggestion of the plugin, so it's quite possible you wouldn't need it.

The bottom bar (statusline) is also a creation of my own: bubbly.nvim. Actually, I was procrastinating fixing some issues by creating my own macros xD

bubbly

Hey thanks for sharing this ! I like the minimalism of your status line, I think I'll use it as I'm more or less rebuilding my config and wanted something else than bubbly.nvim (which is also cool!)

Zest: similar to Aniseed, but much less expansive. It's a good option if you want a bit less diy if you want to deal with macros

zest provides some macros for configuring Neovim and is usable with Hotpot or Aniseed.

Thanks for mentioning zest! I'm certain that it will remain primarily a macro library. I've disabled the tiny compiler it ships with by default to prevent any confusion. As such, it should be compatible with hotpot out of the box.

I would greatly appreciate it if linked to zest.nvim in your readme.

Another plugin that gave me realization is zest.nvim, which uses the Fennel language to simplify configuration by a lot. Fennel's lispyness, REPL, and macros is gonna be a huge boost in Neovim productivity.

Also, this is a shameless plug, but I'm working on a macro library that aims to streamline the configuration process of neovim with fennel. It is a heavy WIP, but I think at this point it conveys the general idea reasonably well. See tsbohc/zest.nvim for more details.