nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-11-01 15:11:25 +00:00
Code Issues Packages Projects Releases Wiki Activity
f41dc35387
nixpkgs/nixos/tests/xmonad.nix

48 lines
1.5 KiB
Nix
Raw Normal View History

nixosTests.xmonad: port to python
2019-11-07 02:18:26 +00:00
import ./make-test-python.nix ({ pkgs, ...} : {
Add XMonad test
2017-09-04 18:03:20 +00:00
name = "xmonad";
meta = with pkgs.stdenv.lib.maintainers; {
maintainers = [ nequissimus ];
};
nixos/displayManager: deprecate separate options for default wm/dm The upstream session files display managers use have no concept of sessions being composed from desktop manager and window manager. To be able to set upstream session files as default session, we need a single option. Having two different ways to set default session would be confusing, though, so we decided to deprecate the old method. We also created separate script for each session, just like we already had a separate desktop file for each one, and started using displayManager.sessionPackages mechanism to make the session handling more uniform.
2019-12-10 14:10:30 +00:00
machine = { pkgs, ... }: {
Add XMonad test
2017-09-04 18:03:20 +00:00
imports = [ ./common/x11.nix ./common/user-account.nix ];
nixos/display-managers/auto: remove This module allows root autoLogin, so we would break that for users, but they shouldn't be using it anyways. This gives the impression like auto is some special display manager, when it's just lightdm and special pam rules to allow root autoLogin. It was created for NixOS's testing so I believe this is where it belongs.
2020-01-26 22:41:19 +00:00
test-support.displayManager.auto.user = "alice";
nixos/displayManager: deprecate separate options for default wm/dm The upstream session files display managers use have no concept of sessions being composed from desktop manager and window manager. To be able to set upstream session files as default session, we need a single option. Having two different ways to set default session would be confusing, though, so we decided to deprecate the old method. We also created separate script for each session, just like we already had a separate desktop file for each one, and started using displayManager.sessionPackages mechanism to make the session handling more uniform.
2019-12-10 14:10:30 +00:00
services.xserver.displayManager.defaultSession = "none+xmonad";
Add XMonad test
2017-09-04 18:03:20 +00:00
services.xserver.windowManager.xmonad = {
enable = true;
enableContribAndExtras = true;
extraPackages = with pkgs.haskellPackages; haskellPackages: [ xmobar ];
xmonad service: add .config option
2018-11-28 22:08:20 +00:00
config = ''
import XMonad
nixosTests.xmonad: don't rely on xmonad being "vanilla" after restart The old (slightly broken) behavior of the xmonad module was to put the vanilla xmonad binary into PATH. This was changed to put the users xmonad into PATH instead. But since the config for the xmonad test uses `launch` (to avoid xmonads self-recompilation logic), it now can't handle the `--restart` flag anymore. So instead use a key binding for restarting, and let xmonad spawn a new xterm on restart. The key binding has to be explicitly added because the default binding will shell out to `xmonad --restart` and therefore not work with the `launch` entrypoint.
2020-10-10 20:33:45 +00:00
import XMonad.Operations (restart)
xmonad service: add .config option
2018-11-28 22:08:20 +00:00
import XMonad.Util.EZConfig
nixosTests.xmonad: don't rely on xmonad being "vanilla" after restart The old (slightly broken) behavior of the xmonad module was to put the vanilla xmonad binary into PATH. This was changed to put the users xmonad into PATH instead. But since the config for the xmonad test uses `launch` (to avoid xmonads self-recompilation logic), it now can't handle the `--restart` flag anymore. So instead use a key binding for restarting, and let xmonad spawn a new xterm on restart. The key binding has to be explicitly added because the default binding will shell out to `xmonad --restart` and therefore not work with the `launch` entrypoint.
2020-10-10 20:33:45 +00:00
import XMonad.Util.SessionStart
main = launch $ def { startupHook = startup } `additionalKeysP` myKeys
startup = isSessionStart >>= \sessInit ->
if sessInit then setSessionStarted else spawn "xterm"
myKeys = [ ("M-C-x", spawn "xterm"), ("M-q", restart "xmonad" True) ]
xmonad service: add .config option
2018-11-28 22:08:20 +00:00
'';
Add XMonad test
2017-09-04 18:03:20 +00:00
};
};
nixosTests.xmonad: port to python
2019-11-07 02:18:26 +00:00
testScript = { nodes, ... }: let
user = nodes.machine.config.users.users.alice;
in ''
machine.wait_for_x()
machine.wait_for_file("${user.home}/.Xauthority")
machine.succeed("xauth merge ${user.home}/.Xauthority")
nixosTests.xmonad: fix
2019-12-13 16:16:59 +00:00
machine.send_key("alt-ctrl-x")
nixosTests.xmonad: port to python
2019-11-07 02:18:26 +00:00
machine.wait_for_window("${user.name}.*machine")
machine.sleep(1)
nixosTests.xmonad: don't rely on xmonad being "vanilla" after restart The old (slightly broken) behavior of the xmonad module was to put the vanilla xmonad binary into PATH. This was changed to put the users xmonad into PATH instead. But since the config for the xmonad test uses `launch` (to avoid xmonads self-recompilation logic), it now can't handle the `--restart` flag anymore. So instead use a key binding for restarting, and let xmonad spawn a new xterm on restart. The key binding has to be explicitly added because the default binding will shell out to `xmonad --restart` and therefore not work with the `launch` entrypoint.
2020-10-10 20:33:45 +00:00
machine.screenshot("terminal1")
machine.send_key("alt-q")
nixosTests.xmonad: port to python
2019-11-07 02:18:26 +00:00
machine.sleep(3)
machine.wait_for_window("${user.name}.*machine")
machine.sleep(1)
nixosTests.xmonad: don't rely on xmonad being "vanilla" after restart The old (slightly broken) behavior of the xmonad module was to put the vanilla xmonad binary into PATH. This was changed to put the users xmonad into PATH instead. But since the config for the xmonad test uses `launch` (to avoid xmonads self-recompilation logic), it now can't handle the `--restart` flag anymore. So instead use a key binding for restarting, and let xmonad spawn a new xterm on restart. The key binding has to be explicitly added because the default binding will shell out to `xmonad --restart` and therefore not work with the `launch` entrypoint.
2020-10-10 20:33:45 +00:00
machine.screenshot("terminal2")
Add XMonad test
2017-09-04 18:03:20 +00:00
'';
})
Reference in New Issue Copy Permalink