From: "Ludovic Courtès" <ludo@gnu.org>
To: Runciter via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Runciter <runciter@whispers-vpn.org>
Subject: Re: Announcing shepherd-run
Date: Wed, 20 Nov 2024 22:24:31 +0100 [thread overview]
Message-ID: <87ed35wqcw.fsf@gnu.org> (raw)
In-Reply-To: <87v7wj5ek1.fsf@whispers-vpn.org> (Runciter via's message of "Wed, 20 Nov 2024 01:17:02 +0800")
Runciter via "Development of GNU Guix and the GNU System distribution."
<guix-devel@gnu.org> skribis:
> I actually think this is cool though, and the rest is mostly random
> thoughts now that I think about this problem: a herd-based minimalist
> alarm clock for production needs 2 features and must not include a third
> feature:
>
> * Repeat, but this is trivial to do with a script.
>
> * A heuristic to output sound at all costs, while trying hard to output
> through speakers and not headphones. This is harder, maybe not
> absolutely required; I suppose phones get it right but I'm not
> even sure.
>
> * A keystroke to stop the alarm from the X lock screen; surely the
> significant other will close their mind to the truth that this feature
> increases the attack surface and must not be included.
All good points! I’d like to have this, but I think it’s beyond the
scope of the ‘timer’ feature. :-)
Ludo’.
next prev parent reply other threads:[~2024-11-20 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 13:19 Announcing shepherd-run Efraim Flashner
2024-11-03 15:57 ` Denis 'GNUtoo' Carikli
2024-11-03 18:18 ` Efraim Flashner
2024-11-04 22:34 ` Ludovic Courtès
2024-11-05 10:59 ` Efraim Flashner
2024-11-09 22:48 ` Ludovic Courtès
2024-11-19 17:17 ` Runciter via Development of GNU Guix and the GNU System distribution.
2024-11-20 21:24 ` Ludovic Courtès [this message]
2024-11-21 18:58 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed35wqcw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=runciter@whispers-vpn.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.