docs/cli lagged behind the Windows komorebic: 35 pages had out-of-date
help text (possible values now listed with their descriptions, new doc
comments, the Scrolling commands without the komorebic.exe usage name) and
3 pages did not exist yet. They are regenerated from the current Windows
CLI definition (komorebic-core docgen-all example, platform windows,
COLUMNS=1000 so nothing is re-wrapped like the existing pages), and the
page conventions of each file are kept: header line only where the page had
one, komorebic.exe as the binary name, trailing newline. The other 149
pages are byte-identical to the fresh output. The KDE and macOS pages are
untouched (decision D20: Windows was the only stale set).
Docs only, no behaviour. Verified: regenerated twice, second compare shows no
diff; the real Windows binary was not run (the pages come from the shared
definition rendered on Linux, class text normalised to the Windows one).
komorebic pan --stream reads the gestures of fingers on a touchpad from standard input, as
whkd writes them for a swipe of three or four fingers (docs/gesture-stream.md in its
repository): a line for each begin, move, end and cancel, with the distances in centimetres,
and any field or message that it does not know ignored. The row follows the fingers while they
are down, and when they lift it comes to rest with a column against an edge of the screen,
going at the speed that the times of the moves say that the fingers were. Focus goes to the
nearest column in view if the focused one is not. A gesture that is given up, or that is
not finished when the stream stops, puts the row back to what it was.
komorebic works out nothing but what it is asked to: --sensitivity multiplies the distances,
--reversed flips the way that the row goes, and --paging takes a step for every two
centimetres that the fingers go, as komorebic pan does, and not move the row with them. Moves
that wait while one is told are added up, as whkd says that they may be.
A gesture is told to komorebi on one connection, which it handles in order, as messages
that are sent on a connection each are not. With ghost movement the pictures that cover the
windows near the screen are taken when the fingers go down, a move of the fingers sets them
where the row puts the windows and does nothing else, and when the fingers lift they glide to
where it comes to rest, over the time that an animation takes, and the windows are shown. Without
it the workspace is laid out a step at a time, as it is for a drag. Ten centimetres of the
fingers move the row the width of the screen. The golden transcript of whkd and the swipes
of its demo are fixtures of the tests that read the stream.
komorebic pan <left|right> moves the view along the row of the Scrolling layout by a column
without moving focus first, and lets it come to rest with a column against an edge of the
screen. Focus goes to the nearest column on the screen if the focused one has gone off it. It
does nothing in the other layouts.
The way that the view goes is the way that focus goes for the commands that have directions:
panning to the left brings what is to the left of the screen into view, which is to move the
row to the right.
This is a command that a wheel can be bound to, as it is with whkd:
alt + wheelup : komorebic pan left.
LGUG2Z