From ArchWiki
Revision as of 19:30, 13 May 2010 by Gladstone (Talk | contribs) (Complementary applications: -- Link to the main Unclutter page)

Jump to: navigation, search

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n links end xmonad is a tiling window manager for X. Windows are arranged automatically to tile the screen without gaps or overlap, maximizing screen use. Window manager features are accessible from the keyboard: a mouse is optional.

xmonad is written, configured and extensible in Haskell. Custom layout algorithms, key bindings and other extensions may be written by the user in config files.

Layouts are applied dynamically, and different layouts may be used on each workspace. Xinerama is fully supported, allowing windows to be tiled on several physical screens.

For more information, please visit the xmonad website: http://xmonad.org/


xmonad is currently available in the community repo. A build for the current development snapshot (darcs) is in the aur. The following instructions are for xmonad-darcs, the development snapshot.

Development version (xmonad-darcs)

The xmonad-darcs development version can be installed from the AUR, with some additional dependencies in [community]. Install them in the following order:


Starting xmonad

To start xmonad automatically, simply add the command exec xmonad to your startup script (e.g. ~/.xinitrc). GDM and KDM users can create a new session file and then select xmonad from the appropriate Session menu.

Note: by default, xmonad does not set an X cursor, therefore the "cross" cursor is usually displayed which can be confusing for new users (thinking that xmonad has not launched correctly). To set the expected left-pointer, add the following to your startup file (e.g. ~/.xinitrc):

xsetroot -cursor_name left_ptr

Example .xinitrc :

 # set the cursor
 xsetroot -cursor_name left_ptr
 # start xmonad
 exec ck-launch-session xmonad

Configuring xmonad

xmonad users can modify, override or extend the default settings with the ~/.xmonad/xmonad.hs configuration file. Recompiling is done on the fly, with the Mod+q shortcut.

If you find you do not have a directory at ~/.xmonad, run xmonad --recompile to create it.

The "default config" for xmonad is quite usuable and it is achieved by simply running without an xmonad.hs entirely. Therefore, even after you run --recompile you will most likely not have an ~/.xmonad/xmonad.hs file. If you would like to start tweaking things, simply create the file and edit it as described below.

Because the xmonad configuration file is written in Haskell, non-programmers may have a difficult time adjusting settings. For detailed HOWTO's and example configs, we refer you to the following resources:

The best approach is to only place your changes and customizations in ~/.xmonad/xmonad.hs and write it such that any unset parameters are picked up from the built-in defaultConfig.

