sendMessage to deal properly with windowset changes made
Add new library functions
Add support for GHC 8.6.x by providing an instance for ‘MonadFail X’. A side effect of that change is that our code no longer compiles with GHC versions prior to 8.0.x. We could work around that, no doubt, but the resulting code would require CPP and Cabal flags and whatnot. It feels more reasonable to just require a moderately recent compiler instead of going through all that trouble.
xmonad no longer always recompile on startup. Now it only does so if the
executable does not have the name that would be used for the compilation
output. The purpose of recompiling and executing the results in this case is
so that the
xmonad executable in the package can be used with custom
The state file that xmonad uses while restarting itself is now removed after it is processed. This fixes a bug that manifested in several different ways:
Recover old behavior (in 0.12) when
focusFollowsMouse == True:
the focus follows when the mouse enters another workspace
but not moving into any window.
Compiles with GHC 8.4.1
Restored compatability with GHC version prior to 8.0.1 by removing the dependency on directory version 1.2.3.
When restarting xmonad, resume state is no longer passed to the next process via the command line. Instead, a temporary state file is created and xmonad’s state is serialized to that file.
When upgrading to 0.13 from a previous version, the
command line option will automatically migrate to a state file.
This fixes issue #12.
You can now control which directory xmonad uses for finding your configuration file and which one is used for storing the compiled version of your configuration. In order of preference:
New environment variables. If you want to use these ensure you set the correct environment variable and also create the directory it references:
XDG Base Directory Specification directories, if they exist:
If none of these directories exist then one will be created using
the following logic: If the relevant environment variable
mentioned in step (1) above is set, the referent directory will be
created and used. Otherwise
~/.xmonad will be created and used.
A custom build script can be used when xmonad is given the
--recompile command line option. If an executable named
exists in the xmonad configuration directory it will be called
ghc. It takes one argument, the name of the
executable binary it must produce.
This fixes #8. (One of two possible custom build solutions. See the next entry for another solution.)
For users who build their xmonad configuration using tools such as cabal or stack, there is another option for executing xmonad.
Instead of running the
xmonad executable directly, arrange to
have your login manager run your configuration binary instead.
Then, in your binary, use the new
launch command instead of
This will keep xmonad from using its configuration file
checking/compiling code and directly start the window manager
execing any other binary.
See the documentation for the
launch function in
for more details.
Fixes #8. (Second way to have a custom build environment for XMonad. See previous entry for another solution.)
Compiles with GHC 7.10.2, 7.8.4, and 7.6.3
Use of data-default allows using
def where previously you
had to write
The setlocale package is now used instead of a binding shipped
with xmonad proper allowing the use of
Main.hs instead of
No longer encodes paths for
manageHook no longer floats Gimp windows
Doesn’t crash when there are fewer workspaces than screens
Query is now an instance of
Various improvements to the example configuration file