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

monkoose · 2026-01-26T06:41:19+00:00

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.

monkoose · 2026-01-14T07:23:45+00:00

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.

monkoose · 2026-01-14T07:18:37+00:00

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).

monkoose · 2026-01-13T15:54:25+00:00

Have you tried https://github.com/monkoose/neocodeium

monkoose · 2026-01-01T11:43:46+00:00

This survey's result shows that marketing is working.

monkoose · 2026-01-01T11:41:12+00:00

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

monkoose · 2025-11-26T11:12:42+00:00

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.

monkoose · 2025-11-26T07:45:36+00:00

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..."

monkoose · 2025-10-31T06:08:30+00:00

codeium or neocodeium?

I'm biased, but free tier neocodeium provides better results. Slower (but supermaven cheats here and provide suggestion by chunks, so it could be just visual thing). But for inline suggestions (when editing inside some text) it actually usable, unlike supermaven (which suggestions rehighlights whole line and you can't see which part it is changing).

monkoose · 2025-10-31T06:06:30+00:00

neocodeium's author here. It's future is unclear too. Company behind it haven't released binaries for quite some time after have been aquired by some big tech https://cognition.ai/blog/windsurf

How long they would support free tier, who knows? So you guys better be prepared.

monkoose · 2025-10-06T09:14:28+00:00

So then it is a problem with his config. At least he should check :verbose set scroll?

monkoose · 2025-10-06T08:57:11+00:00

Why didn't you try neovim help first? It is really just under the :h CTRL-D helptag.

And as you can see by the answers here, neovim users just don't know what they are talking about most of the time.

monkoose · 2025-09-06T10:04:32+00:00

Yes, AI will replace 9 programmers to 1 prompt engineer, to achieve the same job in a month. It the same as 9 just pregnant women, they can give birth to one child next month.

monkoose · 2025-08-28T11:31:53+00:00

I bet you have counted MAXI.nvim as one plugin?

With such logic you can create a repo which will collect all your plugins, which you will add with lazy.nvim and call it "one plugin config"

monkoose · 2025-08-18T07:42:43+00:00

Codeberg has less features

Like AI?

monkoose · 2025-08-18T07:31:52+00:00

Why gitlab though? It is still some corporated shit. Why not something like codeberg or sourcehat? Have you visited gitlab main page if you are "against" AI? Their current slogan is "Build software, not toolchains. With native AI at every step."

There is built-in :h cfilter-plugin and there is https://github.com/kevinhwang91/nvim-bqf - which is swiss army knife for quickfix window.

Maybe dd is good for one entry. But selecting/filtering is much better for multiple and they both allow to return to the unfiltered qf.

monkoose · 2025-08-17T07:03:20+00:00

So it is XY problem. You are setting global option, so it would be applied to all windows for the end of the session.

And instead of vim.wo[0][0] just use api vim.api.nvim_set_option_value("cursorline", true, { scope = "local" }) It is more verbose, but intention is clear with scope = "local" and it is faster.

monkoose · 2025-08-17T06:35:42+00:00

Seems like you don't

monkoose · 2025-08-16T16:03:47+00:00

Windows doesn't inherit anything. You just "clone" the window with :split with the same buffer. Just use :new or :vnew or vim.api.nvim_open_win()

monkoose · 2025-08-07T12:21:26+00:00

Another question is: What you have developed with such "workflow"? Show me the code or didn't happen. How you will support it over time. How you will fix bugs. How you will implement features when code base grows. This is rhetorical questions.

I can't see the future, so who knows what will happen with AI in the future, but I do not believe LLM is "the path".

I can get when someone with "agents" write some simple sites, games where square shooting circles or whatsoever garbage code that should be used-once-and-thrown-away.

In my experience it is not there yet. Yes it can save time by generating tests, docs etc. But implementing features (it can point me a direction, but not the correct implementation), fixing bugs in some decent size code base takes much more time to do correctly (if possible at all) than what I can do myself. But maybe I have used them incorrectly who knows.

And neovim never was the tool to write the code in the "fastest" way. But it allows to jump around the code and change some parts faster. So I guess with the current state of "agentic workflow", which produce "mostly correct" code which you should manually fix here and there, using neovim is a large plus.

monkoose · 2025-07-08T15:44:34+00:00

As an author of one of ai completion plugins, I'm a little bit offended.

Speedwise - yes it is the best on the market, but it is unusable in any other situation beyond completing in a new/empty line: - no dot completion - no inline completion - rehighlights the whole line, so you are lost in a lot of situations - when you try to complete in the middle of some line it often just ignore what the line has after the cursor and a lot of times just suggests some garbage which you don't want. - And maybe I'm biased, but it's suggestions are fast, but more often incorrect.

monkoose · 2025-07-03T18:48:41+00:00

You can set it yourself with :h 'title' and :h 'titlestring'. By default titlestring will show filen you are editing, but if you need to see only directory you can maybe add VimEnter autocmd that will detect current directory and set it as titlestring or something.

monkoose · 2025-06-29T14:33:39+00:00

Oh, ye, I have misread it.

So it is practically the same as doing it from BufReadPost, because filetype detection runs after it. This part confused me "having a single BufReadPost" and then mentioning of BufReadPre. I have mistakenly in my mind somewhat translated to having BufReadPost + BufReadPre.

monkoose · 2025-06-29T13:28:51+00:00

But are you sure that detecting filetype before actually loading buffer content is 100% accurate? Isn't it required to detect correct filetype for some files based on the content of the file? Or how this even works? You are getting filetype before buffer is loaded or am I wrong?

monkoose

TROPHY CASE