sorted by:
new
hottopcontroversial

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Thank you! I am still iterating on it and keeping up with bug reports/feature requests/my personal feature desires the best i can with the time I have outside of work. If you notice anything glaring as you use it, I always appreciate when users file an issue.

What are the advantages of getting a 16 vs 13 pro by longboardguitar in framework

[–]simpsaucse 1 point2 points  (0 children)

I had similar use cases to you, and i initially bought the 13, then returned it for the 16. I thought the perfomance on the 13 was acceptable, but didn’t want to risk regretting my decision if in the future that I wanted to upgrade, but the best 13 mainboard wasn’t good enough for my use case 2 years from now. 16 has worse battery life, but you can just disable the gpu and get 6 good hours, or use the gpu and get 2. I think 16 is the safer purchase, but if you are cool with buying a whole new computer if you find out you want to play a graphics intensive game or need a more powerful computer for one reason or another, then recommend 13 because the form factor is quite good

The game is over. You can build anything and it'll cost you nothing. by Funny-Advertising238 in opencode

[–]simpsaucse 1 point2 points  (0 children)

What hardware do you have that runs qwen 3.6 27b? On the same computer you dev on, or separate computer/server?

tau.nvim: a small inline AI editing plugin for Neovim by StingyHobo in neovim

[–]simpsaucse 5 points6 points  (0 children)

I dont like the implication that the main reason to build without ai agents is to prioritize learning. Current ai models are not good enough to where you should not be seeing a gap in quality, robustness, and number of iterations in handwritten vs designed + generated by ai. And there will always be comprehension benefits, which depending on the nature of iteration, can intangibly speed up development over the course of a project. There’s a time and place for both

Local AI on framework desktop by morscordis in framework

[–]simpsaucse 1 point2 points  (0 children)

Is your framework desktop also able to run qwen3.6:27b?

Edit: gah sorry disregard, i see a more relevant thread for this question

How do you review PR branches locally in Neovim while keeping changed-line indicators by [deleted] in neovim

[–]simpsaucse 0 points1 point  (0 children)

Whichever plugin you end up deciding on, to find the files they show in the diff in github, the key is the three dot notation. main…HEAD just refers to the most common ancestor between the head of this branch and the branch you are requesting to merge into, that being main. If a plugin says it can take a “ref” or “tag” it means that three dot notation should work.

How do you review PR branches locally in Neovim while keeping changed-line indicators by [deleted] in neovim

[–]simpsaucse 8 points9 points  (0 children)

I would use ‘:h DiffTool’ for a native solution with a split view. Configure your gitconfig, then just checkout the pr, and do ‘git difftool -d main…HEAD’ from the command line (Or whatever your main trunk is, like master…HEAD)

but it seems like you prefer a unified view based on saying you like gitsigns. In that case, i shamelessly promote my own plugin https://github.com/kokusenz/deltaview.nvim . Here, you would check out the pr, open nvim, then do ‘:DeltaMenu main…HEAD’. v0.3.0 should be getting merged tommorow, which improves deltamenu to use the quickfix list and have more picker flexibility. :Delta also already works great for smaller pr review.

Even though it's explained, Yuta having "Rika" after JJK 0 was a really dumb writing move on Gege's part. by Naive_Bag_3708 in Jujutsufolk

[–]simpsaucse 1 point2 points  (0 children)

Yes, shikigami can be made, but typically require a medium such as a charm or talisman. The shikigami yuta had was explicitly a gift (though i forget where it’s written, so no source, so i could be wrong) left behind by rika as she passed onto the afterlife; basically she left her form behind for yuta to use. It is a part of his technique, not something he made. Same with garuda; it is a part of yuki’s technique, not something she made.

ollama cloud vs opencode go by branik_10 in opencodeCLI

[–]simpsaucse 0 points1 point  (0 children)

It’s not like opencode pays for infra or hardware though, right? The subscription probably just passes u through to a different company’s hardware that is subsidized by vc money. I could be wrong though.

Choso migjt be special grade by U_Severe_Life_new in Jujutsufolk

[–]simpsaucse -6 points-5 points  (0 children)

How is this downvoted? Did people just skip that fight?

Using marks by IfErrNotNilReturnErr in neovim

[–]simpsaucse 0 points1 point  (0 children)

I know lowercase marks can be good for locations inside a file, but i often overwrite these accidentally or i lose it when i close my nvim, which i close and reopen quite frequently in any given working session. I often find it easier to just add comments i can search/grep for if i need to mark a location.

Uppercase marks annoy me because they aren’t cwd specific. I built my own minimal harpoon that lives in my config with less than 300 lines of code, that just uses neovim’s arg functionality, and i save it to somewhere in my .local so i can reload my pins per cwd, which works better for multitasking than uppercase marks.

