From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>,
Mark H Weaver <mhw@netris.org>,
47458@debbugs.gnu.org
Subject: bug#47458: Terrible UX upgrading Emacs in Guix
Date: Mon, 29 Mar 2021 10:43:22 +0200 [thread overview]
Message-ID: <cbd14e7fe65ca52ad07557ae58f30dc55b6aef4b.camel@student.tugraz.at> (raw)
In-Reply-To: <48be53a43407c9a298bc1abe798f7744a07ed9fa.camel@telenet.be>
Am Montag, den 29.03.2021, 10:24 +0200 schrieb Maxime Devos:
> On Mon, 2021-03-29 at 10:07 +0200, Leo Prikler wrote:
> > [...]
> >
> > In a similar manner, if I see an Emacs version upgrade at the start
> > of
> > the transaction, I already know to prepare for a little environment
> > variable dance to get it to start correctly. I think there has
> > been an
> > idea to update environment variables in GNOME Shell directly, for
> > instance, but
> > a. we're lacking the technology to do so at the moment (e.g. guile-
> > dbus)
>
> Actually, we do have dbus bindings for guile (actually, a
> reimplementation
> of dbus in (Guile) Scheme): guile-ac-d-bus. It doesn't support file
> descriptor
> passing (at least on Guile, other Schemes may differ) though, but
> that's
> probably not required for this.
Thanks for pointing this out! Now I can finally write Guile code to
update all those environment variables. (Hopefully this lets us do
polkit in Guix as well.)
next prev parent reply other threads:[~2021-03-29 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 2:02 bug#47458: Terrible UX upgrading Emacs in Guix Mark H Weaver
2021-03-29 8:07 ` Leo Prikler
2021-03-29 8:24 ` Maxime Devos
2021-03-29 8:43 ` Leo Prikler [this message]
[not found] ` <20210330184101.7643-1-leo.prikler@student.tugraz.at>
2021-04-04 4:35 ` Maxim Cournoyer
2021-04-04 7:49 ` Leo Prikler
2021-04-06 12:09 ` Maxim Cournoyer
2021-04-06 15:49 ` Leo Prikler
2021-04-07 19:46 ` Maxim Cournoyer
2021-05-20 13:24 ` Maxim Cournoyer
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=cbd14e7fe65ca52ad07557ae58f30dc55b6aef4b.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=47458@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=mhw@netris.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 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).