<iiogama>
For those that have the different keyboard modes configured, what do you use them for? I really like the idea, but I can't think of anything I would use them for that I can't accomplish with bemenu.
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 255 seconds]
waleee has quit [Ping timeout: 255 seconds]
tomcat0x42_ has quit [Ping timeout: 256 seconds]
vyivel has quit [Read error: Connection reset by peer]
leopoldek has quit [Remote host closed the connection]
xtvl_ has quit [Quit: WeeChat 4.2.1]
Guest98 has joined #river
traidare has joined #river
Cornelius-Figgle has quit [Quit: leaving]
Cornelius-Figgle has joined #river
Guest98 has quit [Quit: Client closed]
traidare has quit [Ping timeout: 264 seconds]
<ifreund>
iiogama: one example might be a mode to move floting windows around with the keyboard
<leon-p>
I had something like that, but never got used to it
<ifreund>
yeah, the original motivation for modes was that I needed a passthrough mode to use nested compositor instances but didn't want to hardcode that feature for whatever reason
<LarstiQ>
ifreund: I do think that was an elegant way to handle it, even if I haven't found a real practical other use of modes (yet!)
<ifreund>
the locked mode is actually pretty useful too
<LarstiQ>
oh true
<leon-p>
yeah, agreed
<leon-p>
which means the WM protocol will have to communicate locked state
waleee has joined #river
<novakane>
hmm I guess I need to send the same patch for lswt than for wlopm makefile, sorry to break the readability
<leon-p>
I am not too concerned with the readability of a sub-100 lines Makefile
<novakane>
ifreund: pkg-config find it, also meson and zig no problems but yeah I need CFLAGS and LDFLAGS for make
<leon-p>
novakane: have you set C_INCLUDE_PATH (f.e. in your .profile) to include ~/.local?
<leon-p>
note that it's different from PKG_CONFIG_PATH and LD_LIBRARY_PATH
<ifreund>
Makefiles have no automatic pkg-config integration like meson
<ifreund>
Makefile authors have to invoke pkg-config manually
<leon-p>
make predates pkg-config and probably even shared distributed libraries by a fair amount
<novakane>
ah yeah i only have PKG_CONFIG_PATH and LD_LIBRARY_PATH
<ifreund>
yeah, for sure. It's still good practice to use pkg-config these days though
<leon-p>
novakane: set it to "${HOME}/.local/include/:${C_INCLUDE_PATH}". Setting it just to ~/.local will not work well
<novakane>
I think I even removed C_INCLUDE_PATH because it wasn't used, on void at least
<novakane>
yeah seems to be fixed, thanks
<novakane>
ifreund: re XDG_CURRENT_DESKTOP, I have in my start script too, but portals doesn't seems to be aware of it, seems to still works tough
<ifreund>
hmm, actually now that you mention it it's probably not in the environment of my session bus/portals either...
<novakane>
yeah using `< "/proc/$(pidof xdg-desktop-portal)/environ" tr '\0' '\n' | grep '^XDG_CURRENT_DESKTOP='` from xlr portal wiki to check, it's empty
<ifreund>
maybe the river-portals.conf file is now sufficient or something
<ifreund>
anyhow, I'm not going to care until it breaks :D
<novakane>
same xD
traidare has joined #river
<novakane>
ifreund: hmm did you install msmtp for git email, I can't find it?
<ifreund>
novakane: It's not packaged afaik, I tried out the new pyonji utility
<novakane>
oh right never could try pyonji before, didn't have any patch to send since it was made
<ifreund>
let's see if I managed to regress anything
alexherbo2 has joined #river
<ifreund>
also, I'm thinking about dropping the transaction timeout to something lower than 200ms, it feels long enough to be more annoying than the lack of frame perfection IMO
<ifreund>
I need to do some more playing around to find a sweet spot but I think for me personally it's more like 50-100ms
<ifreund>
any thoughts? I don't really want to make it configurable...
leopoldek has joined #river
<leon-p>
I am fine with anything that still looks/feels ok with foot and the average GTK application. Firefox is a lost cause
<leon-p>
although please don't forget that your workstation is a bit faster than the average river running computer :)
<ifreund>
leon-p: I have a x200 now to test with :)
<leon-p>
nice :]
<ifreund>
er, x220
<leon-p>
err, close enough
tomcat0x42 has joined #river
<novakane>
this is nice to see #807 closed \o/
<ifreund>
Indeed, that was in my head at least the biggest blocker before 0.3.0
<ifreund>
now it's just a few features I want to land and cleanup
<ifreund>
well, assuming my "fix" hasn't regressed anything that is :)
<leon-p>
this might be placebo, but typing into fuzzel feels faster now, but I don't think anything related to that was touched recently
<ifreund>
leon-p: probably placebo yeah, I mean there have been some changes to the keyboard code but nothing that should really affect perf
<leon-p>
btw, 959 should be ready for review now
<ifreund>
ah nice, thanks
<dagle>
Hmmm. I managed to crash steam and it managed to lock up river.
<ifreund>
dagle: what exactly do you mean by "lock up river"? as in river is no longer responsive to input?
<dagle>
ifreund: Couldn't move mouse, use keyboard or anything.
<dagle>
My guess it's xwayland that did something funky but I'm no expert.
<ifreund>
dagle: It could be that river crashed and left the VT in a dirty state... any chance you have a coredump?
<ifreund>
by the way, you can recover in this case using sysrq + r to reclaim the keyboard from river and switch ttys
<dagle>
Nope. I don't find any coredumps.
<dagle>
Yeah, dunno if elephant dance is enabled on this machine.
<ifreund>
right, some distros disable it by default
<ifreund>
too bad about the coredumps, if you happen to find any relevant logs or other evidence please open an issue
<dagle>
I could have sshed into the machine and forced a crash etc. If it happens again, I'll do that.
<ifreund>
that'd be great thanks, it's pretty hard to fix something like that without at least a stack trace :)
alexherbo2 has quit [Remote host closed the connection]
<dagle>
So, what happened it that for some reason after suspend, 3 instances of steam started to run.
<ifreund>
you could try backporting the wlroots patch I linked if you want
<dagle>
I'm not running master though.
<dagle>
And it wasn't just the window it self, it was background services and everything.
<ifreund>
ah, yeah no idea then
<ifreund>
to be honest, it's probably not worth digging too deeply if it can't be reproduce on master at this point
<ifreund>
I hope to have 0.3.0 out in the next few weeks
kraem has quit [Remote host closed the connection]
kraem has joined #river
kraem has quit [Remote host closed the connection]
<leon-p>
even just based on the amount of time we have to respond with "please try again with git master" here on IRC the release will be worth it
kraem has joined #river
<LarstiQ>
:)
kraem has quit [Remote host closed the connection]
kraem has joined #river
kraem has quit [Remote host closed the connection]
kraem has joined #river
tomcat0x42 has quit [Ping timeout: 255 seconds]
leopoldek has quit [Remote host closed the connection]
alexherbo2 has joined #river
<szgy>
I y'all I've been having a consisten crash of an app on river (master). The app itself is bitwig-studio (a closed source DAW). I've run river with the debug and error logs but the output doesn't seem to be usefule
<szgy>
On the tty I run river it appears an 'Connection reset by peer PIPE(EE)' and some other stuff which doesn't appear on the log (I can post a picture of the screen if it helps)
<szgy>
This crash doesn't happen on the stable version. I'm installing the river-git package from the AUR in artix linux which I _think_ tracks master...
<LarstiQ>
those should be using different versions of wlroots, right?
<szgy>
river stable and river master? yeah. stable uses wlroots 0.16 and master 0.17
<leon-p>
Does that program run via XWayland?
<szgy>
yep, it seems so (just tried with xwininfo)
<szgy>
it probably relates to bitwig being a DAW and supporting VST plugins (I think opening plugin windows conflicts with how wayland is designed??)
<novakane>
it was working fine iirc as flatpak sometimes ago
<szgy>
bitwig-studio? yeah, not going to run it as flatpak - mostly because since flatpak is sandboxed you can't run external plugins -
<szgy>
on river 0.2 it works fine. but being an app run through XWayland it probably relates to that or wlroots
<leon-p>
probably an XWayland integration issue
<leon-p>
I can also sometimes crash river by hovering the cursor for too long on certain elements in Gimp
<novakane>
DAW is eally one of the few things I can't run on Linux, too annoying
Guest85 has joined #river
Guest85 has quit [Client Quit]
<leon-p>
well, with synths you can always go analog
<szgy>
@leon-p: yeah, the crash is basically hovering stuff until it crashes bitwig (but I thought Gimp was already Wayland native??)
<leon-p>
Gimp is still GTK-2, the GTK-3 port will be released in a few weeks IIRC
<szgy>
novakane: well, it has gotten muuuuch better
<szgy>
oww,nice
<novakane>
szgy: sure, like bitwig is nice on Linux but VSTs meh still annoying especially if you're not like on Ubuntu or something
<novakane>
or like I have a Maschine MK3, I can forget about it on linux
<szgy>
on arch I've been using yabridge for a while without many issues. But I must say I use veeery few vst plugins (maybe a couple of Valhalla and thats it)
<szgy>
doesn't bwig have a Machine MK3 script?? Or does it need a Windows/Mac software to be usable?
<szgy>
is it a MIDI controller or a sort of Elektron type thing??
<leon-p>
I have an old drum-machine as MIDI source, but never got that to work unfortunately
<leon-p>
because I have this fun sound of kicking a large plastic silo which would be a good bass
<novakane>
szgy: yeah as midi it works but with a lot of features that's doesn't without the software, only on windows
Szadek3 has quit [Ping timeout: 255 seconds]
alexherbo2 has quit [Remote host closed the connection]
<szgy>
deamn. Yeah, I also been finding this tendency of brands that sell MIDI controllers which actually don't send MIDI data and are actually HID devices
<szgy>
and its hard to know before you buy it? which like, what the hell
<novakane>
maybe someday after gaming they'll work on music making on Linux :P