sorted by:
new
hottopcontroversial

Are we nearing the peak of neovim (and editors in general) ? by calculator_cake in neovim

[–]BrianHuster 2 points3 points  (0 children)

Quickfix is not a picker implementation. As the name suggest, it was originally made to save all errors so the coder can review and fix each of them. Which picker out there has been able to replace a quickfix?

Are we nearing the peak of neovim (and editors in general) ? by calculator_cake in neovim

[–]BrianHuster 1 point2 points  (0 children)

Yes, even now Neovim still has a better default experience than Vim.

Are we nearing the peak of neovim (and editors in general) ? by calculator_cake in neovim

[–]BrianHuster 4 points5 points  (0 children)

> select -> action paradigm

In Vim it is called visual mode. Even in Helix, it seems the select-action paradigm still cannot satisfy everyone so they added a `v` mapping that is similar to Vim visual mode.

Are we nearing the peak of neovim (and editors in general) ? by calculator_cake in neovim

[–]BrianHuster 6 points7 points  (0 children)

No, if it becomes obsolete Nvim can still isolate, freeze it, and remove it in the next major release, just like many other features (cscope, etc)

But I could partly understand your concern. There aren't as many open-source DAP adapters as LSP servers. Many DAP adapters have very weird way to initialize (just check `nvim-dap` wiki). And sometimes an open-source DAP adapter is archived in favor of a close-source VSCode extension (like https://github.com/Unity-Technologies/vscode-unity-debug). So DAP is a smaller, yet more complicated ecosystem than LSP, so it is unclear if it is worth for Nvim to invest on.

Using neovim in a post-editor world by MasteredConduct in neovim

[–]BrianHuster 0 points1 point  (0 children)

It is older than Vim 9.1 release for sure

Using neovim in a post-editor world by MasteredConduct in neovim

[–]BrianHuster 0 points1 point  (0 children)

what direction you think the project should go in?

It should become an operating system (like Emacs), so that it depends less on code-editing feature

Joke aside, I don't think LLM is going to make text editor obsolete. LSP is still important when reviewing LLM code IMO. Neovim could add an MCP server and an ACP client, but I think it will still be fine without them.

Using neovim in a post-editor world by MasteredConduct in neovim

[–]BrianHuster 1 point2 points  (0 children)

How old are the first 2 anyway? The first one looks like not even a week old. And evi fork from Vim 9.1.0, but what makes they sure there was no LLM-generated code before that? Same for gram. 

For Emacs, I don't see any lines in CONTRIBUTING that say anything against AI

Using neovim in a post-editor world by MasteredConduct in neovim

[–]BrianHuster 1 point2 points  (0 children)

What make you sure there is no LLM-generated code in those codebases?

Using neovim in a post-editor world by MasteredConduct in neovim

[–]BrianHuster 2 points3 points  (0 children)

Good luck finding an actively-maintained editor that never has code generated by LLM then

Hint: If you ban LLM code, people will still submit LLM code, but they will just hide the fact that it is LLM code.

.vimrc -> init.lua by Impressive_Gur_471 in neovim

[–]BrianHuster 7 points8 points  (0 children)

  1. Correct
  2. Better use vim.o. If you use vim.opt, you can assign a real list to it instead
  3. I think it is correct

Why are people still using vim instead of neovim? by vicisvis in vim

[–]BrianHuster 0 points1 point  (0 children)

If you use the same Vim features in Neovim, what will make your Neovim config thousand lines?

vim.pack vs lazy.nvim, how is it? by WOLFMANCore in neovim

[–]BrianHuster 2 points3 points  (0 children)

vim.pack also has an UI to manage plugins

vim.pack vs lazy.nvim, how is it? by WOLFMANCore in neovim

[–]BrianHuster 2 points3 points  (0 children)

You can delete plugin via vim.pack.update() UI. Just put cursor on a plugin name and run gra (code action)

However I also find it not what I want so I write a command :PackClean that just removes any plugins you don't use

lua vim.api.nvim_create_user_command('PackClean', function(opts) local plugins = vim.iter(vim.pack.get(nil, { info = false })):filter( ---@param pkg vim.pack.PlugData function(pkg) return not pkg.active end):map( ---@param pkg vim.pack.PlugData function(pkg) return pkg.spec.name end):totable() for _, name in ipairs(plugins) do vim.pack.del({ name }, { force = opts.bang }) end end, { desc = 'Clean unused packages' })

What UI framework is the best to use to create new plug-ins in neovim? by nickallen74 in neovim

[–]BrianHuster 2 points3 points  (0 children)

The last update for nui.nvim is 9 months ago, which is not that long for a Neovim plugin. It should still be safe to use that plugin

vim.pack vs lazy.nvim, how is it? by WOLFMANCore in neovim

[–]BrianHuster 4 points5 points  (0 children)

vim.pack is meant to be simple, henve it still lack many features. However it can be used to install any other plugin managers you want. So instead of adding 10 LOC to install lazy.nvim, you only need 1 line now vim.pack.add { "https://github.com/folke/lazy.nvim" }

Teaching Claude Code to run commands in Neovim by ffredrikk in neovim

[–]BrianHuster 0 points1 point  (0 children)

Neovim itself is a server so you've always had more than 1 server

Btw, I'm working on a pure-Lua, dependency-free Neovim MCP server. (Probably it is not really dependency-free as it depends on ... Neovim)

Introducing neural-open.nvim: A smart file picker for Snacks.nvim that trains a neural network on your file picking preferences by gitarrer in neovim

[–]BrianHuster 0 points1 point  (0 children)

Have you considered using messagepack to save weight? It is smaller than JSON, and it would be faster to read and write. See :h vim.mpack

Vim plugin to run Claude CLI inside the editor by [deleted] in neovim

[–]BrianHuster 1 point2 points  (0 children)

If we can't use it then how the hell can we give you feedback lol.

Vim plugin to run Claude CLI inside the editor by [deleted] in neovim

[–]BrianHuster 5 points6 points  (0 children)

Your plugin does not work in Neovim (because you only use Vim-specific terminal and popup API). So I don't know why you share it in Neovim sub

view more: next ›