From e51a930c5c5a8609b8656bf997ec853cc04391e7 Mon Sep 17 00:00:00 2001
From: Tomas Volf <~@wolfsden.cz>
Date: Thu, 30 May 2024 20:29:53 +0200
Subject: services: xorg: Add startx-command-service-type.
* gnu/services/xorg.scm (startx-command-profile-service,
startx-command-service-type): New variables.
* doc/guix.texi (X Window): Document startx-command-service-type.
Change-Id: Ia2a7c3b2d5ebf6bcfff40cb2640b17d3baf6eba0
Signed-off-by: Arun Isaac <arunisaac@systemreboot.net>
---
doc/guix.texi | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
(limited to 'doc')
diff --git a/doc/guix.texi b/doc/guix.texi
index e59827d2bb..77521a3542 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -23627,9 +23627,11 @@ Usually the X server is started by a login manager.
Return a @code{startx} script in which the modules, fonts,
etc. specified in @var{config} are available. The result should be used
in place of @code{startx} and should be invoked by the user from a tty
-after login. Unlike @code{xorg-start-command}, this script calls
-xinit. Therefore it works well when executed from a tty. If you are
-using a desktop environment, you are unlikely to need this procedure.
+after login. Unlike @code{xorg-start-command}, this script calls xinit.
+Therefore it works well when executed from a tty. This script can be
+set up as @code{startx} using @code{startx-command-service-type}. If
+you are using a desktop environment, you are unlikely to need this
+procedure.
@end deffn
@@ -23691,6 +23693,14 @@ Whether to setup program as setuid binary.
@end deftp
+@defvar startx-command-service-type
+Add @command{startx} to the system profile putting it onto @env{PATH}.
+
+The value for this service is a @code{<xorg-configuration>} object which
+is passed to the @code{xorg-start-command-xinit} procedure producing the
+@command{startx} used. Default value is @code{(xorg-configuration)}.
+@end defvar
+
@node Printing Services
@subsection Printing Services
--
cgit v1.2.3