RWind - The Racket Window Manager
An extensible window manager written in the Racket programming language, meant to be highly customizable.
There is an RWind mailing list.
First some warnings:
- Backward compatibility will not be ensured in the 0.x branch.
- Due to a security issue in the server, the current version should not be used on multiple user computers, unless the server is disabled. Use at your own risk.
- Stacking and tiling support
- Client command line (repl)
- Customization of key bindings and mouse bindings
- Workspaces with two modes:
- single mode: one workspace over all monitors
- multi mode: one workspace per monitor
- Xinerama and RandR support
- Currently little ICCCM/EWMH compliance
All these features are in development stage.
Installation & quick start
1) Install Racket
Currently, you will need the latest version of Racket.
2) Install RWind
raco pkg install rwind
raco is provided with Racket, so it should be in your path)
It will ask you if you want to install
x11. You should say yes as RWind cannot work without this library.
3) Configure RWind
racket -l rwind/configure
And follow the instructions.
This creates a default RWind configuration file, then it asks you to choose
between a session manager or a
If you choose a session manager configuration, it will abort and you will need to re-type the above command preceded by
These two steps are required because the first configuration files must be owned by the user.
You can reconfigure RWind at any time.
4) Start RWind
a) If you chose a session configuration, go back to the login screen. You should now see RWind in the login options.
b) If you chose a xinit/startx configuration, in a virtual terminal (
Ctrl-Alt-F1), type the following:
xinit .xinitrc-rwind -- :1 &
You may need to modify the display
:2 for example if
:1 is not
available. The default
.xinitrc-rwind is a simple example file that you may want to edit to fit your needs.
By default, you need to close the xterms to exit the session.
Default configuration and customization
Upon configuration, the file
config.rkt was created.
This is where all the RWind customization is done.
By default, you can open this file within RWind by pressing
(this can also be changed in the configuration file).
Take a look at this file to know what keybindings are defined.
You can also of course add you own keybindings.
The default window policy is stacking (as for most traditional window managers),
but you can easily change it to tiling in the configuration file.
With the tiling policy, several layouts are possible (mainly
To choose a layout, specify so in the file:
(current-policy (new policy-tiling% [layout 'dwindle]))
If you edit the configuration file, you will need to restart RWind to take the changes into account, probably by pressing the keybinding as defined in this very file. You don't need to recompile RWind, just restart it.
The client is a console where you can evaluate Racket expressions and communicate with the window manager. It can be opened in a terminal with:
racket -l rwind/client
For example, place the mouse pointer on a window and type in the console:
> (window-name (pointer-window))
> (move-window (pointer-window) 10 40)
The list of available symbols provided by RWind is given by:
All bindings of
#lang racket are available too.
You can get help on a known identifier with:
> (describe 'focus-window)
You can search among the list of identifiers with:
> (search-identifiers "window")
You can get the list of existing layouts for the tiling policy:
> (policy. get-layouts)
The layout can be changed immediately:
> (policy. set-layout 'dwindle)
Each workspace can have its own layout:
> (policy. set-workspace-layout 'uniform)
To reset the layout of a workspace to the default one:
> (policy. reset-workspace-layout)
RWind has some dependencies, in particular the X11 FFI bindings,
that will probably need to be updated with RWind.
To do this automatically, specify the
--auto option to
raco update --auto rwind
Your RWind configurations file will not be modified by the update.
This also means that any new feature that may appear in the new versions of these files
will not be added to your files.
You can reconfigure RWind, and you will be asked if you want to replace the existing
Because RWind heavily relies on the X11 collection, a large part of the debugging happens an the interface between the two.
Create symbolic links to the scripts
user-files/rwind-debug in your home directory.
Compile rwind and x11 in debug mode with
$ user-files/compile-rwind debug. Basically, it removes all previous compilations of the two collections and compiles it with some flags.
Finally, start RWind from a non-X terminal (say, Ctrl-Alt-F1):
xinit .xinitrc-rwind-debug -- :2 &
Then all error messages are redirected to
You should see lines starting with "RW:", and lines starting with " X:" (for the X11 lib).
You can also track the error messages from within RWind with
tail -f ~/rwind.log.