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
# The filename to which Vivarium will write workspace state information whenever something changes.
# Programs can watch this file to display the workspace status.
# This is a hacky solution that will be deprecated at some point.
# workspaces-filename = "/path/to/some/file.txt"
what are the (if any) plans/ideas for implementing a better IPC mechanism?
Will Vivarium use a custom Wayland protocol for this ala River? This for example is how yambar is able to extract the current workspace info from River directly.
The text was updated successfully, but these errors were encountered:
I don't have any specific plan for this - in its current state it's good enough for my use and it isn't at the top of the priority list for further development.
I deliberately stayed away from a full custom protocol initially because it's a lot of complexity that wasn't core to what Vivarium needed and that I didn't think I could support well. I was thinking that perhaps an adequate intermediate solution would be a proper output data socket but with relatively little configurability compared to a full protocol. I haven't thought it through in much detail though.
Given the future deprecation notice in:
vivarium/config/config.toml
Lines 67 to 71 in 94b4d6a
what are the (if any) plans/ideas for implementing a better IPC mechanism?
Will Vivarium use a custom Wayland protocol for this ala River?
This for example is how yambar is able to extract the current workspace info from River directly.
The text was updated successfully, but these errors were encountered: