Usage

Removes all window borders from the specified layout.

Removes the borders from a window under one of the following conditions:

• There is only one screen and only one window. In this case it's obvious that it has the focus, so no border is needed.
• A floating window covers the entire screen (e.g. mplayer).

Forces a layout to use the specified border width. noBorders is equivalent to withBorder 0.

Apply a datatype that has a SetsAmbiguous instance to provide a list of windows that should not have borders.

This gives flexibility over when borders should be drawn, in particular with xinerama setups: Ambiguity has a number of useful SetsAmbiguous instances

ManageHook for sending HasBorder messages:

   title =? "foo" --> hasBorder True

There is no equivalent for ResetBorder.

SetsAmbiguous allows custom actions to generate lists of windows that should not have borders drawn through ConfigurableBorder

To add your own (though perhaps those options would better belong as an additional constructor to Ambiguity), you can add the following function. Note that lr, the parameter representing the Rectangle of the parent layout, was added to hiddens in 0.14. Update your instance accordingly.

data MyAmbiguity = MyAmbiguity deriving (Read, Show)

instance SetsAmbiguous MyAmbiguity where
 hiddens _ wset lr mst wrs = otherHiddens Screen \\ otherHiddens OnlyScreenFloat
    where otherHiddens p = hiddens p wset lr mst wrs

The above example is redundant, because you can have the same result with:

layoutHook = lessBorders (Combine Difference Screen OnlyScreenFloat) (Tall 1 0.5 0.03 ||| ... )

To get the same result as smartBorders:

layoutHook = lessBorders Never (Tall 1 0.5 0.03 ||| ...)

This indirect method is required to keep the Read and Show for ConfigurableBorder so that xmonad can serialize state.

In order of increasing ambiguity (less borders more frequently), where subsequent constructors add additional cases where borders are not drawn than their predecessors. These behaviors make most sense with with multiple screens: for single screens, Never or smartBorders makes more sense.

Used to indicate to the SetsAmbiguous instance for Ambiguity how two lists should be combined.

Only necessary with BorderMessage - remove non-existent windows from the alwaysHidden or neverHidden lists.