A colorscheme built around hierarchy. Each kind of code gets its own color group, split between what comes from the language and its standard library and what's defined in your code.

The palette is just my taste, and it's exposed so you can swap in the colors from your favorite color scheme. The hierarchy stays intact.

Repo: https://codeberg.org/navahas/sanzo.nvim
The reasoning behind it: https://culturecode.dev/posts/what-most-colorschemes-miss

https://github.com/antosha417/nvim-lsp-file-operations

Hello there, @DrKJeff16 here.

I recently became a co-maintainer for nvim-lsp-file-operations and got to work on it. Here's a list of recent improvements:

• Massively improved load times
• Dropped plenary.nvim as a dependency (#55)
  • Redid the logging framework from the ground up
• Added missing neo-tree.nvim events (credits to @mehalter, #43)
• Added public API functions for create(), delete() and rename() (#56)
• Auto-save can now be enabled during setup (#57)
• New user command (:LFO) for standalone usage; supports tab completions (#58)
• Added backwards-compatibility for LSP operations in Neovim <v0.11 (#47)
• Code is now fully annotated
• Reworded and restructured the README
  • Added install instructions for vim.pack

There's more but that was the list of important changes.

Shoutout to @Crysthamus, the author of Crysthamus/nvim-file-operations, as some of the improvements were based off of his. Attribution is both in the code and the README.

Hopefully you enjoy this new batch of changes!

- Sincerely, DrKJeff16

Recently, I started getting emails from business developers who are proposing to place my 10 github star plug-ins in front of .. I guess .. you guys, to make me tons of 🫰 I hope you're ready to start paying up. It seems like neovim users have finally been put in the same category as Apple users who can be charged a premium 😆

BTW, are there any paid plug-ins around in the neovim ecosystem? There was a closed source and paid vim fuzzy finder plug-in back in the day. I don't remember its name nor have I used it but I did consider paying for it back then.

On a more serious note: Are you financially supporting the plug-in ecosystem? If so, I'd like to know more. Not even sure whether there are any needs.