mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Komorebi Bar Conifguration Doesn't Apply On Start #554
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 @xidsyed on GitHub (Jan 3, 2025).
Summary
Problem
komorebi.bar.jsondefines some offset and size configuration that don't apply onkomorebic start --whkd --bar.Running the following command also doesnt seem to fix the problem
Stop-Process -name komorebi-bar; Start-Process komorebi-bar -windowstyle hiddenWork Around:
Open the file in any editor and save it again
Screenshot / Video
https://github.com/user-attachments/assets/8cd76809-caf1-4913-afc8-5c8a977a6744
Version Information
OS Name: Microsoft Windows 11 Home
OS Version: 10.0.22631 N/A Build 22631
komorebic 0.1.32
tag:v0.1.32
commit_hash:4b9d8114
build_time:2025-01-01 19:37:02 +00:00
build_env:rustc 1.83.0 (90b35a623 2024-11-26),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
Looking for configuration files in C:\Users\mmsye
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\mmsye.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@arijit-gogoi commented on GitHub (Jan 5, 2025):
I am having this bug too.
Another workaround is just
touch C:\Users\name\.config\komorebi\komorebi.bar.json.@CtByte commented on GitHub (Jan 5, 2025):
I do not know if it's related, but when you execute the
stopcommand you do not stop the bar and when you execute thestartcommand, you start a new bar, end up having 2 bars running at the same time.@xidsyed commented on GitHub (Jan 6, 2025):
komorebic stop --baryou need to add a
barargument to stop the bar.