# Project level git diff recalc handling · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/cede296b04d2717ca74fe212d89acef95c56a61e)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: cede296b04d2717ca74fe212d89acef95c56a61e

Requested commit: cede296b04d2717ca74fe212d89acef95c56a61e

Commit: cede296b04d2717ca74fe212d89acef95c56a61e

Tree: 3478db1ac60a7e6f6df0b341fca338db99f08ee3

Author: Julia

Committer: Julia

## Message

```
Project level git diff recalc handling

This avoids an issue where in a many-buffer multi-buffer, each modified
buffer could complete its recalc independently, causing a cascade of
repeated notifies

Now all recalcs started at the same time must complete before
 A: Starting another recalc pass
 B: The master notify occurring

Each buffer can still show its new diff if something else triggers it
to notify earlier, this is desirable and does not have the same negative
effects as the notify cascade as those re-layouts would need to happen
anyway

Co-Authored-By: Max Brunsfeld <max@zed.dev>

```

## Parents

- [54421b11f33ad4d27e49950da776025c0a608946](https://git.cafe/gitcafe/zed/commit/54421b11f33ad4d27e49950da776025c0a608946?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/cede296b04d2717ca74fe212d89acef95c56a61e?format=markdown)