From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: GDM update!
Date: Tue, 12 Feb 2019 15:13:29 +0100 [thread overview]
Message-ID: <87r2cdksc6.fsf@gnu.org> (raw)
In-Reply-To: <87y36mbav3.fsf@ngyro.com> (Timothy Sample's message of "Mon, 11 Feb 2019 10:31:12 -0500")
Hello!
Timothy Sample <samplet@ngyro.com> skribis:
> Maybe the GDM folks expect that we write a custom “.desktop” file that
> runs a custom script that checks for “~/.xsession” and runs it. It
> could use “TryExec” to figure out if “~/.xsession” exists, and offer it
> to the user (in the session selector) in that case. To be concrete, we
> would create a “user.desktop” session file with the following contents.
>
> [Desktop Entry]
> Name=User Session
> Comment=Start a user-defined session
> Exec=run-user-xsession
> TryExec=xsession-exists-p
> Icon=
> Type=Application
>
> Here, “run-user-xsession” and “xsession-exists-p” are custom scripts
> that we would write. If this file were somewhere that GDM knows about
> (e.g., “/run/current-system/profile/share/xsessions”), it should work.
We could do that, or should we just arrange for GDM to honor .xsession
when it exists just like we do for SLiM?
Specifically I’m thinking of the ‘xinitrd’ procedure in (gnu services
xorg) and how we pass it to SLiM via ‘slim.cfg’.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-02-12 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 22:30 GDM update! Ludovic Courtès
2019-02-11 13:30 ` Marco van Hulten
2019-02-11 14:39 ` Danny Milosavljevic
2019-02-11 15:31 ` Timothy Sample
2019-02-12 14:13 ` Ludovic Courtès [this message]
2019-02-12 15:39 ` Timothy Sample
2019-02-12 16:11 ` Pierre Neidhardt
2019-02-12 19:04 ` Timothy Sample
2019-02-11 14:43 ` Alex Griffin
2019-02-11 15:12 ` Timothy Sample
2019-02-12 14:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2cdksc6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.