I posted an early version a month ago. I built zsweep because most Minesweeper
clones feel cluttered and require too much mouse movement. I wanted something
that felt like Monkeytype—clean, stats-heavy, and capable of being played
entirely with a keyboard (Vim style).
Hi HN, I built this because I wanted a standard way to tell my internal LLM
proxy which data is ephemeral and which can be saved. It's a draft spec (RFC),
and I've included fail-safe libraries for Go/Python. Would love feedback on the
header structure.
I primarily use lazygit for diff/patch editing as I'm preparing PRs so that commits are in a useful order for reviewers (at least those who choose to go commit-by-commit).
Aside from the fact that I've built workflows for lazygit related to patch editing, the main issue I'd have with `difi` is I use vim and won't use nvim (which should have the tagline "not vim", not "neo vim", because it's not vim in very important ways).
I will definitely try to integrate it with `delta`.
Now `difi` is enabling interactive feature when for letting user to see the changes directly inside editor with nvim plugins. `delta`'s outputs formatted ANSI text is also very interesting to integrate!
Now it defaults to comparing current branch vs `main` for PR review, but I will definitely see the value in a `local changes` mode for pre-commit checks!
The next step would be implement advanced vim motions.
Then refine the current UI and interface.
reply