shepherd: How to pair output of timer to the timer action?

[Tomas Volf]

Hello,

when I create a timer and it gets executed, I see the following in the
/var/log/message:

--8<---cut here---start->8---
Jan 25 20:19:00 localhost shepherd[1]: Timer 'outerr-1' spawned process 32137. 
Jan 25 20:19:00 localhost shepherd[1]: 
[srhm85lyjpqid63i4xyl7ynmvc4c76xz-with-mail-out] a 
Jan 25 20:19:00 localhost shepherd[1]: 
[srhm85lyjpqid63i4xyl7ynmvc4c76xz-with-mail-out] b 
Jan 25 20:19:00 localhost shepherd[1]: Process 32137 of timer 'outerr-1' 
terminated with status 0 after 0 seconds. 
--8<---cut here---end--->8---

The timer services is created by few layers of procedures, so I do not
really have a single definition to paste here, but that is not relevant.
The timer works and gets executed, so that part is fine.

What is unclear to me however is how can I tell (from the log) what
timer produced what output.  It tells me the PID of the timer process:

--8<---cut here---start->8---
Jan 25 20:19:00 localhost shepherd[1]: Timer 'outerr-1' spawned process 32137. 
--8<---cut here---end--->8---

Which is great, but this line does not reference it in any way:

--8<---cut here---start->8---
Jan 25 20:19:00 localhost shepherd[1]: 
[srhm85lyjpqid63i4xyl7ynmvc4c76xz-with-mail-out] a 
--8<---cut here---end--->8---

So I have two questions:

1. How to pair the timer output to the timer itself?

2. How to replace the (not really helpful) program name with a custom
   string (e.g. the timer name)?  It would be much more readable if the
   log line looked like this:

--8<---cut here---start->8---
Jan 25 20:19:00 localhost shepherd[1]: [outerr-1] a 
--8<---cut here---end--->8---

Thanks and have a nice day,
Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.


signature.asc
Description: PGP signature

Re: Using ibus input methods in Emacs GTK+

[宋文武]

Luis Felipe  writes:

> Hello,
>
> I upgraded my Guix system (currently on 17fadbb) and now I can type
> Japanese again (thanks, 宋文武). However, ibus input methods are
> working everywhere (GTK, GTK+, Qt) except in Emacs GTK+, which is
> unexpected because typing Japanese in Emacs used to just work before. 
> My current workaround is to start "emacs -nw" in a GNOME Console and
> then I can use ibus in it.
>
> I thought that maybe something in Emacs 28.x had changed, but trying
> on a Debian 12 machine, I can use ibus normally in Emacs GTK+ without
> configuring anything.
>
> If you're able to type Japanese (or use ibus input methods in general)
> in Emacs GTK+, did you have to do anything special?
>

Well, Emacs use XIM, so you need set 'XMODIFIERS=@im=ibus' and run
ibus-daemon with the "--xim" / "-x" argument.

Hope this helps!

Blind people unable to install Guix System

[宋文武]

Simen Endsjø  writes:

> It was brought to my attention that blind people runs into problems installing
> Guix System, while Debian and Arch have solved this better.
>
> The problem is outlined by the user k.g.roberts, ref
> :
>
>   The installer for Guix System 1.4.0 is basically the same as I remember 
> it from
>   a few years ago; boots almost immediately into an ncurses menu for 
> locale
>   selection and it takes another few screens to get to the option for a 
> shell. No
>   other assistive technologies built into the installer itself outside of 
> what’s
>   in the kernel, so a blind installation is doable over a remote 
> connection after
>   that point, but would likely be a hassle to get going without 
> additional help
>   from a sighted person.
>
> Dave Dude mention a solution, ref 
> :
>
>   They’d need to add a console screen reader, like Fenrir or ESpeakup to 
> the
>   installation image, then have something to type, on the boot command 
> line, to
>   start the reader. Debian has done this, on its installation images for 
> a long
>   time. Arch now does something like this, too. Thanks for looking into 
> this!
>
> I’m not the right person to do something like this, just thought I should 
> report
> it in case it’s easy to fix.

Hello, I CC this email to bug-guix to open an issue now.

Thank you for the report!

Re: shepherd: How to pair output of timer to the timer action?

[Felix Lechner via]

Hi Tomas,

On Sat, Jan 25 2025, Tomas Volf wrote:

> how can I tell (from the log) what timer produced what output

Yeah, I noticed that too but right now love timers too much to complain.
Ludo' may not subscribe here, so I copied them explicitly.

Kind regards
Felix