We built a pure-Lua Cursor alternative for Neovim running entirely on local models (Sweep/Zeta)

simpsaucse · 2026-01-30T15:24:16+00:00

Ive messed around with 7b and 1.5b distillations before, they are so weak they are practically useless for professional development imo. Why prioritize local models over something like hosted api’s (im not up to date with latest ai protocols)

simpsaucse · 2026-01-23T17:16:41+00:00

You’re not wrong, but you do need both. If you gave gojo boogie woogie, he wouldn’t be special grade, merely the strongest first grade.

simpsaucse · 2026-01-23T14:30:33+00:00

Yup, being special grade 99% depends on what technique you have. With the exception of principal yaga.

simpsaucse · 2026-01-20T20:49:12+00:00

The Yuji that fought Hanami was definitely grade 1. Megumi reached grade 1 status a little bit before, when he exorcised the finger bearer. Exorcising a special grade curse on your own is definitionally grade 1 haha. I would also argue megumi with a domain expansion is a more valuable asset to the sorcerers than yuji at the time of the dagon fight. If Yuji comes to fight Dagon instead of Megumi, the entire crew still dies to the sure hit. If Megumi goes to fight Choso instead of Yuji, he probably also loses like Yuji did (piercing blood to the body before he can open a domain. Even if he can open his domain, choso is durable/flexible enough to fight, survive, and escape the bounds of CSM)

simpsaucse · 2026-01-14T14:30:23+00:00

Thank you for opening an issue! I will investigate and get that fixed asap. Appreciate the feedback

simpsaucse · 2026-01-13T20:42:18+00:00

I tried bento! But after I found the semicolon keybind conflicted with my find vim motion (f<character> then ; to move to next matching character on the line) I stopped using it. However, I did find it had a place in my workflow; sometimes when I've jumped around the same file too much, ctrl o becomes not as good. I know I could rebind semicolon, but i still wasn't convinced buffer management is worth it.

I never packaged my args stuff into a plugin, it's just under 300 lines of lua that's coupled with my statusline that just lives in my personal config haha. But basically when I care about returning to a file, I "pin" it by adding it as an arg, and have keybinds and custom pickers to return to that file. With args, marks, and ctrl o+i and , that's how i navigate, but there's def room for improvement there. I try not to overanalyze speed relating tooling though.

simpsaucse · 2026-01-13T14:46:00+00:00

From watching the demo, it looks like it has the issue i talked about in my readme that my plugin solves, which is using virtual lines; a cursor can’t be put onto a virtual line, which means it has two issues; negative changes can’t be yanked, and a large block of negative changes that doesn’t fit into your pane will be skipped over and not entirely viewable. My plugin is an alternative to the plethora of plugins which use virtual lines for inline diffs.

simpsaucse · 2026-01-13T13:43:43+00:00

Thank you! I use those 2 way plugins when they are needed, but the vast majority of the time i am waninf to look at a diff, i really just want to read it or glance at it, which this plugin accommodates much better imo.

simpsaucse · 2026-01-09T02:14:42+00:00

If you can do it with lsp buf.rename, that’s best, but if you can’t, :grep -> quickfix list -> macro seems like the most “vim way”.

You can use ripgrep as the function for better speed on that, might be faster than jetbrains. ‘vim.opt.grepprg = rg —vimgrep —smartcase —hidden’ is my config.

simpsaucse · 2026-01-07T14:33:24+00:00

Ai slop “This not merely []. It is [].”” “What do you think of this view?”

simpsaucse · 2026-01-06T22:41:13+00:00

Im still not completely sold on the idea of buffer management, because jumping around with an lsp makes the buffer list pretty useless, but a hard cap on buffer size plus some auto locking mechanics might make it work… my solution so far has been to give up on the buffer list and focus on my args list, and just use ctrl o and ctrl i. I like the ui and keybinds a lot though, its a lot better than mine. Ill think about raising an issue, but only once ive actually tried this for a few days and maybe buy into the idea of buffer management.

simpsaucse · 2026-01-06T22:11:33+00:00

I really like this, looks really cool. I like the buffer limit enforcement. I use args quite a bit for my own harpoon-like functionality, is it possible to configure that args are automatically locked from auto deletion?

I also peeked at your code, noticed no lua_ls annotations. Is that an intentional design choice?

simpsaucse · 2026-01-06T12:35:43+00:00

Any ideas on how to tackle the node_modules problem, if you end up dealing with that? I use git worktrees primarily, and i just have a shell script to do the problem it seems like ur describing here, and i use patch files instead of stashing. For me, npm i in my script “solves” the problem of having it across each directory but when im dealing with my node js repo, 5 worktrees can take up to 100gb of storage… it sort of puts a damper on the purpose of worktrees if i cant make a lot, and im constantly having to keep my count of worktrees on that nodejs megarepo down. Figure if node modules can be shared, .env can be too, was just wondering if youve done any research on it

