mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-19 07:08:48 +01:00
komorebic is done when a command is in the daemon's queue, not when it has run, and a scenario opens a window right after giving a rule or a name: both are events of the same queue, and the window could be first. The platform asks for `state` after every command that changes something, which the daemon answers in the order it got things (the rules scenario failed a different check on each run before, and its named-workspace checks pass three runs in three now). The daemon watches its configuration file with FSEvents, and a file written in the first half second after it answered is never noticed (0 s: not reloaded in 12 s; 0.5 s: reloaded after 2.6 s; later ones after two or three seconds). A start waits a second for it, as nobody edits a file that fast. config_reload goes from 6 of 8 checks to 8 of 8.