display which file triggered the re-run

[marcospb19]

A draft to address #438.

What it looks like (at the time of writing):

TODO:

• Pressing F5 wrongly shows the last triggered path instead, instead of "computing..."

[Canop]

counting bytes isn't the right way to know if a string should be shortened. Even counting chars is wrong, as some may be double width. And you can't shorten a string at any arbitrary byte, or the UTF8 might be invalid.

But there are proper utilities in bacon do display strings while taking care of the available size. Look for calls to write_composite_fill in bacon (the last argument can be Center).

[Canop]

I don't think this is the right approach to debug bacon. You may have much more to display and you can't always write this info in bacon itself.

You should use the log: launch bacon with BACON_LOG=debug bacon (or BACON_LOG=debug cargo run -- path/to/project if you're in the bacon project dir. Then display the log with tail -f bacon.log in another terminal. You'll see for example that the path triggering the recompute is logged, as well as some ignoring related info. And you can of course, to find the problem, add more debug! and info! in the code.

[marcospb19]

You should use the log: ...

Sounds great, thanks! I couldn't find that in the docs, so I'll pass my eyes on it again later to see if I just missed it, or if I can make a PR to improve it.

[Canop]

You're right, it's missing in the doc.

It should be in this page: https://dystroy.org/bacon/community/bacon-dev/

And it should be similar to what I've written for another program: https://dystroy.org/broot/community/#log

[Canop]

Actually, logging is mentioned: http://localhost:8004/community/bacon-dev/#issues