Crates.io | river-rs |
lib.rs | river-rs |
version | |
source | src |
created_at | 2025-01-28 11:40:28.190235 |
updated_at | 2025-02-02 16:37:00.135624 |
description | Utilities for configuring River Window Manager. |
homepage | |
repository | https://github.com/Yappaholic/river-rs |
max_upload_size | |
id | 1533431 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
This is just a proof of concept and my attempt at better understanding Rust
.
Currently Work In Progress.
Well, why not? After all, why not build something unique and fun.
On a more serious note, writing configuration for RiverWM
in programming languages
teaches a lot about language's basic operations, loops, typing, working with strings,
creating compound objects and tooling. That's why I would recommend you too to try
and build a simple library for configuring RiverWM
in any language you want
(C
, Zig
, Haskell
, Java?, whatever!).
Right now you can describe and apply custom keybindings in a procedural way, when you apply keybinds one by one, depending on wether you want to change the modifier keys, and then apply config in the end.
spawn
function by now)