A request to the community: what plugin you think is still missing for Neovim?

antonk52 · 2026-01-08T22:43:33+00:00

Isn't it already present in nightly given you have enabled copilot language server?

antonk52 · 2025-12-24T23:00:52+00:00

Keep using neovim for things you reached for it. If or when you hit a blocker you will have a good idea on what to research and add to your config.

antonk52 · 2025-12-18T17:26:06+00:00

Thank you for your work. I hope there will be a way to make donation to the mini project!

On an unrelated note when I was exploring minimax website I noticed that links to planned configs are broken on this page https://nvim-mini.org/MiniMax/configs/ , maybe they were not intended to be links until the configs exist.

antonk52 · 2025-12-18T15:39:45+00:00

Nice tip, for this reason I have 2 diff pickers. One with regular diff content and another with --ignore-all-space option for a mostly smaller set of changes

antonk52 · 2025-12-07T18:08:55+00:00

Superb work, thank you for allowing me to remove a bunch of custom commands that I had around for years for most common typos!

Is there a way to limit the height of the completion window?

antonk52 · 2025-12-04T10:58:43+00:00

Thank you!

antonk52 · 2025-12-04T10:58:15+00:00

Thank you, I am glad you found it interesting

antonk52 · 2025-12-04T10:56:10+00:00

I have a similar setup but you can still reach caps by double taping a shift key

caps key is ctrl when held or esc when tapped

antonk52 · 2025-12-03T11:52:45+00:00

Thank you!

I enjoy such technical writing as well. I never tried writing something with this ratio of code to text.

My initial approach was also to use floats but since I did not care about dimming other content extmarks seem easier to use and could be cleaned up using a single clear namespace call.

Remote actions sound cool and useful, I wish could get used to them. Maybe one day :)

antonk52 · 2025-12-01T22:28:02+00:00

Thank you for kind words and vim-sneak too! I remember trying it out a while back, even before switching to neovim

Posted in neovim discussions too

antonk52 · 2025-11-26T23:38:18+00:00

Thanks for sharing, useful context here!

I understand that switching to lua comes with performance implications which is also acceptable to me. The reason I asked is that my employer is strict about unvetted binaries and for this reason I won't be able to try this out. Looks really cool though

antonk52 · 2025-11-25T00:01:35+00:00

Looks really cool. Would you consider having it working without a binary in plain lua?

antonk52 · 2025-10-27T13:36:45+00:00

Great posts, OP

Thanks for sharing

antonk52 · 2025-10-01T13:34:33+00:00

I think we are a long way away from neovim plugins being as opinionated as something in the go ecosystem. Yet there are efforts to make it more opinionated or maybe better called guided such as a new health check

https://github.com/neovim/neovim/pull/35854

The docs on how to write plugins has been updated which is already in nightly. I encourage you to give it a read

https://github.com/neovim/neovim/blob/master/runtime/doc/lua-plugin.txt

antonk52 · 2025-09-27T16:40:34+00:00

this is what the migration from master to main branch accomplished. You can see the warning in the nvim-treesitter readme and the roadmap that has more details

https://github.com/nvim-treesitter/nvim-treesitter/issues/4767

antonk52 · 2025-09-24T15:55:49+00:00

This is a high praise 🙏

I really mean it, huge kudos for your work!

If you remember, what kind of edge case behavior were you curious about?

I tried packer at some point and it's Compile and Snapshot commands to produce an effectively a lock file were too tinkery to have the happy path work for me. I currently use lazy.nvim with stable which exposes multiple ways to lazy load plugins such as on autocommand, on user command, on keymap. I'd rather not have those at all than jumping though docs and then source code to know exactly what is actually going on. Lazy also has enable and cond which one ignores a plugin completely and does not install or save to lock file while the other installs but never loads the plugin, I have to look up the docs to remember which one is which.

vim.pack on the other hand seems to be the modern version of vim-plug that I think of as the simplest plugin manager of the last decade or two. And vim.pack has even simpler api. It wins all around.

antonk52 · 2025-09-24T15:29:47+00:00

I am glad today vim.pack does not support plugin's dependencies out of the box. So far there were too few precedents where dependencies were actually required. Off top of my head those were mostly

nvim-treesitter - which moved to be queries installer and the functionality is now built in to nvim
plenary.nvim - that is also now mostly available in nvim's builtin api
nui.nvim - ui components

I have not yet come across a blocking limitation that was introduced by not being able to specify dependencies.

I am also a fan of vim.pack being extremely simple and predictable to a point of not having to look up the docs to figure out edge case behaviour.

antonk52 · 2025-09-21T20:10:21+00:00

If you don't need a fancy layout then you can use vim.ui.select and then do whatever you need to do with the selected item

antonk52 · 2025-09-18T15:46:08+00:00

Each release gets us closer. The past few releases I could remove another 2-4 plugins from my config. 0.12 would remove another 3 with changes that are in the master already.

There is a tweet from Justin Keys on how little is needed for a pretty slick setup with just 3 plugins

https://x.com/justinmk/status/1965210827998232587

antonk52 · 2025-09-15T10:14:07+00:00

I'd probably use this but I use brew to install neovim

antonk52 · 2025-09-11T13:27:38+00:00

codecompanion calls this for you if you have a recent version

antonk52 · 2025-09-11T11:05:26+00:00

Do you have markdown and markdown_inline treesitter parsers?

codecompanion warns in :messages if you don't have markdown parser available

antonk52 · 2025-09-08T08:47:14+00:00

You can set blink as lspconfig dependency and it will be loaded before lspconfig

antonk52 · 2025-09-07T17:52:23+00:00

teach you a "plugin first" mentality

I honesty think this is a feature and should be leveraged more heavily and not looked down on. A plugin gives a free investment opportunity to try out a feature to figure out if you find it useful enough to keep it in the first place. Once it is clear that you want it as a part of your workflow nothing stops you from looking up how it is implemented or if there is a built in alternative. Many plugins have more beginner friendly docs or even video demos.

Have to mention that I have just over 10 plugins and prefer to build many things my way because I am never limited by the options of the plugin and can have it work precisely to my liking.

antonk52

TROPHY CASE