u/jceb

Do you do that for the simple plugins you use? Personally, I'm happy for every plugin I don't own and someone else keeps an eye on.

If the plugin noise is too high, why not create another subreddit dedicated to plugins and forbid posting plugins in this one. That would be way cleaner and allow people to unplug from the plugin wave altogether. It also reduces the burden the moderators who now have to research the plugins commit history. Maybe the moderators are in need of extra work and designed the policy to fill this gap 🤷

It adds an extra burden on plugin authors, doesn't it. I don't think this is a good idea.

I don't get the haste argument. What does it even mean? The policy is designed to curb AI slop .. by putting constraints on everyone. The moment I feel like I should share my plugin should be the moment I can share it. I assume that for most plugin authors its not a full-time job to create plugins and schedule announcements.

Well anyway, I won't argue this any further. If everyone wants more bureaucracy, let them have it. I don't see how any of this is going to benefit plugin authors and the community in general.

Yep, that didn't take two months. It took a few days / weeks,. Way less than the proposed 2 months.

I love the proposition. Let's set up a nice bureaucracy first and then we talk about working around it. Well, there's still Show Hackernews.

Are you a developer? Have you created any plugins? Most plugins are rather small. The way I create plugins is that there is an initial effort and then it stalls because I've achieved everything I want. The plugin doesn't take 2 months to get to a useful state, maybe a weekend or two. And then, as usage grows and bug reports trickle in, it sees some more development. That's it. What's the effect of delaying the plugin being posted by two months? Either people won't post it at all or bug fixing and usage will be slowed down by 1 month at least. What for? 🤷

Too bad, I find 2 months a very long period. Remember the multicursor conversation? Would it have been possible to post the plugins that resulted out of it? I don't think so. The plugins are still under active development and have passed the 2 month mark by now. At the same time, I don't think the conversation would have been the same without the plugins.

In my opinion, the rules are overreaching and don't help. Were there too many plugin posts? I don't think so.

I ran into the same situation. The simplicity is great, however a bit more granularity would be welcome.

Yes, same here. OSS is the way to go .. however, then it's one person/a very small group picking up the bill for all of us.

Well, yes, someone's investing in the plugins to make them work. I think all plug-ins we use are worth paying for / supporting the devs who sink their time into them.

Don't worry, it's a fun post to cheer us all up. I'm sure tons of people have received such mails 😄

Same here, I put it into an installable plugin: https://github.com/jceb/multicursor-mappings.nvim

I implemented very similar mappings while mainly using neovim's built-in API to perform the file operations: https://github.com/jceb/vimrc/blob/main/lua/custom/plugins/local/directory/after/ftplugin/directory.lua

BTW, have you tried the latest version that I posted recently: https://github.com/jceb/multicursor-mappings.nvim?

See also https://www.reddit.com/r/neovim/s/GIMtZ5ZdkR

The if check verifies whether there is more than one cursor, i.e. you press <M-n> more than 1 time in a row. In that case, the next location is searched for and a cursor of placed.

Say again, where should we call this function?

I use a pre-commit hook that prevents such issues.

You can use a central key vault like Vault, Azure and the like. This reduces onboarding efforts massively since no key material needs to be shared.

u/brokenreed5 I was able to reproduce and fix your issue. You can find the updated version here: https://github.com/jceb/multicursor-mappings.nvim

Strange, `<M-a>` in visual mode produces exactly the result I was expecting. Maybe I need to update neovim to see if something broke 🤷

Thanks, I'll take a look at it.

I second that. jiejie plugin and the multicursor implementation made 2026 a very special year for me in neovim. I also packaged a number of multicursor-mappings that provide the convenience of existing multicursor plugins for the native implementation.

I've created jiejie.nvim as a fugitive-like interface to the jujutsu version control system at the beginning of this year. The results surpassed my expectations - my git workflow is now so much more enjoyable 😊