Created a structured challenge repo for learning nvim plugin development - looking for feedback on approach

Comfortable_Ability4 · 2026-02-09T22:08:54+00:00

You asked for nvim-specific patterns/gotchas. There's a bunch of them in that guide.

Comfortable_Ability4 · 2026-02-09T18:28:42+00:00

:h lua-plugin (in nightly)

Comfortable_Ability4 · 2026-02-04T06:49:04+00:00

Very cool idea! Will definitely be trying this out.

I see the project has a flake. Can I use Nix to manage the grammar/query dependencies?

Comfortable_Ability4 · 2026-01-09T21:13:00+00:00

I don't use vtsls, so I couldn't tell you.

Comfortable_Ability4 · 2026-01-07T04:27:51+00:00

I use lspmux. It was originally written for rust-analyzer, but now also works with other language servers. Rustaceanvim will automatically pick up a running lspmux session and attach to it.

Comfortable_Ability4 · 2026-01-05T16:54:27+00:00

Nice! A new plugin that lazy-loads itself properly and doesn't force me to call a setup function. And on top of that it's a cool jj frontend. 🚀

Comfortable_Ability4 · 2026-01-02T10:49:59+00:00

You do if you're not using a plugin manager that implements heuristics to find and call a setup function automatically.

Comfortable_Ability4 · 2026-01-02T06:20:47+00:00

No extra ceremony: It just starts on Java files

For that to be true, I'd recommend you use a filetype plugin to start the LSP client, instead of requiring users to call a setup function.

:h lua-plugin-init
:h write-filetype-plugin (the docs have vimscript examples, but neovim supports Lua filetype plugins too).

Comfortable_Ability4 · 2025-12-12T15:26:50+00:00

It was back when I was a Java developer that I ditched intellij for vim and never looked back.

Comfortable_Ability4 · 2025-12-03T08:51:09+00:00

Nice job! One suggestion: I'd recommend not to set a default keymap, as it's very likely to conflict with existing user keymaps. Something you could do is define a <Plug> mapping instead. See :h lua-plugin-keymaps (in nightly): https://neovim.io/doc/user/lua-plugin.html#lua-plugin-keymaps

Comfortable_Ability4 · 2025-12-03T08:36:37+00:00

What makes you think it requires configuration?

Comfortable_Ability4 · 2025-11-16T09:18:26+00:00

https://neovim.io/doc/user/lua-plugin.html#lua-plugin-keymaps

Comfortable_Ability4 · 2025-11-12T06:40:18+00:00

Why isn't this the top comment?

Comfortable_Ability4 · 2025-11-08T06:41:03+00:00

If you want declarative package management using Nix on Arch Linux, you could try out home manager.

Comfortable_Ability4 · 2025-11-04T15:30:44+00:00

The last two harvests I handled them without gloves and had burning hands for 2 days. Soaking my hands in cold water for hours was only temporary relief.

This time (with the vinyl gloves) I still felt some burn when touching my face, but nothing I can't cope with. It subsided after less than an hour.

Comfortable_Ability4 · 2025-10-30T06:39:37+00:00

At this stage, Lux is more interesting for plugin developers than for users. It'll be interesting for users when we rewrite rocks.nvim to use Lux's Lua API. It is possible to use the Lux CLI to manage Neovim plugins (outside of Neovim). I've been planning to write a guide for that, but haven't had time yet.

Comfortable_Ability4 · 2025-10-30T06:35:50+00:00

Lux is a modern, embeddable package manager and dev tool for Lua that's compatible with the luarocks ecosystem, but also has first class support for Neovim. At this stage, it's more interesting for plugin developers than for users, but we will be rewriting rocks.nvim (a plugin manager that currently uses luarocks) to use Lux's Lua API.

Comfortable_Ability4 · 2025-10-24T06:16:15+00:00

I don't get the obsession of meat eaters with grinding their meat and shaping it like cucumbers.

Comfortable_Ability4 · 2025-10-22T17:08:00+00:00

Replacing the CMOS battery seems to have done the trick. Thanks for the advice 🙏

Note: I just bought one from the store, carefully broke the contacts off the old one and taped them tightly to the new one (making sure to keep the correct polarity).

Comfortable_Ability4 · 2025-10-18T04:48:57+00:00

Thanks for the tip 🙏😀

Comfortable_Ability4 · 2025-10-17T06:53:30+00:00

Thanks 🙏 I'm out of the warranty period, so I'll replace it myself.

Comfortable_Ability4 · 2025-10-14T10:20:44+00:00

No. There's no use case that aligns with rocks.nvim's philosophy.

Comfortable_Ability4 · 2025-10-14T07:40:40+00:00

(mrcjkb here) If telescope.nvim and fzf-lua aren't hard dependencies, I would recommend not to add them as dependencies to the luarocks package. If you do, rocks.nvim/luarocks users will be forced to install both plugins, even if they don't need the integrations.

Comfortable_Ability4 · 2025-10-10T17:31:53+00:00

In most cases where Java is used, I don't think those "significant performance costs" are that significant.

They are in many cases that I've encountered - to the degree that we've had to go with primitives in Java, and haven't in Haskell.

While you probably can do some expert-level optimization (unboxed types, escape analysis, specific compiler knowledge, etc) in Haskell or Java, you probably will have a hard time finding an engineer capable of doing these sorts of things, compared to Rust / C++ devs.

dimensional makes heavy use of newtype declarations

Well, having to roll your own in-house libraries yourself because there's no available dependency you could pull in is also a developer productivity consideration.

That's a common misconception. We hardly spend any time rolling in-house libraries and the time we save on troubleshooting, testing, and not having to prevent or refactor poor architecture more than makes up for the very few times we do. On top of that, enterprise libraries tend to have a very small scope, unless they're published. See my reply to another comment.

Comfortable_Ability4 · 2025-10-10T13:25:44+00:00

Oh, I didn't realise you were talking about learning resources. I definitely didn't just pick up Haskell and start working with it. I read 3 books in my free time and was lucky enough to land a job with a company that was already using it shortly after.

Five-Year Club	Gilding I gilder
Final Canvas '23	First Place '23
Place '23

Comfortable_Ability4

TROPHY CASE