You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for making this, it is amazing, and I love to be able to use my i3status-rs config outside of sway.
I'm not sure, but I think all, the workspace button logic can be done through the i3bar protocol.
So one simple approach would be making the same i3bar protocol we have on the right also for the left.
To make this work, we would also need to create such a workspace button generator for river and hyprland.
Maybe i3status-rs will add workspace modules once this works.
The text was updated successfully, but these errors were encountered:
There is actually a specialized protocol in i3-bar for that: i3/i3#4311, but it is one-way (the script streams json, but does not receive any events) and effectively only works for i3/sway.
Using the same protocol for both right and left parts of the bar seems doable and reasonable, I just didn't have a use for that.
By the way, I'm open to supporting more compositors/wms if that is your use case.
First of all, thanks for making this, it is amazing, and I love to be able to use my i3status-rs config outside of sway.
I'm not sure, but I think all, the workspace button logic can be done through the i3bar protocol.
So one simple approach would be making the same i3bar protocol we have on the right also for the left.
To make this work, we would also need to create such a workspace button generator for river and hyprland.
Maybe i3status-rs will add workspace modules once this works.
The text was updated successfully, but these errors were encountered: