Note that by omitting compiling dwm from source a great deal of customizability is lost, since dwm's entire configuration is performed by editing its source code. Taking this in mind, the rest of the article assumes that dwm has been compiled from source as explained in the entirety of this section.

+

{{note|By omitting compiling dwm from source a great deal of customizability is lost, since dwm's entire configuration is performed by editing its source code. Taking this in mind, the rest of the article assumes that dwm has been compiled from source as explained in the entirety of this section.}}

You will probably also want to consider installing [[dmenu]], a fast and lightweight dynamic menu for X:

You will probably also want to consider installing [[dmenu]], a fast and lightweight dynamic menu for X:

Line 22:

Line 23:

===Requirements===

===Requirements===

−

Basic programming tools present in {{package Official|base-devel}} are needed in order to compile dwm and build a package for it, and the {{package Official|abs}} package is also a requisite for fetching the necessary build scripts:

+

Basic programming tools present in {{Pkg|base-devel}} are needed in order to compile dwm and build a package for it, and the {{Pkg|abs}} package is also a requisite for fetching the necessary build scripts:

# pacman -S base-devel abs

# pacman -S base-devel abs

===Download build scripts with ABS===

===Download build scripts with ABS===

−

Once the required packages are installed, use ABS to fetch the latest build scripts from the repositories to the current directory:

+

Once the required packages are installed, use ABS to update and then copy the dwm build scripts from the ABS tree to a temporary directory. For example:

−

$ ABSROOT=. abs community/dwm

+

# abs community/dwm

+

$ cp -r /var/abs/community/dwm ~/dwm

===Build and install package===

===Build and install package===

−

Use {{Codeline|cd}} by switching to the directory containing the build scripts (the example above used {{Filename|~/dwm}}). Then run:

+

Use {{Ic|cd}} to switch to the directory containing the build scripts (the example above used {{ic|~/dwm}}). Then run:

$ makepkg -i

$ makepkg -i

This will compile dwm, build an Arch Linux package containing the resulting files, and install the package file all in one step. If problems are encountered, review the output for specific information.

This will compile dwm, build an Arch Linux package containing the resulting files, and install the package file all in one step. If problems are encountered, review the output for specific information.

−

{{Tip|If this directory ({{filename|~/dwm}}) is saved, it can subsequently be used for making changes to the default configuration.}}

+

{{Tip|If this directory ({{ic|~/dwm}}) is saved, it can subsequently be used for making changes to the default configuration.}}

==Configuring==

==Configuring==

−

dwm, as mentioned before, is exclusively configured at compile-time via some of its source files, namely {{Filename|config.h}} and {{Filename|config.mk}}. While the initial configuration provides a good set of defaults, it's realistic to expect that at some point potential users will probably want to make adjustments to their setups.

+

dwm, as mentioned before, is exclusively configured at compile-time via some of its source files, namely {{ic|config.h}} and {{ic|config.mk}}. While the initial configuration provides a good set of defaults, it is reasonable to expect eventual customization.

===Method 1: ABS rebuild (recommended)===

===Method 1: ABS rebuild (recommended)===

Line 44:

Line 46:

====Customizing config.h====

====Customizing config.h====

−

Browse to the dwm source code directory saved during the [[#Installing|installation process]]; {{filename|~/dwm}} in the example. The {{filename|config.h}} found within this directory is where the general dwm preferences are stored. Most settings within the file should be self-explanatory, while others may not share the same trait. For detailed information on these settings, see the [http://www.suckless.org/dwm/ dwm website].

+

Browse to the dwm source code directory saved during the [[#Installing|installation process]]; {{ic|~/dwm}} in the example. The {{ic|config.h}} found within this directory is where the general dwm preferences are stored. Most settings within the file should be self-explanatory. For detailed information on these settings, see the [http://dwm.suckless.org/ dwm website].

{{note|Be sure to make a backup copy of config.h before modifying it, just in case something goes wrong.}}

{{note|Be sure to make a backup copy of config.h before modifying it, just in case something goes wrong.}}

Line 60:

Line 62:

====Notes====

====Notes====

−

From now on, instead of updating the md5sums for every {{filename|config.h}} revision, which are known to become frequent, one may erase the md5sums array and build dwm with the {{codeline|--skipinteg}} option:

+

From now on, instead of updating the md5sums for every {{ic|config.h}} revision, which are known to become frequent, one may erase the md5sums array and build dwm with the {{Ic|--skipinteg}} option:

$ makepkg -efi --skipinteg

$ makepkg -efi --skipinteg

Line 66:

Line 68:

===Method 2: Mercurial (advanced)===

===Method 2: Mercurial (advanced)===

−

dwm is maintained upstream within a [http://www.selenic.com/mercurial/wiki/ Mercurial] version control system at [http://hg.suckless.org/dwm suckless.org]. Those already familiar with Mercurial may find it more convenient to maintain configurations and patches within this system. A [http://www.suckless.org/dwm/customisation/patch_queue.html detailed tutorial] on this method is available at the dwm website.

+

dwm is maintained upstream within a [http://www.selenic.com/mercurial/wiki/ Mercurial] version control system at [http://hg.suckless.org/dwm suckless.org]. Those already familiar with Mercurial may find it more convenient to maintain configurations and patches within this system. A [http://dwm.suckless.org/customisation/patch_queue detailed tutorial] on this method is available at the dwm website.

Before building dwm from the Mercurial sources, be sure to alter config.mk accordingly, because failure to do so may result in X crashes. Here are the values that need changing:

Before building dwm from the Mercurial sources, be sure to alter config.mk accordingly, because failure to do so may result in X crashes. Here are the values that need changing:

−

Modify {{codeline|PREFIX}}:

+

Modify {{Ic|PREFIX}}:

PREFIX = /usr

PREFIX = /usr

The X11 include folder:

The X11 include folder:

Line 78:

Line 80:

==Starting dwm==

==Starting dwm==

−

To start dwm with {{Codeline|startx}} or the [[SLIM]] login manager, simply append the following to {{Filename|~/.xinitrc}}:

+

To start dwm with {{Ic|startx}} or the [[SLIM]] login manager, simply append the following to {{ic|~/.xinitrc}}:

exec dwm

exec dwm

−

For [[GDM]], add it to {{Filename|~/.Xclients}} instead, and select "Run XClient Script" from the Sessions menu.

+

For [[GDM]], add it to {{ic|~/.Xclients}} instead, and select "Run XClient Script" from the Sessions menu.

+

+

===Starting a customized dwm from a display manager===

+

+

The default /usr/share/xsessions/dwm.desktop does not allow for a customized start like can be done in .xinitrc.

+

A solution to this problem is to make a start script, for example /usr/bin/dwm-personalized and make an alternative xsession .desktop file (/usr/share/xsessions/dwm-personalized.desktop).

+

+

Example of /usr/share/xsessions/dwm-personalized

+

<pre>[Desktop Entry]

+

Encoding=UTF-8

+

Name=Dwm-personalized

+

Comment=Dynamic window manager

+

Exec=dwm-personalized

+

Icon=dwm

+

Type=XSession

+

</pre>

+

+

Example of /usr/bin/dwm-personalized

+

+

<pre>#!/bin/zsh

+

+

#Set swedish keyboard map

+

setxkbmap se

+

+

#Set chrome as default browser

+

if [ -n "$DISPLAY" ]; then

+

BROWSER=google-chrome

+

fi

+

+

#Set status bar & start DWM

+

conky | while read -r; do xsetroot -name "$REPLY"; done &

+

exec dwm

+

</pre>

==Statusbar configuration==

==Statusbar configuration==

−

dwm uses the root window's name to display information in its statusbar, which can be changed with {{Codeline|xsetroot -name}}.

+

dwm uses the root window's name to display information in its statusbar, which can be changed with {{Ic|xsetroot -name}}.

===Basic statusbar===

===Basic statusbar===

−

This example prints the date in [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601] format. Add it to files {{filename|~/.xinitrc}} or {{filename|~/.Xclients}} or see this page's discussion for more details about the GDM-3 case :

+

This example prints the date in [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601] format. Add it to files {{ic|~/.xinitrc}} or {{ic|~/.Xclients}} or see this page's discussion for more details about the GDM-3 case :

<pre>

<pre>

while true; do

while true; do

Line 96:

Line 130:

</pre>

</pre>

−

Here is an example intended for laptops that depends on the {{Package Official|acpi}} package for showing battery information:

+

Here is an example intended for laptops that depends on the {{Pkg|acpi}} package for showing battery information:

<pre>

<pre>

while true ; do

while true ; do

−

xsetroot -name "$( acpi -b | awk '{ print $3, $4 }' | tr -d ',' )"

+

xsetroot -name "$(acpi -b | awk 'sub(/,/,"") {print $3, $4}')"

sleep 1m

sleep 1m

done &

done &

Line 130:

Line 164:

</pre>

</pre>

−

Finally, make sure there is only one instance of dwm in {{filename|~/.xinitrc}} or {{filename|~/.Xclients}}, so combining everything together should resemble this:

+

Finally, make sure there is only one instance of dwm in {{ic|~/.xinitrc}} or {{ic|~/.Xclients}}, so combining everything together should resemble this:

Conky can be printed to the statusbar with {{Codeline|xsetroot -name}}:

+

[[Conky]] can be printed to the statusbar with {{Ic|xsetroot -name}}:

conky | while read -r; do xsetroot -name "$REPLY"; done &

conky | while read -r; do xsetroot -name "$REPLY"; done &

exec dwm

exec dwm

Line 204:

Line 241:

===Patches & additional tiling modes===

===Patches & additional tiling modes===

−

The official website has a number of [http://www.suckless.org/dwm/patches patches] that can add extra functionality to dwm. Users can easily customize dwm by applying the modifications they like. The [http://www.suckless.org/dwm/patches/bottom_stack.html Bottom Stack] patch provides an additional tiling mode that splits the screen horizontally, as opposed to the default vertically oriented tiling mode. Similarly, bstack horizontal splits the tiles horizontally.

+

The official website has a number of [http://dwm.suckless.org/patches/ patches] that can add extra functionality to dwm. Users can easily customize dwm by applying the modifications they like. The [http://dwm.suckless.org/patches/bottom_stack Bottom Stack] patch provides an additional tiling mode that splits the screen horizontally, as opposed to the default vertically oriented tiling mode. Similarly, bstack horizontal splits the tiles horizontally.

The [http://dwm.suckless.org/patches/gapless_grid gaplessgrid patch] allows windows to be tiled like a grid.

The [http://dwm.suckless.org/patches/gapless_grid gaplessgrid patch] allows windows to be tiled like a grid.

Line 212:

Line 249:

===Fixing gaps around terminal windows===

===Fixing gaps around terminal windows===

−

If there are empty gaps of desktop space outside terminal windows, it is likely due to the terminal's font size. Either adjust the size until finding the ideal scale that closes the gap, or toggle {{Codeline|resizehints}} to ''False'' in {{filename|config.h}}:

+

If there are empty gaps of desktop space outside terminal windows, it is likely due to the terminal's font size. Either adjust the size until finding the ideal scale that closes the gap, or toggle {{Ic|resizehints}} to ''False'' in {{ic|config.h}}:

{{Out of date|layoutgaps.patch has been applied upstream in December 2011 and is no longer part of {{AUR|rxvt-unicode-patched}}. Solution below does not work for dwm-6.0 and rxvt-unicode-9.15. }}

Another choice for [[urxvt]] users is applying the [[urxvt#Fix maximized window gaps|hints patch]] and regressing to dwm's original behaviour:

Another choice for [[urxvt]] users is applying the [[urxvt#Fix maximized window gaps|hints patch]] and regressing to dwm's original behaviour:

static Bool resizehints = '''True''';

static Bool resizehints = '''True''';

Line 234:

Line 272:

dwm can now be restarted without destroying other X windows by pressing the usual Mod-Shift-Q combination.

dwm can now be restarted without destroying other X windows by pressing the usual Mod-Shift-Q combination.

−

It's a good idea to place the above startup script into a separate file, {{Filename|~/bin/startdwm}} for instance, and execute it through {{filename|~/.xinitrc}}. From this point on, when desiring to actually end the X session simply execute {{Codeline|killall startdwm}}, or bind it to a convenient key.

+

It is a good idea to place the above startup script into a separate file, {{ic|~/bin/startdwm}} for instance, and execute it through {{ic|~/.xinitrc}}. From this point on, when desiring to actually end the X session simply execute {{Ic|killall startdwm}}, or bind it to a convenient key.

===Make the right Alt key work as if it were Mod4 (Windows Key)===

===Make the right Alt key work as if it were Mod4 (Windows Key)===

−

When using Mod4 (aka Super/Windows Key) as the {{codeline|MODKEY}}, it may be equally convenient to have the right Alt key (Alt_R) act as Mod4. This will allow performing otherwise awkward keystrokes one-handed, such as zooming with Alt_R+Enter.

+

When using Mod4 (aka Super/Windows Key) as the {{Ic|MODKEY}}, it may be equally convenient to have the right Alt key (Alt_R) act as Mod4. This will allow performing otherwise awkward keystrokes one-handed, such as zooming with Alt_R+Enter.

First, find out which keycode is assigned to Alt_R:

First, find out which keycode is assigned to Alt_R:

xmodmap -pke | grep Alt_R

xmodmap -pke | grep Alt_R

−

Then simply add the following to the startup script (e.g. {{filename|~/.xinitrc}}), changing the keycode ''113'' if necessary to the result gathered by the previous {{codeline|xmodmap}} command:

+

Then simply add the following to the startup script (e.g. {{ic|~/.xinitrc}}), changing the keycode ''113'' if necessary to the result gathered by the previous {{Ic|xmodmap}} command:

xmodmap -e "keycode 113 = Super_L" # reassign Alt_R to Super_L

xmodmap -e "keycode 113 = Super_L" # reassign Alt_R to Super_L

xmodmap -e "remove mod1 = Super_L" # make sure X keeps it out of the mod1 group

xmodmap -e "remove mod1 = Super_L" # make sure X keeps it out of the mod1 group

Line 250:

Line 288:

To disable focus follows mouse behaviour comment out the following line in definiton of struct handler in dwm.c

To disable focus follows mouse behaviour comment out the following line in definiton of struct handler in dwm.c

<pre>[EnterNotify] = enternotify, </pre>

<pre>[EnterNotify] = enternotify, </pre>

+

Note that this change can cause some difficulties. After it the first click on inactive window will only bring the focus on it. To interact with window contents (buttons, fields etc) you need to click again. Also if you have several monitors you can notice that keyboard focus doesn't switch to another monitor activated by clicking.

===Adding custom keybinds/shortcuts===

===Adding custom keybinds/shortcuts===

−

Two entries are needed in {{filename|config.h}} to create custom keybinds. One under the "/* commands /*" section, and another under the "static Key keys[] = {" section.

+

Two entries are needed in {{ic|config.h}} to create custom keybinds. One under the "/* commands /*" section, and another under the "static Key keys[] = {" section.

Revision as of 22:45, 26 October 2012

dwm is a dynamic window manager for X. It manages windows in tiled, stacked, and full-screen layouts, as well as many others with the help of optional patches. Layouts can be applied dynamically, optimizing the environment for the application in use and the task performed. dwm is extremely lightweight and fast, written in C and with a stated design goal of remaining under 2000 source lines of code. It provides multi-head support for xrandr and Xinerama.

Installing

These instructions will install dwm using makepkg along with the Arch Build System, or ABS for short. This will allow reconfiguring it at a later time without complications. If only interested in installing dwm for a test drive, simply install the binary package from the repositories instead:

# pacman -S dwm

Note: By omitting compiling dwm from source a great deal of customizability is lost, since dwm's entire configuration is performed by editing its source code. Taking this in mind, the rest of the article assumes that dwm has been compiled from source as explained in the entirety of this section.

You will probably also want to consider installing dmenu, a fast and lightweight dynamic menu for X:

# pacman -S dmenu

Requirements

Basic programming tools present in base-devel are needed in order to compile dwm and build a package for it, and the abs package is also a requisite for fetching the necessary build scripts:

# pacman -S base-devel abs

Download build scripts with ABS

Once the required packages are installed, use ABS to update and then copy the dwm build scripts from the ABS tree to a temporary directory. For example:

# abs community/dwm
$ cp -r /var/abs/community/dwm ~/dwm

Build and install package

Use cd to switch to the directory containing the build scripts (the example above used ~/dwm). Then run:

$ makepkg -i

This will compile dwm, build an Arch Linux package containing the resulting files, and install the package file all in one step. If problems are encountered, review the output for specific information.

Tip: If this directory (~/dwm) is saved, it can subsequently be used for making changes to the default configuration.

Configuring

dwm, as mentioned before, is exclusively configured at compile-time via some of its source files, namely config.h and config.mk. While the initial configuration provides a good set of defaults, it is reasonable to expect eventual customization.

Method 1: ABS rebuild (recommended)

Modifying dwm is quite simple using this route.

Customizing config.h

Browse to the dwm source code directory saved during the installation process; ~/dwm in the example. The config.h found within this directory is where the general dwm preferences are stored. Most settings within the file should be self-explanatory. For detailed information on these settings, see the dwm website.

Note: Be sure to make a backup copy of config.h before modifying it, just in case something goes wrong.

Method 2: Mercurial (advanced)

dwm is maintained upstream within a Mercurial version control system at suckless.org. Those already familiar with Mercurial may find it more convenient to maintain configurations and patches within this system. A detailed tutorial on this method is available at the dwm website.

Before building dwm from the Mercurial sources, be sure to alter config.mk accordingly, because failure to do so may result in X crashes. Here are the values that need changing:

Modify PREFIX:

PREFIX = /usr

The X11 include folder:

X11INC = /usr/include/X11

And the the X11 lib directory:

X11LIB = /usr/lib/X11

Starting dwm

To start dwm with startx or the SLIM login manager, simply append the following to ~/.xinitrc:

exec dwm

For GDM, add it to ~/.Xclients instead, and select "Run XClient Script" from the Sessions menu.

Starting a customized dwm from a display manager

The default /usr/share/xsessions/dwm.desktop does not allow for a customized start like can be done in .xinitrc.
A solution to this problem is to make a start script, for example /usr/bin/dwm-personalized and make an alternative xsession .desktop file (/usr/share/xsessions/dwm-personalized.desktop).

Basic usage

Using dmenu

Dmenu is a useful addon to dwm. Rather than a standard list-style menu, it acts as a sort of autocomplete to typing in the names of binaries. It is more advanced than many program launchers and integrates well within dwm.

To start it, press Template:Keypress + Template:Keypress (Template:Keypress should be the Template:Keypress key by default). This can, of course, be changed if you so desire. Then, simply type in the first few characters of the binary you wish to run until you see it along the top bar. Then, simply use your left and right arrow keys to navigate to it and press enter.

Closing a window

Window layouts

By default, dwm will operate in tiled mode. This can be observed by new windows on the same tag growing smaller and smaller as new windows are opened. The windows will, together, take up the entire screen (except for the menu bar) at all times. There are, however, two other modes: floating and monocle. Floating mode should be familiar to users of non-tiling window managers; it allows users to rearrange windows as they please. Monocle mode will keep a single window visible at all times.

To switch to monocole mode, press Template:Keypress + Template:Keypress. To check if you are in monocle mode, you can see an M in square brackets (if no windows are open on that tag) or a number in square brackets (which corresponds with the number of windows open on that tag). Thus, a tag with no windows open would display this: [M], and a tag with 'n' windows open would display this: [n].

Exiting dwm

Extended usage

Patches & additional tiling modes

The official website has a number of patches that can add extra functionality to dwm. Users can easily customize dwm by applying the modifications they like. The Bottom Stack patch provides an additional tiling mode that splits the screen horizontally, as opposed to the default vertically oriented tiling mode. Similarly, bstack horizontal splits the tiles horizontally.

Enable one layout per tag

The default behaviour of dwm is to apply the currently selected layout for all tags.To have different layouts for different tags use the pertag patch.

Fixing gaps around terminal windows

If there are empty gaps of desktop space outside terminal windows, it is likely due to the terminal's font size. Either adjust the size until finding the ideal scale that closes the gap, or toggle resizehints to False in config.h:

This will cause dwm to ignore resize requests from all client windows, not just terminals. The downside to this workaround is that some terminals may suffer redraw anomalies, such as ghost lines and premature line wraps, among others.

Urxvt

This article or section is out of date.

Reason: layoutgaps.patch has been applied upstream in December 2011 and is no longer part of rxvt-unicode-patchedAUR. Solution below does not work for dwm-6.0 and rxvt-unicode-9.15. (Discuss in Talk:Dwm#)

Another choice for urxvt users is applying the hints patch and regressing to dwm's original behaviour:

static Bool resizehints = True;

Restart dwm without logging out or closing programs

For restarting dwm without logging out or closing applications, change or add a startup script so that it loads dwm in a while loop, like this:

dwm can now be restarted without destroying other X windows by pressing the usual Mod-Shift-Q combination.

It is a good idea to place the above startup script into a separate file, ~/bin/startdwm for instance, and execute it through ~/.xinitrc. From this point on, when desiring to actually end the X session simply execute killall startdwm, or bind it to a convenient key.

Make the right Alt key work as if it were Mod4 (Windows Key)

When using Mod4 (aka Super/Windows Key) as the MODKEY, it may be equally convenient to have the right Alt key (Alt_R) act as Mod4. This will allow performing otherwise awkward keystrokes one-handed, such as zooming with Alt_R+Enter.

First, find out which keycode is assigned to Alt_R:

xmodmap -pke | grep Alt_R

Then simply add the following to the startup script (e.g. ~/.xinitrc), changing the keycode 113 if necessary to the result gathered by the previous xmodmap command:

Now, any functions that are triggered by a Super_L (Windows) key press will also be triggered by an Alt_R key press.

Disable focus follows mouse behaviour

To disable focus follows mouse behaviour comment out the following line in definiton of struct handler in dwm.c

[EnterNotify] = enternotify,

Note that this change can cause some difficulties. After it the first click on inactive window will only bring the focus on it. To interact with window contents (buttons, fields etc) you need to click again. Also if you have several monitors you can notice that keyboard focus doesn't switch to another monitor activated by clicking.

Adding custom keybinds/shortcuts

Two entries are needed in config.h to create custom keybinds. One under the "/* commands /*" section, and another under the "static Key keys[] = {" section.

<keybindname> can be anything... <command> <-flags> and <arguments> can be anything but they have to be individually enclosed in "",

{ MODKEY, XK_<key>, spawn, {.v = <keybindname> } },

...would bind Mod+<key> to the command defined previously.

{ MODKEY|ShiftMask, XK_<key>, spawn, {.v = <keybindname> } },

...would bind Mod+Shift+<key> Use ControlMask for Ctrl key.

Single keys such as Fn or multimedia keys have to be bound with the hex codes obtainable from the program "xev"

{ 0, 0xff00, spawn, {.v = <keybindname> } },

...would bind foo key 0xff00 to <keybindname>

Fixing misbehaving Java applications

As of JRE 6u20, Java applications misbehave in dwm because it is not a known window manager to Java. This causes menus to close when the mouse is released, and other little issues. First, install wmname from the [community] repository:

# pacman -S wmname

Now all you have to do is use wmname to set a WM name that Java recognizes:

$ wmname LG3D

This is not permanent, so you may want to add this command to your .xinitrc.

It is also possible to change enable export _JAVA_AWT_WM_NONREPARENTING=1 in /etc/profile.d/jre.sh