Explain the different use cases of Layout.Spacing, Layout.Gaps and Hooks.ManageDocks.

[xrvdg]

I wanted to start a discussion about the use cases of these layout modules as per issue #160 . The modules Layout.Spacing, Layout.Gaps and Hooks.ManageDocks seem to have overlapping functionality to the uninitiated.

Layout.Spacing vs Hooks.ManageDocks

Layout.Gaps already contains a note that if you want to leave space for a dock-type application you should use Hooks.ManageDocks. I think that Layout.Spacing should also contain the first sentence of the note:

Note that XMonad.Hooks.ManageDocks is the preferred solution for leaving space for your dock-type applications (status bars, toolbars, docks, etc.), since it automatically sets up appropriate gaps, allows them to be toggled, etc.

And maybe a link with reference to Layout.Gaps for the second sentence in the note.

However, XMonad.Layout.Gaps module may be useful in some situations where the automated approach of ManageDocks does not work; for example, to work with a dock-type application that does not properly set the STRUTS property, or to leave part of the screen blank which is truncated by a projector, and so on.

Layout.Spacing vs Layout.Gaps

The modules Layout.Spacing and Layout.Gaps seem to have overlapping functionality. Both create a gaps/space around a window. The differences being that:

• Layout.Spacing is user friendlier if you want uniform gaps rather than different gap sizes;
• Layout.Gaps can toggle the gaps, but I guess this is not to hard to implement for Layout.Spacing if desired. It already "toggles" the spaces with the smartSpacing* functions.

Are there more cases to use Layout.Gaps over Layout.Spacing?

[ellakk]

Are there more cases to use Layout.Gaps over Layout.Spacing?

The documentation clearly says Layout.Spacing is to add spacing around windows and Layout.Gaps is for the screen edges (Fallback if ewmh does not not work for some reason). I don't see how this functionality overlaps. There's a fad these days in the wm community to add gaps around windows for seemingly aesthetic reasons, there's a popular fork (confusingly called i3-gaps, it would be i3-spacing in xmonad terms) of I3 that's built around this functionality.

[xrvdg]

@ellakk you are absolutely right, I have read the documentation with i3-gaps in mind. My bad!

[geekosaur]

I'd argue this documentation is needed *precisely* because of this confusion.

…

On Mon, Jul 3, 2017 at 2:32 PM, Xander van der Goot < ***@***.***> wrote: @ellakk <https://github.com/ellakk> you are absolutely right, I have read the documentation with i3-gaps in mind. My bad! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#199 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8SoFPsROdsPP3gk5qGDp7Ew9aGUxr-ks5sKTO8gaJpZM4OMZlg> .

-- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net