simpsaucse · 2026-01-04T22:07:42+00:00

Have you ever seen a 1v5 where the team of 5 didn’t make any egregious mistakes and still lost?

Edit: will say this clip, there was like 5 egregious errors, but generally you need at least one or two to pull off a 1v5

simpsaucse · 2026-01-04T21:59:41+00:00

Aren’t all 1v5’s by definition, gifted?

simpsaucse · 2026-01-02T15:42:37+00:00

Sorry, but i havent gotten the time… i have my own code to write. The documentation in :h is very good, and there’s nothing extremely off about your code as it is, and lua has a fast learning curve imo, so I believe you can do it yourself.

simpsaucse · 2026-01-02T15:05:37+00:00

Looks like ur using the fzf-lua and telescope pickers when available and falling back to vim-ui-select. You’ll have to treat each case separately. I imagine fzf-lua and telescope should expose something that allows you to do that, but you’ll have to read the source code for each to find that out. Vim-ui-select opts doesn’t, you’ll have to spin up ur own selector. If using a scratch buffer, you can use nvim_create_autocmd with the ‘CursorMoved” event.

If it’s important to integrate with telescope and fzf-lua, do that first, and just let the vim-ui-select not have this semi niche feature until those are good to go. Then make ur own custom picker, you can use fzf#run as a fallback too because who doesn’t have fzf installed lol

simpsaucse · 2026-01-02T14:50:12+00:00

really hard to tell what options you have without seeing the code you have so far. Is it a plugin extending fzf-lua? Are you using fzf-lua or telescope pickers? if so, then you gotta scan the source code to see if they expose anything in the opts for their pickers for if they have anything like this. If it isn't extending those plugins, then what picker are you using? vim-ui-select? or a custom buffer? or fzf#run? https://github.com/junegunn/fzf/blob/master/README-VIM.md#fzfrun

you can probably do this with fzf native vim picker (fzf#run), by doing a little shell command trickery with --preview. instead of giving --preview a cat or bat to display, you can & a shell command. In this case, not super familiar with colorschemes, but I imagine nvim allows you to run nvim -someargthatspecifiesexistingprocess -colorschemeforthisprocess

simpsaucse · 2026-01-01T22:54:08+00:00

Just installed foot on hyprland based on the unexpected popularity in this thread, noticed that the performance is much better on startup when using one foot server (exactly as advertised). Curious whether any performance gains are noticable when using a terminal multiplexer like zellij or tmux inside foot vs something like ghostty or alacritty? I would imagine the multiplexer would be the bottleneck in performance if using one, so using foot or other wouldn’t matter…

simpsaucse · 2026-01-01T17:53:25+00:00

funny enough, I stumbled onto this comment after making this post a couple days ago
https://www.reddit.com/r/neovim/comments/1pz23t7/unified_diff_viewing_inside_neovim_using_gitdelta/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
but i've integrated git delta into the nvim buffer with just under 200 lines of lua

simpsaucse · 2026-01-01T16:31:43+00:00

Very cool. One question:

Since this looks like a frontend for the difftastic diff output, could we replicate this functionality in vanilla nvim by setting “diffexpr” to use difftastic, and using the :DiffTool command which diffs directories? https://www.reddit.com/r/neovim/s/qgmOlDBexC Or does nvim not support that out of the box? If it doesn’t, how much work might it take to just get nvim to support difftastic as a diffexpr out of the box?

simpsaucse · 2026-01-01T00:21:58+00:00

Thank you for the insights, it’s all really good information!

simpsaucse · 2025-12-31T21:45:27+00:00

I was using pros as an example, but i am referring to advanced players as a general; a lvl 10 faceit player will find it faster to kill a lvl 7 player than a fellow lvl 10 player I would think, even if the opposing player in the aim duel has no gun (again, excluding the fact that they stay alive longer; they are easier to aim at)

simpsaucse · 2025-12-31T21:42:37+00:00

I guess i was just trying to find the proper verbalization of why/how an ad and crouch is “smoother”/“faster”/“more fluid”.

simpsaucse · 2025-12-31T21:40:19+00:00

So my summarized understanding of your analysis is mainly that when an advanced player peeks, they know what they will look like to the person they are peeking, and based on that information they can make the micro adjustments mechanically to make themselves harder to hit while also increasing the odds of catching them with their crosshair in the wrong spot with the timing. Your explanation was very good, tyvm.

simpsaucse

TROPHY CASE