From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: paren@disroot.org, Andrew Tropin <andrew@trop.in>,
65343@debbugs.gnu.org, Brian Cully <bjc@spork.org>
Subject: [bug#65343] [PATCH] home: services: Add 'x11-display' service.
Date: Fri, 15 Sep 2023 01:39:10 +0300 [thread overview]
Message-ID: <87il8c2xdd.fsf@gmail.com> (raw)
In-Reply-To: <87msxo5w2x.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Thu, 14 Sep 2023 22:38:46 +0200")
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
[…]
> Now, without this service the situation is even worse: shepherd and its
> sub-processes inherit whatever ‘DISPLAY’ value was in its environment,
> if any, and that’s it. This service is a hack, but might still do more
> good than harm?
Inheriting environment variable is under the user's controll. Finding a
readable file by the user is less (requires to start x11 sessions in a
specific order). By more controll I mean the user could stop Shepherd on
a DISPLAY :0 and start it on DISPLAY :1 without stopping x11 sessions.
In any case, current patch with or without specification of files order
(or ‘herd start x11-display :42’) will change current behaviour. So, I
think a small entry in ‘news.scm’ could save somebody a day.
Regards,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2023-09-14 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 17:43 [bug#65343] [PATCH] home: services: Add 'x11-display' service Ludovic Courtès
2023-08-16 19:03 ` Oleg Pykhalov
2023-08-16 20:55 ` Brian Cully via Guix-patches via
2023-09-05 12:00 ` Andrew Tropin
2023-09-14 20:38 ` Ludovic Courtès
2023-09-14 22:39 ` Oleg Pykhalov [this message]
2023-10-20 21:09 ` [bug#65343] [PATCH v2] " Ludovic Courtès
2023-11-03 16:58 ` Oleg Pykhalov
2023-11-05 22:30 ` Ludovic Courtès
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=87il8c2xdd.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=65343@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=bjc@spork.org \
--cc=ludo@gnu.org \
--cc=paren@disroot.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).