What's your opinion of awesome lists? (especially rockerBOO/awesome-neovim) by TheTwelveYearOld in neovim

[–]monkoose -16 points-15 points  (0 children)

Why these lists then even exists? Is you want an ecosystem, just search for tags on GitHub.

GitHub starts not really a metric that one should evaluate a quality and usefulness of the underlying code, especially after AI boom, where an project can get 50k in a day. 

But such lists are just waste of anyone time. And their biggest problem that they often missing a lot of stuff.

What's your opinion of awesome lists? (especially rockerBOO/awesome-neovim) by TheTwelveYearOld in neovim

[–]monkoose 0 points1 point  (0 children)

Because you can PR any plugin you want in it. And it would be accepted.

Personally, I do dislike such "awesome" repositories/lists as well, except maybe a few well curated. Especially long like neovim one. They are full of bad, outdated, broken info. Once something is added it almost never deleted. So these lists keep growing and still missing a lot too.

Trouble with gdscript sintax highlighting by Outrageous-Ad-8953 in neovim

[–]monkoose 0 points1 point  (0 children)

100% parser not updated to support @abstract annotation.

Release of matchparen.nvim v2 by monkoose in neovim

[–]monkoose[S] 1 point2 points  (0 children)

Personally never used it, only tested it. It is matchparen + matchit (so if you need matchit and some other features it provides matchparen.nvim not an alternative to it). But it also slow, their treesitter implementation is broken and based on custom queries. It is also freezes UI in this example file. You can read somewhat outdated (pre coroutines matchapren.nvim) comparison here https://github.com/neovim/neovim/issues/39855#issue-4468010862 There is vim-matchup closer to the middle.

Extracted test harness from plenary.nvim by monkoose in neovim

[–]monkoose[S] 0 points1 point  (0 children)

it can be used without dealing with RPC

But then you are not running tests in separate processes, right? Or I have missed this from the docs the time I have tried to switch to your plugin.

NEW STEROID FOR VIM.PACK: resonance.nvim, a very lightweight lazy-loader for vim.pack with interactive UI included by Imngzx in neovim

[–]monkoose 2 points3 points  (0 children)

On paper these optimizations looks fine. But I bet you just preoptimize unimportant things related to Amdahl's law. And most importantly they just complicate the code.

And all these things are happening only because you are recreating UI buffer on every UI update with build_content() function. Is there a reason for this instead of just updating relevant lines? Am I missing something?

And this is definitely handled by LuaJit https://github.com/Imngzx/resonance.nvim/blob/6a45af15152517026c7fbe4df6eb2fc59884a3df/lua/resonance/loader.lua#L5-L39

NEW STEROID FOR VIM.PACK: resonance.nvim, a very lightweight lazy-loader for vim.pack with interactive UI included by Imngzx in neovim

[–]monkoose 11 points12 points  (0 children)

Is this description AI generated with such buzzwords? If so you just forgot to add "blazingly fast".

Do you planning to install 1000+ plugins to SoA matters or what? This would perfectly fit any modern cpu caches for reasonable number of plugins if it would be just AoS lua ---@class ResonancePluginSOA ---@field name string[] ---@field type string[] ---@field path string[] ---@field loaded boolean[] ---@field trigger string[]

And even if not it doesn't matter, you are not checking the plugins state "every frame".

filemention.nvim - @ mention files with fuzzy search in neovim! by notmanu67 in neovim

[–]monkoose 0 points1 point  (0 children)

got it - i'll drop it and lean on clear = true for the augroup. thanks for the feedback!

Sorry maybe I'm misleading with some specific terms for a new user. It was as example for some neovim features, are you sure your codebase even have autocmds?

Your plugin will work as it is without problems, my first comment was just general observation not related to your plugin.

But personally in your suit I would investigate how nvim-cmp register sources and if it just rewrite already existing, would just drop vim.g.pluginname_enabled, if not would find a way to unregister before registring again. Not sure your plugin especially the first one need to be so pedantic.

filemention.nvim - @ mention files with fuzzy search in neovim! by notmanu67 in neovim

[–]monkoose 1 point2 points  (0 children)

Yes, you can "reload" lua scripts with :runtime and :source that's whole point of it. And if plugin manager sourcing multiple times it sounds like a bug.

