mike

The functions exposed on nog.window and nog.workspace seem to be missing from the generated documentation book.

Perhaps we should have nog copy a baseline config on startup if none exists. There are some defaults it loads but I think without a config.ns you may not get...

This one can definitely use a bit of planning, I think. > Things to consider: > > * What happens when the primary display gets removed? I think the program...

Just throwing this out there regarding the sizes of the tiles when moving a workspace between displays with really big resolution differences... I was playing around with how to implement...

>I am not too sure what the usecases are for saving/loading static layouts. The more I think about it the less useful it seems. Can you think about some valid...

YES I wanted to work on something like this after finishing the #255 issue. I've been thinking about it a bit; the thing that bugged me when I used i3...

There's a lot here to comment on but to start I'll point out that you can currently get the effect you want (I think) by using min_height and min_width. When...

This is actually by design to support some keyboard layouts that use the AltGr key (#210) However, you can configure nog to use the right alt key by adding this...

re-opening until we update the documentation

I've encountered this kind of thing occasionally, I think I haven't as much recently as I use the [min_width/min_height](https://timuntersberger.github.io/nog/configuration/settings.html?highlight=min_wi#settings) settings to make nog ignore these windows that I'm just pulling...