all repos — ryudo @ eb4238f6f1cd09b508ddf501e44b437aaf9565f0

the floatiling window manager that flows; fork of rio from plan9port

update README
Iris Lightshard nilix@nilfm.cc
PGP Signature
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEkFh6dA+k/6CXFXU4O3+8IhROY5gFAmCclJoACgkQO3+8IhRO
Y5jaXw//cznxqYYq8xFiKliUlHfvYQPpvL1onVf2RXJvm+wcdgJPV8RbGNCithAf
KsppEe6vMUsVZTZx/IzTrx/K1M9MqtAsSlG/IZmFSmzMAdoUiKqolA4vH5NfAwjG
bc8G8sT8tssJ2Ny2tG+fVeKhyXB+nAgCC5wis3Dxfr7D5yySE9vP7LG0AJpJ21gG
yJZIW16oQEBBzjip+jyCeLl5bJfJ5R25xZvg7YSAPAPRdr7/U+oiH81cO2lV6ybu
2vLNpaJGkGtq5z1g9c8PuqaoEJ+b+wv+Wb77cSqR4Btl9lRHbos4Jma11XKTSqZ1
e/BYf6mPse17Bt7QwpFUy54KU7RMup+1+n02XiBac3o0Id2+9+T784F6bgKkT0lF
6s4BXB1Zd8IwMqjUFsFUbjOw3O82RI9j/mCTuOXC+CsM6+huPDL71esiUpX4wRY/
Axc1GKCCxk6WokNjGGfaQQ4KpAssHsz0BIAal7VpTx6QmzeFkhJpSOYluQh9TAWJ
fQQg4xOlm9zxoDRTyVPd7tYVpJFFseY9FDzvUgLRlIRtHVLeZfmkVyTWroIFvS7Z
nSjSwwkY+n7ZNj97r658c1+V8OFRFt594e/R49m+2m+QhwWI91YUf63SyUuhMamL
5Oy/zeV2zJpJS1jfjk6f/KxS8xHE+4diHNFC9qbOvhPKAzUcSaQ=
=yKk2
-----END PGP SIGNATURE-----
commit

eb4238f6f1cd09b508ddf501e44b437aaf9565f0

parent

80d5a8db52eed2f354a9053c25be333ca13c8fef

1 files changed, 3 insertions(+), 9 deletions(-)

jump to
M README.mdREADME.md

@@ -52,17 +52,11 @@

### Dependencies, Building, Installation Being forked from Rio, Ryudo requires `plan9port`, `Xlib`, and `Xt`. If you enable notifications, it of course requires `notify-send`. -Make it with `mk ryudo` and then copy the resulting executable `ryudo` to -somewhere in your **PATH** -If you try to install it with `mk install` it will probably install -to `$PLAN9/bin/` under the name `rio`. This is less than ideal but I'm -not a master of mk, so my protocol is to use a mk target `ryudo` which -builds the program as `o.rio`, then calls `ryudomagic.sh` to rename -the program. A proper mkfile is planned before version 1.0. +Build with `build.sh` (calls `mk` and does some other magic), and install with `install.sh` (will install to a local folder if run as a normal user, or to your `$PLAN9/bin/` if run as root). -If you have trouble building, you might need to edit the **mkfile** at line 2 -to point to the proper location of your plan9port's **mkwsysrules.sh**. +If you have trouble building, you might need to edit the `mkfile` at line 2 +to point to the proper location of your plan9port's `mkwsysrules.sh`. ### Bugs and Caveats Of the bugs and caveats not already mentioned in Rio's readme: