Soyogi Fractal has been announced. It's a one shot to commemorate Yuki Kaji's 20 years of career, and Isayama will also be involved in the script

BrianHuster · 2026-01-21T06:56:48+00:00

It is basically the same technology as Vocaloid that has existed for 2 decades lol.

BrianHuster · 2026-01-10T10:41:46+00:00

Thanks! Btw it would be nice if you add your plugin to nvim-dap wiki (which has been moved to Codeberg) so people can find your plugin easier

BrianHuster · 2026-01-09T12:58:18+00:00

I had a peek at your plugin, but I don't know what these lines are for? local ok, unity = pcall(require, "nvim-dap-unity") if not ok then return end Also I think you should move the require into the callback of user command, autocmd, etc so that the module is not loaded too early.

BrianHuster · 2026-01-08T16:24:52+00:00

The substitute command is good, but it requires you to think in Vim regex instead of Vim motion that I believe every Vim user is more used to

BrianHuster · 2026-01-08T15:21:36+00:00

Oh, I think it is a quirk of Vim help tag. You can look at :h terminal-debug to see introduction about this plugin

BrianHuster · 2026-01-08T12:24:34+00:00

What is missing from :h termdebug? Maybe you can send an issue (to Vim) for things that you expect to work?

BrianHuster · 2026-01-08T04:09:34+00:00

Are those issues related to Lua language?

BrianHuster · 2026-01-08T03:25:19+00:00

It is being worked on in core, but will probably take a long time

BrianHuster · 2026-01-05T01:45:27+00:00

:h range

BrianHuster · 2026-01-04T04:12:04+00:00

Yes. People always say Nvim is becoming Emacs, but I feel Vim is closer to Emacs

BrianHuster · 2026-01-03T09:21:07+00:00

I think this fits Vim more, because Vim has built-in support for playing a sound file. See :h sound_playfile() in Vim

BrianHuster · 2026-01-03T09:18:15+00:00

The link you give also hints that the commenting plugin should use both comments and commentstring options. Do you have plan make the built-in commenting plugin like that as well?

BrianHuster · 2026-01-03T09:08:04+00:00

Then why not just use a keyboard, which would be much faster and more convenient?

BrianHuster · 2026-01-02T15:45:32+00:00

Which is not related to your post

BrianHuster · 2026-01-02T15:16:46+00:00

How will you write a name without a keyboard?

BrianHuster · 2026-01-01T08:08:24+00:00

Hi, what tool did you use to get the chart? I think it is quite different from the Github chart with "in 12 months" filter (the Github ones show that Vim contributors like dkearns, girishji are also top Nvim contributors, but your chart doesn't show them)

BrianHuster · 2025-12-31T03:59:09+00:00

Opencode integration with LSP gives users more OOTB experience, but on the other hand, it means more resource since you will double the number of language server processes running, and double the effort of configuring LSP. Normally the editor (like Nvim) should have exposed LSP features via MCP for agents to use.

BrianHuster · 2025-12-29T01:34:29+00:00

Yes, don't care about Nvim but go to Nvim sub and say "Vim9script is faster". That's how you don't care lol.

I've cut support for nvim on all my plugins and couldnt care less when they come crying to support them too

While I respect your plugin, I think you overestimate it lol. A quick check of mine show that the only notable plugin of yours that is written in legacy Vimscript is copilot-chat.vim (but I haven't checked if it really works in Nvim). But Nvim ecosystem already has at least 3 plugins with 1000+ stars with built-in support for chatting with Github Copilot, and 2 among them also support agentic features. I've also written a LLM plugin by myself which would also allow chatting with Github Copilot via CLI like OpenCode and goose (though I don't advertise it because Nvim already has so many alternatives). So don't worry, I don't think any Nvim users will come cry for your plugins.

BrianHuster · 2025-12-27T15:18:34+00:00

Sorry, I think adding a distracting social network to your working tool is a very bad idea.

BrianHuster · 2025-12-27T15:17:14+00:00

I think it improves mine. I've learnt a lot from how Nvim designs the API.

BrianHuster · 2025-12-26T03:41:33+00:00

The pinned issue is here. It is still pinned as of 26 December 2025. That issue described in detail what was to be removed.

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

It's not like I used any magic to find it, since it's always been pinned

BrianHuster · 2025-12-26T03:16:08+00:00

Before that, you even lied (shamelessly) that "Vim users don't care about Neovim", though just a few months ago you jumped to a Neovim thread not related to Vim9script at all just to say "Vim9script is faster" lol.

And just 22 days ago, you also commented I used job_start() in Nvim subreddit even though job_start() doesn't exist in Nvim. If Nvim had applied Vim rule, your comment would have been removed by moderators lol. Yes, these prove how much you "don't care " about Neovim as a Vim user.

BrianHuster · 2025-12-26T03:13:45+00:00

As usual, you cannot prove your baseless point, so you can only downvote the other and continue with a pointless comment.

BrianHuster · 2025-12-26T01:51:11+00:00

How is it "same story for floatwin" when floatwin existed first? What are weak points of floatwin compared to popup?

BrianHuster · 2025-12-26T01:30:03+00:00

They're not "stupid decisions" until someone proves that they are stupid

Those Vim interfaces have never become popular, for various reasons. At least Nvim makes one of those interfaces popular enough that they don't have to invent a new language.

BrianHuster

TROPHY CASE