utils-code/jesseduffield.lazygit
1
0
Fork 0
mirror of https://github.com/jesseduffield/lazygit.git synced 2026-09-10 07:36:27 -04:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Say newContentPending rather than resetOriginPending

Browse source 
resetOriginPending was the old name that we initially used, it has been
renamed to newContentPending meanwhile.
This commit is contained in:
Stefan Haller 2026-08-09 12:01:53 +02:00
parent db1734d0ff
commit 81ee437f3a
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
focused-main-view-production-plan.md
View file

@ -665,7 +665,7 @@ Commits:
first, then `swapIn()`, then set origin/selection** — this ordering is a
real invariant (reordering reintroduces flicker for buffer-parse; guarded
by `TestNewCmdTaskRestore`, N§20.5); the origin reset is now the manager's
`resetOriginPending` flag rather than a per-render field, and a restore
`newContentPending` flag rather than a per-render field, and a restore
takes precedence over it *and* clears it (PR 1 deviation 6);
**not cleared when a task starts** (survives
stop-and-replace by the periodic refresh), cleared in `Apply` (found or
@ -1161,7 +1161,7 @@ Log:
merging to master soon. Every later PR branches off its predecessor; nothing
is pushed, and fixup commits for earlier branches go on the tip of the stack
for the user to move down. Seven deviations from the plan are recorded in the
PR 1 section, of which two matter later: the manager's `resetOriginPending`
PR 1 section, of which two matter later: the manager's `newContentPending`
replaces the planned `LinesToRead.ResetOrigin` (PR 6's restore competes with
it and must clear it — deviation 6), and the
`screenColMax` gap fixed in PR 1 commit 9 is still live on the prototype