Actionless Loveless

i think you can start from the existing tests for low-level screenshot api as a starting point

or mb adding `examples` would be better, but here i myself not sure how it would be better to implement for examples

@poisson-aerohead yup, either tests or examples - both counted for coverage

idk, i was trying to look into your code but you have single-letter var names so i gave up, but good luck fixing it :)

leave short var names for either logically reasonable (like x, y coordinates, etc) or ones conventional for awesome API (c, s, cr, etc)

also please double-check what none of your helper functions is already implemented in `gears` standard library (particularly gears.filesystem)

> It seems that $HOME in the Xephyr environment is '/dev/null/' ```console tests/run.sh 16:export HOME=/dev/null 199: XDG_CONFIG_HOME="$build_dir" ```

> GitHub gives you allow you to test writing files on a virtual drive? better tmp dir - otherwise it would create mess when running it locally

`/tmp/awesome_test_screenshots_run2022_01_0213666`

if you not sure you can just push and try it yourself on GH actions - the code on merge will be squashed anyway, so extra commits wouldn't 'spam' the...