At least one of the instructions spans multiple paragraphs, which makes
it difficult to make out when this kind of interlude ends and the rest
of the text picks back up. Introducing separators, while slightly
visually jarring, solves this problem. As such, make sure that these
sections are reasonably far apart and group ones that are close
together.
* Avoid mangling unused parts of pkgs.haskell in `fromHOL`.
* Create 'defComp', specifying the default compiler, customisable
through ./comp.nix.
* Include `modernise` module as a workaround for NIX_GHC -> XMONAD_GHC.
.gitignore:
* Include nix 'result' symlink.
Users often mistakenly use className to query the application (resource)
name of a window; probably since WM_CLASS even has "class" in its name,
so confusion ensues. Improve the documentation to explicitly state
which of the two strings in WM_CLASS the respective functions match.
As advised in [1], provide a way to set the path for the xmessage and
ghc binaries via XMONAD_XMESSAGE and XMONAD_GHC environment variables.
[1]: 36d5761b3e
This reverts commit 29475fa7f8.
xmonad/xmonad-contrib#731 fixes the WindowNavigation issue with alpha
channels, so we can re-enable alpha support. A subsequent commit will
bump versions/dependencies to keep things in sync, although strictly
speaking that's not necessary here.
As discussed in #401, while hlint complains on a definition like
(<||>) x y = ifM x (pure True) y
because it could be eta reduced, actually doing that and writing
(<||>) x = ifM x (pure True)
feels a bit awkward. The solution is to always actually define these
kinds of infix operators in an infix way; i.e., we write
x <||> y = ifM x (pure True) y
instead. For the sake of consistency, it now seems prudent to define
all infix operators in this way (with exceptions for literal aliases,
like `(<+>) = mappend`).
Related: https://github.com/xmonad/xmonad/pull/401
This reverts commit c537a0658a.
A discussion of why, as well as a new way forward, in being discussed in
https://github.com/xmonad/xmonad/issues/395
However, since we would like to release a new minor version soon-ish,
it's better to revert this for now.
Fixes: e5a258f19c ("Revert "Merge pull request #350 from Thiago4532/opaque-window-border"")
This reverts commit dbe9c4f799, reversing
changes made to f6e4e278b5.
A discussion of why, as well as a new way forward, in being discussed in
https://github.com/xmonad/xmonad/issues/395
However, since we would like to release a new minor version soon-ish,
it's better to revert this for now.
Single-commit pull requests are discouraged by the core team now, so
drop that section and just refer to cbeams a kernel docs instead.
Related: https://github.com/xmonad/xmonad/issues/341
On IRC an issue came up where a user couldn't press M-] since they were
using a German keyboard layout and ] is put behind some AltGr
combination. The correct way to specify that would be something along
the lines of M-M5-9, but we don't really want to go into that in the
tutorial. Thus, only use the obvious modifiers, as well as letters,
which should work on every layout.
So far, some functions like focus{Up,Down} and swap{Up,Down} had
combined Haddock comments, since giving each their own would result in
some duplication of information. This is nicer when reading the source,
but Haddock can't really handle this when generating the HTML page,
which will come out a bit garbled in that case. Since a lot of users
may be only reading the Haddocks, we should prefer this to a source with
as few redundancies as possible.
Closes: https://github.com/xmonad/xmonad/issues/387
