Session configuration in xmonad under kdm
On Debian testing (Lenny), when I install the xmonad package I automatically get an "XMonad" item in the "Session type" menu on the kdm login screen. Nice! But how do I configure that session? It ignones my ~/.xsession. Thanks, Yitz
I wrote:
On Debian testing (Lenny), when I install the xmonad package I automatically get an "XMonad" item in the "Session type" menu on the kdm login screen. Nice! But how do I configure that session? It ignones my ~/.xsession.
OK, I see why. The Debian package supplies a file /usr/share/xsessions/xmonad.desktop containing the line: Exec=xmonad Instead, it should run a script that first sources xsession file(s) and then execs xmonad. I propose that: o the cross-platform standard name for this script should be "startxmonad" (/usr/bin/startxmonad on Debian). o the script should set SESSION_TYPE=xmonad so that xsession scripts can know that this is an xmonad session. o the script should first source /etc/xmonad/xsession, if it exists, then ~/.xsession if it exists. Debian bug submitted. Other platforms? Thanks, Yitz
Hi, I did not see any responses on this mail: Am Montag, den 02.06.2008, 13:54 +0300 schrieb Yitzchak Gale:
OK, I see why. The Debian package supplies a file /usr/share/xsessions/xmonad.desktop containing the line:
Exec=xmonad
Instead, it should run a script that first sources xsession file(s) and then execs xmonad.
I propose that:
o the cross-platform standard name for this script should be "startxmonad" (/usr/bin/startxmonad on Debian). o the script should set SESSION_TYPE=xmonad so that xsession scripts can know that this is an xmonad session. o the script should first source /etc/xmonad/xsession, if it exists, then ~/.xsession if it exists.
Debian bug submitted.
I’m willing to fix this in the debian package, but I’d prefer a non-debian-specific solution, so what do you think of this? Would you add a session script to the next release? Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
On Thu, Jun 05, 2008 at 09:36:05PM +0000, Joachim Breitner wrote:
Hi,
I did not see any responses on this mail:
Am Montag, den 02.06.2008, 13:54 +0300 schrieb Yitzchak Gale:
OK, I see why. The Debian package supplies a file /usr/share/xsessions/xmonad.desktop containing the line:
Exec=xmonad
Instead, it should run a script that first sources xsession file(s) and then execs xmonad.
I propose that:
o the cross-platform standard name for this script should be "startxmonad" (/usr/bin/startxmonad on Debian). o the script should set SESSION_TYPE=xmonad so that xsession scripts can know that this is an xmonad session. o the script should first source /etc/xmonad/xsession, if it exists, then ~/.xsession if it exists.
Debian bug submitted.
I’m willing to fix this in the debian package, but I’d prefer a non-debian-specific solution, so what do you think of this? Would you add a session script to the next release?
Thanks, Joachim
Sure, assuming that the 'startxmonad' script is sufficiently platform agnostic. Could we also provide the xmonad.desktop file? Are there any comments from the other distribution teams (Gentoo, Arch, etc.)? Cheers, Spencer Janssen
On Mon, Jun 02, 2008 at 11:57:00AM +0300, Yitzchak Gale wrote:
On Debian testing (Lenny), when I install the xmonad package I automatically get an "XMonad" item in the "Session type" menu on the kdm login screen. Nice!
But how do I configure that session? It ignones my ~/.xsession.
Thanks, Yitz
Is ~/.xsession the right place? I know that I start xmonad inside my .xsession, which is obviously a problem if we'd like to source it in a WM initialization routine. How do GNOME and KDE handle this? Cheers, Spencer Janssen
I wrote:
But how do I configure that session? It ignones my ~/.xsession.
Spencer Janssen wrote:
Is ~/.xsession the right place? I know that I start xmonad inside my .xsession, which is obviously a problem if we'd like to source it in a WM initialization routine. How do GNOME and KDE handle this?
The idea of this setup is that if you want to use xmonad both ways, your .xsession would test the SESSION_TYPE environment variable. (Maybe it should be X_SESSION_TYPE?) GNOME and KDE ignore the classic X startup conventions. Instead, there are various ways to configure how a session starts up that work with their more complex session management systems. We could do something similar for xmonad - have a "startup" script or subdirectory inside .xmonad, and then require that xmonad always start using startxmonad (except inside kde or gnome). It seems to me that you would then lose some of the feeling that xmonad is a simple window manager in the classic sense, not a "desktop environment" like gnome or kde. But it's a possibility. I do think that there should not be a major difference between a vanilla xmonad session started via kdm or gdm or startx. They all should use .xsession, or all use .xmonad/startup. Thanks, Yitz
participants (3)
-
Joachim Breitner -
Spencer Janssen -
Yitzchak Gale