kitchen/kiwmi
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix issues in README.adoc

Browse source 
Set kiwmi to lowercase.
Remove unintended heading.
Change "barely anything" to "almost nothing" for clarity.
This commit is contained in:
Qazzquimby 2019-03-07 14:08:49 -08:00 • committed by GitHub
parent b99482010c
commit f21386810a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
README.adoc
View file

@ -7,15 +7,15 @@ Configuration
-------------
Configuration languages are confusing. They are neither flexible nor easy to use. Moreover, they add significant complexity to the program itself.
Kiwmi listens to a socket and offers a basic client, kiwmic, to communicate with kiwmi, similarly to how bspwm works.
kiwmi listens to a socket and offers a basic client, kiwmic, to communicate with kiwmi, similarly to how bspwm works.
This allows the user to write the configuration in any langauge, e.g. as a bash script, which allows for high flexibility.
Kiwmi handles barely anything on it's own, and instead it emits events, to which the client can subscribe and react accordingly.
kiwmi handles almost nothing on it's own, and instead it emits events, to which the client can subscribe and react accordingly.
This allows for 100% flexibility and customizability, while requiring little overhead effort.
New user configurations will be linked as they are created, to help new users get started.
Kiwmi will end up being configured by a monolithic frontend, or collection of small scripts.
kiwmi will end up being configured by a monolithic frontend, or collection of small scripts.
A small (probably) Python library may be created to aid creating a monolithic frontend.
Dependencies
@ -32,6 +32,7 @@ Building
Make sure all dependencies are installed.
Run:
----
$ meson build
$ ninja -C build