Correct socket -> protocol in readme
This commit is contained in:
parent
d83cbf55d1
commit
f8a4f1dbe9
1 changed files with 3 additions and 2 deletions
|
@ -14,8 +14,9 @@ don't hesitate to
|
|||
- Simplicity and minimalism, river should not overstep the bounds of a
|
||||
window manger.
|
||||
- Dynamic window management based on a stack of views and tags like dwm.
|
||||
- Scriptable configuration and control through a socket and separate
|
||||
binary, `riverctl`, like bspwm.
|
||||
- Scriptable configuration and control through a separate binary,
|
||||
`riverctl`, like bspwm. This works using the custom
|
||||
[river-control](protocol/river-control-unstable-v1.xml) protocol.
|
||||
|
||||
## Packaging status
|
||||
|
||||
|
|
Loading…
Reference in a new issue