From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Leo Famulari <leo@famulari.name>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Run graphical application in container
Date: Tue, 16 Oct 2018 20:25:17 +0200 [thread overview]
Message-ID: <87lg6xn3zm.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20181016161056.GA25057@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
Yes, that was it, thanks a lot!
Is anyone interested in finishing the work that was sketched in
https://lists.gnu.org/archive/html/help-guix/2018-01/msg00056.html ?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-10-16 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 14:22 Run graphical application in container Pierre Neidhardt
2018-10-16 16:10 ` Leo Famulari
2018-10-16 18:25 ` Pierre Neidhardt [this message]
2018-10-17 12:20 ` Ludovic Courtès
2020-07-01 20:17 ` Christopher Lemmer Webber
2020-07-01 20:42 ` Christopher Lemmer Webber
2020-07-01 20:57 ` Pierre Neidhardt
2020-07-01 21:53 ` zimoun
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=87lg6xn3zm.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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.
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).