commit 331b34f7c1aafc6ed036389f3e585e1d177071c5 parent 6ac9894d38b42ef44f5ea00e780c9b88d1048ce3 Author: zk <58356365+e-zk@users.noreply.github.com> Date: Mon, 7 Dec 2020 18:16:01 +1000 update readme Diffstat:
| M | README | | | 4 | ++-- |
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README b/README @@ -19,9 +19,9 @@ The following are some examples to illustrate how after can be useful (or not). Notify yourself when your build is done: - $ after -p 2027 -e "build is done!" + $ after -n gcc -e "build is done!" Put your machine to sleep after your updates are complete: - $ after -n pkg_add -e "doas zzz" | sh + $ after -p 2027 -e "doas zzz" | sh