Tanguy,

My apologies for not replying sooner.  I fail at managing the 
scarce free time I have these days.

Tanguy Le Carrour wrote:
>> Cooooool! :-)
>> Did you write the "much more snipped" by yourself?

I snipped some definitions for other services, like ibus-daemon 
and gpg-agent, because I haven't used them in a long time (didn't 
want to risk confusing anyone with code that might've bitrotted), 
and they don't add any new concepts to the emacs example.  It's 
more of the same.  You're not missing anything.

>> If yes, is it available somewhere? Else, is it documented 
>> somewhere?
>> Did you copy/paste it from another Guix file?

Only in my home directory :-)  No on-line dotfiles like the other 
cool kids.

I figured this much out on my own, but my use of the Shepherd's 
probably pretty basic.

Its manual isn't as far along as Guix's and, to be honest, didn't 
make much sense to me until *after* learning what I know from 
reading the code & good old trial and error.

> I've been playing with shepherd and service configurations and 
> it's
> actually easier than I thought it would be, at least for 
> "simple"
> services. Thanks for showing me the way! :-)
>
> I love it so much that I started/stopped the emacs service 
> (defined with
> the snippet above) a few times.

Hours of fun!  Happy to have helped.

> It works as expected, except for the `defunct` processes that 
> hang
> around.  Each time I run `herd stop emacs`, I get a new one, as 
> if
> shepherd could not forget about the dead process.  This doesn't
> prevent me from re-starting the process and using the service, 
> but
> it looks… messy!
>
> Am I doing something wrong?!

No, you're right, I'd simply never checked this before.  Stopping 
emacs gives me… Zombie emacs.  And mu.

Kind regards,

T G-R