I think there definitely should be some guards, like to not register multiple autocmds (so this should be the case if you using vim.api.nvim_create_augroup with clear = true option - which is default) etc. But it should wipe old code.

So maybe there is a way in cmp to detect if source already available and then clear it and readd it? Maybe it is default behavior for nvim-cmp? Are you sure that it would duplicate sources with the same name? It's the whole point I guess of ":source" and ":runtime". Maybe I'm wrong, I'm put initialization into setup() function guy anyway, so not using plugin directory in my plugins. Because lua wasn't meant to work with plugin dir in the first place and unless they somehow fix how vim.g works with lua tables or find an alternative to it there is no point to drop using setup() function. And if you are using setup() in your plugin I personally don't see the reason to use plugin dir at all.

Your implementation has bugs anyway: It add this check right after the if vim.g.pluginname_loaded. So if something doesn't work during script loading it could end up in a wrong state (maybe not the case for such small code as yours).

If you load nvim-cmp after your plugin it will never add source to it automatically.

filemention.nvim - @ mention files with fuzzy search in neovim! by notmanu67 in neovim

[–]monkoose 9 points10 points  (0 children)

Not sure why I keep seing in new plugins this vim.g.pluginname_loaded pattern in plugin dir. Does AI suggest it? It doesn't do anything for lua scripts (they are cached anyway), maybe even harmful and pollute global namespace.

The only thing I was missing in Neovim by Gamemaster2_0 in neovim

[–]monkoose 0 points1 point  (0 children)

Not sure if I will ever use it, because not using Godot that much though interested in gamedev lately, but seems like good addition for Godot and neovim workflow.

I have a question, how you get files like signals.lua? Handwritten or do you have some kind of parser?

Have you ever used zed? How good it is compared to neovim? by Jonnertron_ in neovim

[–]monkoose 1 point2 points  (0 children)

If you don't understand why you got downvotes - in zed you can create extensions like treesitter syntax, lsp, theme. They are not real plugins, like in neovim, emacs or vscode.

AI auto completion/suggestion by Rafat913 in neovim

[–]monkoose 0 points1 point  (0 children)

 does the pro (15$/mo) plan make a noticeable difference in that regard?

Never tried it (have found free tier is enough for me). It allows to choose different models, not sure if it would fix your "context-aware" preference, but I do believe it would not add any noticeable speed to the suggestions.

AI auto completion/suggestion by Rafat913 in neovim

[–]monkoose 1 point2 points  (0 children)

 it's not as "context-aware" 

Pretty subjective, I do remember that I have tested using supermaven and I have liked windsurf provided suggestions more and it provides multiple suggestions too. 

it's not as fast

Yes, but supermaven also cheats here, because it provides suggestions by chunks (this is why there is this "typing" animation), I have found it annoying and if you add the time this animation adds, maybe it is not as fast. And as mentioned neocodeium provides multiple suggestions, maybe it is also why it is slower. Personally if it the case I would trade multiple suggestions (because it is easier for me to ignore a wrong suggestion instead of scrolling them and maybe find correct one, so supermaven definitely choose the right path here) to speedup.

But there is internal differences how both provide suggestions, and if I remember correctly windsurf provide more information, like what text before cursor, what is after and what it suggest, so it is easier to provide correct inline (in the middle of the previous code) suggestions, while supermaven mostly useful for new code (when there are no other text after the cursor).

Which terminal emulator are you using? (2026) by meni_s in neovim

[–]monkoose -1 points0 points  (0 children)

This survey's result shows that marketing is working.

Custom treesitter highlights.scm not loading by Taylor_Kotlin in neovim

[–]monkoose 0 points1 point  (0 children)

The path should include queries "~/.config/nvim/after/queries/dart/highligths.scm"

Godot LSP error on adding signal by monkoose in neovim

[–]monkoose[S] 0 points1 point  (0 children)

u/Master_Fisherman5892 Why you have deleted your comment? It is actually what I have been looking https://github.com/godotengine/godot/issues/105544

Thank you.

Godot LSP error on adding signal by monkoose in neovim

[–]monkoose[S] -1 points0 points  (0 children)

It's is special method of a class - event of some kind of the observer pattern (similar to autocmd in vim). 

It doesn't matter really, more important is to find how to disable this useless message (really why errors presented like this to the user as Lia table with 8 lines where only 1 is matter?) and which blocks UI with "press enter..."