This is achieved by writing an xmonad.hs like this:

 import XMonad
   xmonad $ defaultConfig
     { terminal    = "urxvt"
     , modMask     = mod4Mask
     , borderWidth = 3

This simply overrides the default terminal and borderwidth while leaving all other settings at their defaults (inherited from the function defaultConfig).

As things get more complicated, it can be handy to call configuration options by function name inside the main function, and define these separately in their own sections of your xmonad.hs. This makes large customizations like your layout and manage hooks easier to visualize and maintain.

The above simple xmonad.hs could have been written like this:

 import XMonad
   xmonad $ defaultConfig
     { terminal    = myTerminal
     , modMask     = myModMask
     , borderWidth = myBorderWidth
 -- yes, these are functions; just very simple ones
 -- that accept no input and return static values
 myTerminal    = "urxvt"
 myModMask     = mod4Mask -- Win key or Super_L
 myBorderWidth = 3

Also, order at top level (main, myTerminal, myModMask etc.), or within the {} does not matter in Haskell, as long as imports come first.

The following is taken from the 0.9 config file template found here. It is an example of the most common functions one might want to define in their main do block.

   terminal           = myTerminal,
   focusFollowsMouse  = myFocusFollowsMouse,
   borderWidth        = myBorderWidth,
   modMask            = myModMask,
   -- numlockMask deprecated in 0.9.1
   -- numlockMask        = myNumlockMask,
   workspaces         = myWorkspaces,
   normalBorderColor  = myNormalBorderColor,
   focusedBorderColor = myFocusedBorderColor,

   -- key bindings
   keys               = myKeys,
   mouseBindings      = myMouseBindings,
   -- hooks, layouts
   layoutHook         = myLayout,
   manageHook         = myManageHook,
   handleEventHook    = myEventHook,
   logHook            = myLogHook,
   startupHook        = myStartupHook

Exiting xmonad

To end the current xmonad session, press Mod+SHIFT+q (Mod being ALT by default).

Tips and tricks

Complementary applications

There are number of complementary utilities that work well with xmonad. The most common of these include:

Making room for conky or tray apps

Wrap your layouts with avoidStruts from XMonad.Hooks.ManageDocks for automatic dock/panel/trayer spacing:

 import XMonad
 import XMonad.Hooks.ManageDocks
   xmonad $ defaultConfig
     { ...
     , layoutHook=avoidStruts $ Tall ||| Wide ||| Full
     , manageHook=manageHook defaultConfig <+> manageDocks
     , ...

If you ever want to toggle the gaps, this action can be added to your key bindings:

,((modMask x, xK_b     ), sendMessage ToggleStruts)

Using xmobar with xmonad

xmobar is a light and minimalistic text based bar, designed to work with xmonad.
To use xmobar with xmonad, you will need two packages in addition to the xmonad package, these are xmonad-contrib from [community] and xmobar or xmobar-darcs from aur.

Here we will start xmobar from within xmonad, which reloads xmobar whenever you reload xmonad.

Open up ~/.xmonad/xmonad.hs in your favorite editor, and choose one of the two following options:

Option 1: Quick, less flexible

Note: there is also a dzen which you can substitute for xmobar in either case.

Common imports:

import XMonad
import XMonad.Hooks.DynamicLog

The xmobar action starts xmobar and returns a modified config that includes all the options described in the xmonad:Option2: More configurable choice.

main=xmonad=<< xmobar myConfig
myConfig=defaultConfig { modMask=mod4Mask, -- or any other configurations here ... }

Option 2: More Configurable

As of xmonad(-contrib) 0.9, there is a new statusBar function in XMonad.Hooks.DynamicLog. It allows you to use your own configuration for:

  • The command used to execute the bar
  • The PP that determines what's being written to the bar
  • The keybinding to toggle the gap for the bar

Following is an example of how to use it: Template:File

Verify XMobar Config

The template and default xmobarrcs contains this.

At last, open up ~/.xmobarrc and make sure you got StdinReader in the template and run the plugin. E.g.


Now, all you should have to do is either to start, or restart xmonad.

Example configurations

Below are some example configurations from fellow xmonad users. Feel free to add links to your own.


GDM can not find xmonad

You can force GDM to launch xmonad by creating the file xmonad.desktop in the /usr/share/xsessions directory and add the contents:

[Desktop Entry]
Comment=This session starts xmonad

Now xmonad will show in your GDM session menu. Thanks to Santanu Chatterjee for the hint.

Missing xmonad-i386-linux

Xmonad should automatically create the xmonad-i386-linux file (in $HOME/.xmonad/). If this it not the case you can grab a cool looking config file from the xmonad wiki or create your own. Put the .hs and all others files in .xmonad/ and run the command from the folder:

xmonad --recompile

Now you should see the file.

Problems with Java applications

The standard Java gui toolkit has a hardcoded list of "non-reparenting" window managers. Since XMonad is not in that list, there can be some problems with running some java applications. One of the most common problems is "grey blobs", when the java application renders as a plain grey box instead of rendering the gui.

There is several thing that can help:

  • If you are using openjdk6, you can export _JAVA_AWT_WM_NONREPARENTING=1 .
  • If you are using Sun JRE/JDK, the best solution is usually to use SetWMName.

For more details about the problem, refer to the XMonad FAQ.

Other Resources

xmonad - The official xmonad website

xmonad.hs - Original xmonad.hs

xmonad: a guided tour

dzen - General purpose messaging and notification program

dmenu - Dynamic X menu for the quick launching of programs