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
Add a custom window rule argument to niri msg action spawn that applies properties to the first window created by the spawned process. For example, to spawn just one application window as floating, or at specific coordinates.
One question is how to represent this in the IPC structures. It would make sense to accept the same KDL as in the config for niri msg action spawn. However, it would also make sense to write out the window rule properties inside IPC structures, and pass them along with the rest of the action as JSON. And on the contrary, I don't like the idea of having a rule: String in IPC which is then parsed as KDL inside the niri server process.
So maybe we could put the window rule properties into the IPC structures and parse the config KDL in the client niri msg process? This unfortunately results in some duplication of window rule structures between the config and the IPC, but I guess that's not too bad.
The text was updated successfully, but these errors were encountered:
Add a custom window rule argument to
niri msg action spawn
that applies properties to the first window created by the spawned process. For example, to spawn just one application window as floating, or at specific coordinates.One question is how to represent this in the IPC structures. It would make sense to accept the same KDL as in the config for
niri msg action spawn
. However, it would also make sense to write out the window rule properties inside IPC structures, and pass them along with the rest of the action as JSON. And on the contrary, I don't like the idea of having arule: String
in IPC which is then parsed as KDL inside the niri server process.So maybe we could put the window rule properties into the IPC structures and parse the config KDL in the client
niri msg
process? This unfortunately results in some duplication of window rule structures between the config and the IPC, but I guess that's not too bad.The text was updated successfully, but these errors were encountered: