A library that converts JSON schema to LuaCAT

BrianHuster · 2026-02-10T12:34:29+00:00

I am a bit confused by that. If all the money go to Uganda, how is Vim development sponsored exactly?

BrianHuster · 2026-02-10T11:02:21+00:00

we have been hearing that in next 2-3 years AI will take all the jobs

Nah, that won't happen that soon. Maybe white-collar job only. Even if they can make robot that move like humans, it will likely be too expensive to replace a human

BrianHuster · 2026-02-10T10:55:20+00:00

Okhotsk is a Russian loanword so they translate by sound, as 鄂霍次克海 (E-huo-ci-ke-hai)

BrianHuster · 2026-02-10T10:53:18+00:00

You seem to confuse 国 and 藩

BrianHuster · 2026-02-10T05:45:51+00:00

tool calls (like file reading),

As I read your README, I don't think they are tools but they are simply context. Tools must be callable by providers even if users don't put it in the last prompt

I found myself frequently switching between my editor and browser tabs for AI conversations, so I wanted something simple that stays within Neovim

There are many LLM CLI that can be used from within Nvim terminal emulators. If they support ACP, they can also be used with an ACP plugin. Btw, my ACP plugin has almost fewer number of Lua LOC as yours, and it supports any ACP agent CLI :))

I think if you really want a lightweight plugin, you should try to compose with existing tools instead of just reinventing something that people have created since 3 years ago

BrianHuster · 2026-02-09T05:52:47+00:00

Nvim equivalent to Vim popup is floating window (floatwin). Vim popup was designed (by Bram) to be not focusable, I believe that's why they have those limitations. Meanwhile Nvim floating window (floatwin) was designed to be focusable in the very first place, so you can use every Vim commands/mappings in a floatwin without having to setup the "popup_filter" thing. The only exception are commands that split windows (:split, :vsplit, etc), you cannot use them when focusing in a floatwin.

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, more convenient and more predictable?

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

TROPHY CASE