Skip to content

Latest commit

 

History

History
63 lines (45 loc) · 2.45 KB

README.md

File metadata and controls

63 lines (45 loc) · 2.45 KB

My Xmonad configuration

This is rather simple Xmonad configuration with KDE integration which would also work standalone.

Inspiration

Primary source of information for Xmonad KDE integration:

Moreover this configuration is based on the following examples:

Quick setup

Install Xmonad and clone this repository into ~/.xmonad directory:

$ git clone https://github.com/marbu/xmonad.git ~/.xmonad

KDE 4

$ mkdir -p ~/.kde/env
$ echo 'KDEWM=/usr/bin/xmonad' > ~/.kde/env/set_window_manager.sh

Note: runner (in KDE triggered via alt-f2) is binded to meta-p as expected, but you should configure it to use floating mode (otherwise the input line loses focus and you are not able to type anything in it). This is a reported bug of xmonad-contrib.

KDE 5 Plasma Workspace

Compared to KDE 4, the only difference is the location of configuration files:

$ mkdir -p ~/.config/plasma-workspace/env
$ echo 'export KDEWM=/usr/bin/xmonad' > ~/.config/plasma-workspace/env/set_window_manager.sh

Note: Plasma now uses meta key in some default keybindings (eg. meta-tab is catched by Plasma and not Xmonad) which needs to be reconfigured.

Unfortunatelly, there are few new issues compared to KDE 4 with xmonad:

  • KDE Bug 351141 fixed in Plasma 5.8
  • KDE Bug 351706
  • multiple screens mess with window placement (most of windows from multiple virtual desktops end up on single virt. desktop when screen is connected or disconnected) and this may be a consequence of new KDE 5 feature which maintains separate desktop configuration when new screen is attached (further investigation needed)