lazygit

starred/lazygit

Fork 0

mirror of https://github.com/jesseduffield/lazygit.git synced 2026-10-05 21:46:49 -04:00

Files

T

History

Stefan HallerandClaude Opus 5 c9c6d00a47 Say what a diff command's output is for

Two things about a diff command follow from what its output is for: whether
the diff renderer produces it, and whether it is coloured. That was a
`plain` flag, which covers two of the three cases — the diff as configured,
and git's own uncoloured diff for building patches out of — and leaves no
room for the third, which is about to be needed: git's own diff, coloured,
for showing where the renderer's version of it can't be acted on.

So the flag becomes a mode. It also takes over deciding the colour, which
each command spelled out for itself, and it settles a question the flag
couldn't put: whether ignoring whitespace applies. It is about what the user
wants to see, so it holds for anything shown, and not for a diff a patch is
built from, which has to describe every change.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-10-05 11:20:31 +02:00

direnv

Offer direnv .envrc approval from inside lazygit

2026-06-04 09:05:01 +02:00

git_commands

Say what a diff command's output is for

2026-10-05 11:20:31 +02:00

git_config

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

hosting_service

Optimize regex compilations