https://todo.sr.ht/~mil/sxmo-tickets/331

---
 config.def.h | 1 +
 lisgd.c      | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/config.def.h b/config.def.h
index 76af153..d07f50d 100644
--- a/config.def.h
+++ b/config.def.h
@@ -22,6 +22,7 @@ double edgesizeright = 50.0;
 double edgesizebottom = 50.0;
 char *device = "/dev/input/touchscreen";
[message trimmed]

---
 USERGUIDE.md | 46 ++++++++++++++++++++++++++++++----------------
 1 file changed, 30 insertions(+), 16 deletions(-)

diff --git a/USERGUIDE.md b/USERGUIDE.md
index 9d96a7d..693aceb 100644
--- a/USERGUIDE.md
+++ b/USERGUIDE.md
@@ -199,13 +199,13 @@ If you are in a call, the length of the call will be display adjacent to the tit

 ## **Screen Lock**

-A custom application ([sxmo_screenlock](https://git.sr.ht/~mil/sxmo-utils/tree/master/programs/sxmo_screenlock.c))
-enables you to lock the screen so no tap events are processed. This application
[message trimmed]

I think mnc should only wake on cronjob that are mediated by
sxmo_rtcwake.sh , this way the user has control whether to run cronjobs:
 a) during crust only (sxmo_rtcwake.sh --strict)
 b) during normal operation only (no use of sxmo_rtcwake.sh)
 c) both crust and normal mode (via sxmo_rtcwake.sh)

This relies on the mnc patch I sent prior to this one, mnc reads from
stdin so we can handle the filter logic ourselves in our script.

---
 scripts/core/sxmo_screenlock.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/core/sxmo_screenlock.sh b/scripts/core/sxmo_screenlock.sh
[message trimmed]

This supersedes my earlier patch: https://lists.sr.ht/~mil/sxmo-devel/patches/24040

An extra patch for sxmo-utils will follow this one.

---
 README.md | 19 ++++++++++++++++---
 mnc.go    | 26 +++++++++++++-------------
 2 files changed, 29 insertions(+), 16 deletions(-)

diff --git a/README.md b/README.md
index f6fafa2..903650c 100644
--- a/README.md
+++ b/README.md
@@ -14,15 +14,28 @@ go build mnc.go
[message trimmed]

Thanks! Merged

--

Maarten van Gompel (proycon)
https://proycon.anaproy.nl

Merged!

--

Maarten van Gompel (proycon)
https://proycon.anaproy.nl

I merged this one now even though it's a bit too specific probably, it
prevents a very annoying bug. We can revise it to cover more
sound-outputing tools later.

--

Maarten van Gompel (proycon)
https://proycon.anaproy.nl

On 21-07-27 09:09, Stacy Harper wrote:
> We also have to remove them on outgoing call. We use find instead of rm
> with a wildcard cause wildcard look not expanded here.

Merged!

--

Maarten van Gompel (proycon)
https://proycon.anaproy.nl

On 21-07-29 05:44, Stacy Harper wrote:
> I am thinking:  Does mnc should not just read crontabs through the stdin
> pipe?
>
> It simplify the mnc code and make it easy for us to filter the crontab
> by ourself.

No it doesn't, and yes it should indeed :) That's precisely what I
suggested.

--

Maarten van Gompel (proycon)
https://proycon.anaproy.nl

I think mnc should only wake on cronjob that are mediated by
sxmo_rtcwake.sh , this way the user has control whether to run cronjobs:
 a) during crust only (sxmo_rtcwake.sh --strict)
 b) during normal operation only (no use of sxmo_rtcwake.sh)
 c) both crust and normal mode (via sxmo_rtcwake.sh)

I don't really know much Go so this patch can probably be done better,
ideally I'd say mnc shouldn't even run crontab -l at all but should just
accept input from stdin so we can pipe whatever we want to it and solve
this outside of mnc (keeping mnc more generic). If anyone else wants to
have a Go (pun intended ;) ) at it, please do..

---
 mnc.go | 2 +-
[message trimmed]