Zander671/river
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Correct socket -> protocol in readme

Browse Source
This commit is contained in:
Isaac Freund 2020-05-24 21:07:57 +02:00
parent d83cbf55d1
commit f8a4f1dbe9
No known key found for this signature in database
GPG Key ID: 86DED400DDFD7A11
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -14,8 +14,9 @@ don't hesitate to
- Simplicity and minimalism, river should not overstep the bounds of a - Simplicity and minimalism, river should not overstep the bounds of a
window manger. window manger.
- Dynamic window management based on a stack of views and tags like dwm. - Dynamic window management based on a stack of views and tags like dwm.
- Scriptable configuration and control through a socket and separate - Scriptable configuration and control through a separate binary,
binary, `riverctl`, like bspwm. `riverctl`, like bspwm. This works using the custom
[river-control](protocol/river-control-unstable-v1.xml) protocol.
## Packaging status ## Packaging status