# build runner: implement \-\-watch \(work-in-progress\) · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/bbd90a562efd6e802ed41df2649a05fad763a4de)

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

Visibility: public

Requested revision: bbd90a562efd6e802ed41df2649a05fad763a4de

Requested commit: bbd90a562efd6e802ed41df2649a05fad763a4de

Commit: bbd90a562efd6e802ed41df2649a05fad763a4de

Tree: c5276879ad6ade65af80393019ac649f9e6c1734

Author: Andrew Kelley

Committer: Andrew Kelley

## Message

```
build runner: implement --watch (work-in-progress)

I'm still learning how the fanotify API works but I think after playing
with it in this commit, I finally know how to implement it, at least on
Linux. This commit does not accomplish the goal but I want to take the
code in a different direction and still be able to reference this point
in time by viewing a source control diff.

I think the move is going to be saving the file_handle for the parent
directory, which combined with the dirent names is how we can correlate
the events back to the Step instances that have registered file system
inputs. I predict this to be similar to implementations on other
operating systems.

```

## Parents

- [deea36250ffe458d92b32b1ad090b8a958ba8082](https://git.cafe/gitcafe/zig/commit/deea36250ffe458d92b32b1ad090b8a958ba8082?format=markdown)

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