04:53 <leon-p> updated my input config proposal a bit: https://paste.rs/Ksi

04:54 <leon-p> keyboards will require a bit more thought, but all other settings any arbitrary input device supports should be possible to support with this approach

11:50 <novakane> would something like this be good to make attach-mode global? https://zigbin.io/4e9a09

12:24 <leon-p> novakane: that probably does not do what you think it does

12:25 <leon-p> instead of making attach-mode global, that code only sets it for all existing outputs. If a new output is created after that command has been called, it will be unaffected

12:31 <novakane> leon-p: oh yeah I see, that's not the good way then, thanks

12:32 <novakane> leon-p: unrelated but you use aerc right?

12:42 <leon-p> novakane: yes, I am on aerc

12:43 <novakane> leon-p: how do you save in a correct format a patch received?

13:26 <leon-p> novakane: `:save <name of file>`

14:45 <novakane> leon-p: oh really, i tried this and it wasn't great, missing the header iirc

14:51 <leon-p> novakane: for git patches you can also just skip saving it and pipe it directly to `git am -3`

14:59 <novakane> oh ok cool thanks

17:35 <ifreund> ugh, drag icons need damage tracking too

17:43 <novakane> everyday a new surprise with damage tracking

17:47 <novakane> I saw you add #262 unstable/staging to 0.1.0, so what does it changes for river, build.zig?

17:53 <ifreund> novakane: it means that before releasing 0.1.0, I want to remember to consider doing that breaking change

17:56 <novakane> ifreund: yeah but I mean what should be changed in river? IF you dont want to change river-* protocol

17:57 <ifreund> if I decide not to break things, nothing

17:59 <novakane> got ya, either you do what I made with my closed PR and break everything or you just leave it like this

21:11 <Guest3537> Hello folks, trying to determine if river is the WM I should be using full-time as a replacement to my current Gnome setup. Hence the question, what features is river missing compared to sway?