Hans Donner

initially that could... But that means the container is always running, and on a specific instance. And requires specific containers/images for the scheduled jobs. Would rather have a central cron/scheduler...

A loadbalancer is a good candidate for bridging in some of thse cases.

casued by `(add-hook 'window-configuration-change-hook #'nano-modeline-update-windows)` On removing the hook, all was ok.

seems to be this one: `(one-window-p t)` - one one window, it shows the modeline - ona a frame with two windows, split with `C-x 2`, when the top window...

current workaround: add `(remove-hook 'window-configuration-change-hook #'nano-modeline-update-windows)` after require - until investigated / fixed

rebased / squashed

i've noticed that one is needed, as some trailing odd background is visible. (I have a right-margin-width > 0)

I've noticed some "major" changes as well that impacted my customisation as well. "noticed some graphical issues" What do you mean? And what kind of customisations have you applied?

Looks like this might be fixed with #23

Hi, i've provided a workaround for the modeline still showing The inactive nano-modeline most likely is also fixed by #23