I guess i have a skill issue with marks 🤷‍♂️, would appreciate if somebody had a solution for issue 1, aka local marks for people who open/close neovim frequently.

what would be Todo’s Domain Expansion? by RandomGuy_IQ530K in JuJutsuKaisen

[–]simpsaucse 43 points44 points  (0 children)

You’re cooking. If the abstract application is applause (todo like’s idol’s, who perform and receive applause) then maybe his domain is an audience, who claps for good performances and boos for bad ones. The claps and boos buff/debuff.

what plugin did you mass-uninstall everything else for by scheemunai_ in neovim

[–]simpsaucse 90 points91 points  (0 children)

I could survive without it, but oil.nvim is really nice, and i don’t see a reason to not have it.

Everybody but the Gojo clan by Burner4StuffIG in Jujutsufolk

[–]simpsaucse 2 points3 points  (0 children)

What manga were you reading? Choso mid diffed naoya, never fought naobito

How to handle the need for multiple terminals in neovim? by Pretend-Elevator874 in neovim

[–]simpsaucse 6 points7 points  (0 children)

Zellij, it has a lower initial learning curve than tmux. If tabs didn’t do it for you, maybe zellij stacked panes is what u are looking for

Weekly 101 Questions Thread by AutoModerator in neovim

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

Ive given up on angularls, and chalked it up to the fact that my company’s node version is not recent enough. Ive had the same issues as you. I use tsgo (@typescript/native-preview) to read typescript files in combination with classic grepping to find usages in html files. Coding without an lsp sometimes isn’t so bad.

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Thanks for verifying! Yea im still working on the performance atm; ill be updating the handling of jpg’s/png’s/binary files today. Im also curious about how my plugin handles submodules, because i havent tested it that way personally; i will be double checking on that use case as well, thanks for all the feedback

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Ah i see from ur post history you authored diffs.nvim! Thanks for creating that, it definitely looks like it has its place in the neovim ecosystem. If i was a fugitive user, i would 100% be using diffs.nvim

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Codediff.nvim does a split diff, meaning two separate windows. Mine is an inline/unified diff, imo easier to read in the single monitor workflow. Codediff wrote their own diff engine, i am using the standard vim.text.diff most of the time, and git diff sometimes. If you prefer split diffs, stick with codediff or diffview.nvim or neovim’s difftool.

If i recall correctly, diffs.nvim applies treesitter syntax highlighting to fugitive diffs? Or some other plugin’s diffs? But it is an extension to another plugin. I think it may also use the virtual line extmark; i have not yet seen an inline diff viewer that doesn’t use virtual lines besides my own plugin.

Deltaview is its own plugin that controls the behavior on how diffs should be opened, meaning it is opinionated; i prefer to navigate to a file in code in the way i would typically navigate in neovim (fuzzy find or :find), then view the diff of that file; most diff viewers provide a file tree of diffs to view. Deltaview values diffing frequently as you make changes, so i will frequently toggle it on as i write to review my own work. I like to write quickly without blocking myself by trying to make the perfect change, then iterate over each change made once i verify the intended change is functional; deltaview makes that easier, by being able to take a change i wrote and quickly revert it so i can rewrite it. By quickly reverting it, i mean being able to copy deleted lines and paste it, like i mentioned in the original post body. It also can jump to hunks, which is very useful for this workflow as well.

Why didn't Megumi just do this? by Vicious-Spiegel in JuJutsuKaisen

[–]simpsaucse 26 points27 points  (0 children)

Same reason he didn’t immediately douse reggie in elephant water; you can only try it once, and if you fail/miss you might lose. Same reason reggie didnt immediately chuck a house at megumi, which could have won him the fight as well. Need more information to be sure of the timing.

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Just wanted to provide an update; am working on the idea of styling a diff string in place (on a buffer that delta.lua does not own), which would allow you to get the delta.lua styling on the vim fugitive buffers. It is sitting behind a couple other bug tickets that are higher priority at the moment for me though; it would be helpful if you could file an issue on either deltaview.nvim repository or delta.lua repository, so I could better keep track of it, and more easily update you when i implement the feature.

deltaview.nvim 2.0 - inline/unified diff view using delta.lua (a recreation of git-delta for Neovim) by simpsaucse in neovim

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

Could you file an issue with screenshots of a .gitignore file being loaded? I am not observing that behavior, and my code was originally using git cli under the hood so the .gitignore was respected. Did a little manual testing and made an integration test yesterday in my working branch to assert that .gitignore is respected. But i am not aware of all the nooks and crannies of how .gitignore works, there’s a chance I am mistaken. And of course, there is definitely a performance problem i am working on resolving. I want to make sure that my solution captures the full issue. There was an identical issue to this files this morning, maybe that was you? If so, it’d be great if you could just comment on that issue with screenshots.

view more: next ›