Events IPC #411
mentalblock
started this conversation in
Ideas
Events IPC
#411
Replies: 2 comments 9 replies
-
Why a separate socket? My plan is to just make a |
Beta Was this translation helpful? Give feedback.
9 replies
-
It's implemented now: https://github.com/YaLTeR/niri/wiki/IPC#event-stream |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would like to suggest a separate, read-only Events IPC socket. This is something that the Hyprland compositor provides.
All events can be monitored by watching this socket. This would allow bars that have no plans to implement Wayland protocols to retrieve status changes immediately and efficiently. In particular, Eww is the bar I currently use. It has a listening mechanism,
deflisten
, that monitors the output of a command and updates the bar UI.In summary, if Niri had a read-only Events IPC, I would then be able to use the
socat
utility to extract and parse whatever Niri state I would like. It is lightweight and responsive method. My only use case at the moment is for workspaces status and focused window titles, but I am sure others would leverage this to suit their needs.Related discussions and issues:
Beta Was this translation helpful? Give feedback.
All reactions