From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Proof of concept: Shepherd + DBus = ♥
Date: Mon, 06 Mar 2023 18:28:45 +0100 [thread overview]
Message-ID: <87v8jd7prm.fsf@gnu.org> (raw)
In-Reply-To: <7e1f52a58efd486263665e4346fa04fd4a01cae7.camel@gmail.com> (Liliana Marie Prikler's message of "Sat, 25 Feb 2023 20:34:09 +0100")
Hi!
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
[...]
>> > If you were naughty and didn't do the magic dance, you get a rather
>> > unhelpful result instead.
>> >
>> > $ herd getenv gnome PATH
>> >
>> > ;;; (reply #f "")
>>
>> This is super cool and super useful. Is there some way we could
>> achieve this (getenv/setenv in the GNOME Shell process) without
>> resorting to JS?
> Well, we could patch the Gnome Shell DBus API to expose getenv(s),
> setenv(ss) and unsetenv(s) – note the DBus method signature in
> brackets. As far as I'm aware, there is currently no such public API.
Maybe it’s worth trying. We could always submit that upstream.
>> Provided suitable Fibers integration, we could have services that
>> automatically start/stop based on some notification received on the
>> bus (devices plugged/unplugged, power or network condition changes,
>> etc.).
> Even better, we could (at some time) go full systemd and take control
> over all services spawned via DBus.
Yes!
Ludo’.
next prev parent reply other threads:[~2023-03-06 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:55 Proof of concept: Shepherd + DBus = ♥ Liliana Marie Prikler
2023-02-25 3:29 ` Maxim Cournoyer
2023-02-25 18:38 ` Ludovic Courtès
2023-02-25 19:34 ` Liliana Marie Prikler
2023-03-06 17:28 ` Ludovic Courtès [this message]
2023-04-11 13:44 ` Simon Tournier
2023-04-12 5:30 ` Liliana Marie Prikler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8jd7prm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).