mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-16 13:51:19 +01:00
docs(lag): the lag command and the geometry-lag finding in the guide and the docs
This commit is contained in:
1 parent
aca5ea7e80
commit
a6f5a4e758
2 files changed
+7
No files matched your search
@@ -125,6 +125,7 @@ and `event:12.end` when it finished.
|
||||
| `diff A B` | What changed between two moments in terms a person would use: a window appeared, moved, was really somewhere else; focus moved; a monitor came or went |
|
||||
| `events` | komorebi's events, classified (command, focus, lifecycle, drag, monitor, lock, and `echo`: the OS reporting back a move komorebi made itself), with the handler that ran and whether the state changed |
|
||||
| `trace event:N` | One event end to end: what its handler logged, with the source statement for each line, what other threads logged meanwhile, and every change with who made it (see below). `--os` adds the OS trace around it: komorebi's own calls into the OS, the system and each application, split into while the handler ran and after |
|
||||
| `lag [--window ID] [--tolerance N] [--grace-ms MS]` | For each window, every stretch it was off the rect komorebi's layout gave it (needs `--window-track`): start, end, duration, and the largest and last offset on each edge, in pixels (points on a Mac). With border windows in the track, whether the border or the window lagged. Offsets within the tolerance (default 8) and the grace after a layout change (default 500 ms, for animations) are not flagged. On KDE the track is komorebi's own state, so nothing is reported and the answer says why. The same episodes are the `geometry-lag:window` and `geometry-lag:border` findings |
|
||||
| `window ID\|TEXT` | One window's life: when it appeared, moved, was parked off screen, was really somewhere else, and which event did each |
|
||||
| `code event:N`, `code log:N` | The line of komorebi's source that wrote a log line, with the code around it |
|
||||
| `logq QUERY` | Query komorebi's log by field, with no escape codes or span prefixes to strip: `level=ERROR and message~ghost`, `hwnd=0x77179C` (decimal and hex are the same window), `command=MoveWindow`; `--count`, `--group-by FIELD`, `--from`/`--to`, `--spans` |
|
||||
|
||||
@@ -121,6 +121,12 @@ locations as hints.
|
||||
(pixels on Windows, points on a Mac). On Windows komorebi's border windows are in the track too, marked `border`
|
||||
(`border_of` names the window for a floating window's border; a tiled one is named for its container in the
|
||||
`title`, to be joined with `State`; pairing by rect is a heuristic, not recorded). Without it (`--no-window-track`, or a host that cannot list windows) only the sparse per-event probes exist.
|
||||
`lag <session>` (also the `geometry-lag:window` and `geometry-lag:border` findings) compares that track
|
||||
with komorebi's layout rects: per window, each stretch it was off its layout rect, start, end, duration, and
|
||||
the largest and last offset on each edge, on the master clock; with border windows in the track (rows marked
|
||||
`border`) it says whether the border or the window lagged. Offsets within `--tolerance` (default 8) and the
|
||||
first `--grace-ms` (default 500) after a layout change, when komorebi may be animating, are not flagged.
|
||||
On KDE the track is komorebi's own state, so `lag` says it is not independent and reports nothing.
|
||||
- Video time `00:00.000` is the first frame of any display. A display that was unplugged, asleep
|
||||
or whose capture failed has a gap, and `incident` records say why.
|
||||
|
||||
|
||||
Reference in new issue
Block a user