starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[FEAT]: Watching Variables (e.g. workspace number) #282

New Issue
Closed
opened 2026-01-05 14:49:28 +01:00 by adam · 8 comments
adam commented 2026-01-05 14:49:28 +01:00
Owner
Copy Link

Originally created by @skulldogged on GitHub (Jan 13, 2024).

Is your feature request related to a problem? Please describe.
I've added a widget to the rainmeter skin I use that shows which komorebi workspace I'm on. As of right now though, it doesn't seem I can properly "watch" the workspace value for changes. Currently I'm just re-running komorebic query focused-workspace-index every second.

Describe the solution you'd like
A komorebic command for watching values for changes, outputting the new value to stdout when it changes.

Describe alternatives you've considered
As said above, I just re-run the query every second.

Additional context
N/A

Originally created by @skulldogged on GitHub (Jan 13, 2024). **Is your feature request related to a problem? Please describe.** I've added a widget to the rainmeter skin I use that shows which komorebi workspace I'm on. As of right now though, it doesn't seem I can properly "watch" the workspace value for changes. Currently I'm just re-running `komorebic query focused-workspace-index` every second. **Describe the solution you'd like** A komorebic command for watching values for changes, outputting the new value to stdout when it changes. **Describe alternatives you've considered** As said above, I just re-run the query every second. **Additional context** N/A
adam added the enhancement label 2026-01-05 14:49:28 +01:00
adam closed this issue 2026-01-05 14:49:28 +01:00
adam commented 2026-01-05 14:49:28 +01:00
Author
Owner
Copy Link

@skulldogged commented on GitHub (Jan 13, 2024):

(Apologies if this already exists, but from what I've seen in the documentation + issues it doesn't seem to be.)

@skulldogged commented on GitHub (Jan 13, 2024): (Apologies if this already exists, but from what I've seen in the documentation + issues it doesn't seem to be.)
adam commented 2026-01-05 14:49:28 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 13, 2024):

This is an interesting idea; would it be enough to terminate reach returned update value with a newline?

@LGUG2Z commented on GitHub (Jan 13, 2024): This is an interesting idea; would it be enough to terminate reach returned update value with a newline?
adam commented 2026-01-05 14:49:28 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 13, 2024):

Also I'd love to see a screenshot of what you've made in Rainmeter!

@LGUG2Z commented on GitHub (Jan 13, 2024): Also I'd love to see a screenshot of what you've made in Rainmeter!
adam commented 2026-01-05 14:49:28 +01:00
Author
Owner
Copy Link

@modkavartini commented on GitHub (Jan 13, 2024):

they would be referring to something like this:

Rainmeter_rur94HLqc6

(i coincidentally fell upon this post xd)

@modkavartini commented on GitHub (Jan 13, 2024): they would be [referring to](https://github.com/modkavartini/catppuccin/issues/14) something like this: ![Rainmeter_rur94HLqc6](https://github.com/LGUG2Z/komorebi/assets/81793953/6551a816-1769-4146-9157-ceef40eaf404) (i coincidentally fell upon this post xd)
adam commented 2026-01-05 14:49:29 +01:00
Author
Owner
Copy Link

@skulldogged commented on GitHub (Jan 14, 2024):

This is an interesting idea; would it be enough to terminate reach returned update value with a newline?

Honestly, I'm not sure... I don't see any reason why that would be bad, but I'm not sure if it would be the best approach either.

@skulldogged commented on GitHub (Jan 14, 2024): > This is an interesting idea; would it be enough to terminate reach returned update value with a newline? Honestly, I'm not sure... I don't see any reason why that would be *bad*, but I'm not sure if it would be the best approach either.
adam commented 2026-01-05 14:49:29 +01:00
Author
Owner
Copy Link

@melMass commented on GitHub (Jan 31, 2024):

Thanks a lot @modkavartini , super useful widget, I had a bad experience with bulky rm skins years ago but this bar works really well and was my missing bit after swtiching from GlazeWM to komorebi!

@LGUG2Z IMHO it could be referenced in the readme since yasb is not straightforward to install and quite bulky in the end

@melMass commented on GitHub (Jan 31, 2024): Thanks a lot @modkavartini , super useful widget, I had a bad experience with bulky rm skins years ago but this bar works really well and was my missing bit after swtiching from GlazeWM to komorebi! @LGUG2Z IMHO it could be referenced in the readme since yasb is not straightforward to install and quite bulky in the end
adam commented 2026-01-05 14:49:29 +01:00
Author
Owner
Copy Link

@melMass commented on GitHub (Mar 21, 2024):

I guess this can be closed now that we have event subscription

@melMass commented on GitHub (Mar 21, 2024): I guess this can be closed now that we have [event subscription](https://github.com/LGUG2Z/komorebi?tab=readme-ov-file#window-manager-event-subscriptions)
adam commented 2026-01-05 14:49:29 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Mar 21, 2024):

Yeah, since you can now subscribe to events with the entire state using both UDS and Named Pipes I'm gonna close this out.

@LGUG2Z commented on GitHub (Mar 21, 2024): Yeah, since you can now subscribe to events with the entire state using both UDS and Named Pipes I'm gonna close this out.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#282
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?