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
Hello, I would like to add a few commands which display information related to the current layout, specifically the current count / wide-count. This would be very helpful for making custom waybar modules.
Desired solution
Perhaps the wideriver binary (or a separate binary) could have a --print-count flag for example. This would work pretty well, and i imagine would be quite simple to implement.
Ideas
No response
The text was updated successfully, but these errors were encountered:
There's currently an undocumented "feature" that will display the count and ratio, when you're running with --log-threshold debug. It sounds like it may not match your use, however if it does we could make it a first class feature.
We can definitely add commands to do this. Something like
--get-count --get-ratio
riverctl send-layout-cmd wideriver "--get-count"
We could also add the layout and stack for completeness.
Edit: there does not appear to be a means to return any sort of output string from a layout command.
The simplest course of action may to add a user defined layout strings, defined at startup. Perhaps something like:
--layout-name-wide 'H H $count'
--layout-name-left '$count I H $ratio'
printf format strings should not be used for security.
Waybar could simply show the layout string, process via a regex, or the user could implement a custom module.
Missing behavior
Hello, I would like to add a few commands which display information related to the current layout, specifically the current count / wide-count. This would be very helpful for making custom waybar modules.
Desired solution
Perhaps the wideriver binary (or a separate binary) could have a --print-count flag for example. This would work pretty well, and i imagine would be quite simple to implement.
Ideas
No response
The text was updated successfully, but these errors were encountered: