mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: komorebic start --bar causes unnecessary resizing
#568
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @helmesjo on GitHub (Jan 23, 2025).
Summary
This is arguably a "bug" (at least in a UX-sense), but also border-line feature as well.
When you start
komorebicalong with the bar then the windows are tiled & resized first, then the bar pops up, then the windows are resized again.Is there a specific reason for this, or should the order perhaps just be swapped?
OT but slightly related:
Is there a way to measure startup time of the individual parts? Eg. initial tiling, bar setup, whkd etc.
Version Information
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
@LGUG2Z commented on GitHub (Jan 23, 2025):
You can avoid the double-resize by setting your desired
work_area_offsetdirectly inkomorebi.jsoninstead of inkomorebi.bar.json@LGUG2Z commented on GitHub (Jan 23, 2025):
For startup time benchmarking you could add your own to the
startcommand handler - there are a few calls tosleepin there while polling and waiting for different pieces to come up in a certain order