<aktina>
i think it would be better to update the example init file of river in the repo
<aktina>
i had something to do with floating a terminal, but it didn't seem to work, even when i gave it float app-id
<aktina>
as in the example init file there was a "riverctl rule-add float -app-id 'float*' -title 'foo'"
<leon-p>
aktina: the example init should be up to date, note though that it obviously targets git master and not the recent relase
<leon-p>
and how rules work changed recently
<aktina>
but in manpage of riverctl, there is no 'rule-add' option
<aktina>
oh
<aktina>
got it, i didn't read the last commit message
<leon-p>
people copying the example init from the repo while running an old version of river is a common mistake
<leon-p>
maybe we should have some version checking in it or something
<leon-p>
perhaps river could set a $RIVER_VERSION env var or something, with the init just exiting it is wrong
<leon-p>
although that does not solve the issue for people just copy-pasting commands...
<aktina>
i think i am using the latest version, i'm on voidlinux
<aktina>
in repology, which i checked just now, it seems to be up-to-date
<aktina>
i copy pasted commands, because, 1. i'm a noob in general, 2. 1st time using tags system
<leon-p>
master is ahead of the most recent release, obviously
<aktina>
sorry, i don't exactly understand everything you are saying enough
<aktina>
but can the example init in readme be linked to the 'example init of recent release' instead of master ??
<leon-p>
no
<leon-p>
a clean repo is internally consistent
<leon-p>
and regards git master branch as the most correct, not the recent release
<aktina>
well, maybe, i'll explain my experience
<leon-p>
also, users really should get into the habbit of just reading the docs instead of copy-pasting commands, we write them for a reason
<leon-p>
sorry, didn't mean to be snarky, but my opinion still holds
<aktina>
i installed river via my package manager, wanted to try it out, so i go to the github readme, and there i see a link to an example init file, and as i almost have no idea what it is, i simply copy paste to see where it develops
<dnkl>
isn't the example init packaged with river? Always use the packaged example conf (if available), not just with river, instead of pulling it down (or copying from) the one in the repo. That way you know for sure the versions match
<leon-p>
yeah, but that is a user error. We ship documentation and an example with each release. Upstream docs and example init target upstream changes
<aktina>
after having an initial experience, i wanted to have monocle layout, so i even changed it to rivercarro layout, so i now understand half of it, just, i found a 'inconsistency' with what i looked in manpage and the init in repo
<aktina>
dnkl: well, i don't think void shipped with example init
<aktina>
i first checked in my system before going to github
<aktina>
well, i understand that to have less conflicts in the repo, it is always uptodate with master branch
<aktina>
but i appreciate a note in readme next to the section where it shows example init that the init is in reference to the master branch and not the latest release
<leon-p>
PR it and see if it gets accepted 🤷
<aktina>
i find this to be a minor issue, i don't exactly mind, learnt something new
<aktina>
it just might confuse newcomers
<leon-p>
FWIW river is advanced software aimed at people with a fairly decent understanding of UNIX and related conventions
<aktina>
especially when not many blogs exist for setting up river (i kinda learnt how-to-linux only with blogs, forums and such)