This is slight change to the original implementation. This version
forces a recompile if XMonad detects a custom build script. The
previous version took into consideration the time stamps of the source
files.
For a custom build script, the source files may be located in another
location, or there could be dependencies unknown to XMonad. Better to
just always call the build script and let it work out if something
needs to be built.
The xmonadNoArgs function is now exposed as launch. This allows users
to start xmonad from a custom binary and skip the configuration
complication check. (This is related to issue #62.)
In order to make the new launch function easier to use, resume state
has been removed from the command line and is now stored in a
temporary file. As a bonus this fixes issue #12.
This commit also includes a method of migrating from older command
line state to the newer state file. This should allow you have an
older xmonad instance start a newer xmonad and maintain state.
Users can specify directory overrides via environment variables. If
those aren't set, xmonad now prefers XDG directories. If ~/.xmonad
exists and none of the others do, it will be used instead.
See: xmonad/xmonad#61
We need to make sure that the StackSet contains the right
position for the window at all times while dragging. Previously,
the window was only placed at a different position. If, for any
reason, a layout refresh happens while the window is being dragged,
then the window will jump back to the old position because the StackSet
still contains the position of the window where it was as the drag started.
This patch fixes that issue by calling float after each mouse movement, which
ensures that the position for the window is updated in the StackSet.
Fixes#63
This is a continuation of the work done by Adam Sjøgren (@asjo) to
resolve an issue where RGBA windows have transparent borders. It also
fixes bugs related to windows suddenly disappearing right before
xmonad calls getWindowAttributes.
For more information see xmonad/xmonad#9
Fix test failures on GHC 8 for `abort` and `new_abort` caused by `error`
appending the stack trace to the error message (since base
4.9.0.0)[1]. This fixes#36.
An alternative is to use `errorWithoutStackTrace` (new in base 4.9.0.0),
but this then requires use of CPP for backwards compatibility.
Remove type constraints prompting GHC to warn about redundant
constraints.
Tested with 7.6.3, 7.8.4, 7.10.3, 8.0.1 (all on NixOS).
[1] https://hackage.haskell.org/package/base-4.9.0.0/docs/GHC-Stack.html
