<nmeum>
is there any way to make river quit fullscreen mode for the currently focused window once a popup dialog appears? for example, I often use full screen terminals windows and if I spawn a pinentry dialog from these windows (e.g. because of gpg/ssh usage) then I don't see that dialog
<leon-p>
nmeum: no, however I have created a pinentry replacement using the layer shel which will appear above fullscreen windows. it's called wayprompt. am on mobile right now, so no link
<leon-p>
alternatively you can use either the TTY or CLI pinentry shipped with gpg which appear right in the terminal
<nmeum>
I was considering coming up with a river patch (which would optionally unfocus the fullscreen window), but not sure if there is interest in this sort of feature…
<Dustee>
im also interested in how to make my mako notifications appear above fullscreen views, was hoping there was a rule option for that
pkap has joined #river
<nmeum>
my idea was something along the lines of: if the current window is focused and a new window appears on the workspace/tag then quit fullscreen mode
<Dustee>
i wouldn't want it to drop me out of fullscreen mode when im watching a movie or playing a game, that would be way too agressive. I just want to see the 3 second long notification in the corner.
<ifreund>
Dustee: for mako you can configure mako to use the overlay layer instead of the top layer
<ifreund>
tldr; some windows like the gtk file dialog in firefox give river the information that there is a parent/child relation between them and the firefox window
<ifreund>
if river has this information, I think it would be reasonable to display the child on top of the parent despite fullscreen
<ifreund>
as for pinentry specifically, I don't think it exposes that parent/child relationship to river as it is not created by e.g. your terminal process but rather by the gpg agent process
Dustee has quit [Quit: Client closed]
<ifreund>
leon-p's layer-shell pinentry is a good solution there IMO
<ifreund>
this protocol is not yet widely supported though, I don't think there's a wlroots implementation yet either
<ifreund>
anyhow, I totally agree that the current river UX is crappy and would be happy to review/merge a patch improving the situation
<nmeum>
maybe some sort of configuration option would be useful that defines under which circumstances a window should be display on top of a fullscreen one with configuration values such as if-child, always, …?
<nmeum>
I will give wayprompt a try for now maybe it resolves my usecase, thanks for the pointer! :)
<ifreund>
no problem :)
<Guest72>
Or phrased differently, is there an easy way to point the build towards wlroots if it is named wlroots-0.17 instead?
<ifreund>
Guest72: I think your first message got lost, it sounds like you want to replace river.linkSystemLibrary("wlroots"); with "wlroots-0.17" in river's build.zig though
<ifreund>
you could perhaps also use symlinks or similar to trick pkg-config, not sure
<Guest72>
Ah sorry, asked earlier because I got stuck trying to build river on chimera linux :) But looks like that already did the trick, thanks!
<ifreund>
oh, I see your message now. Hadn't caught up with everything from this morning yet
<Guest72>
No problem!
Guest72 has quit [Quit: Client closed]
<novakane>
would be nice if chimera just use wlroots name for the current release of wlroots, I haven't check if there is a reason to not do that
Szadek has quit [Quit: off]
angry_vincent has quit [Remote host closed the connection]
Szadek has joined #river
<ifreund>
novakane: it's to allow installing multiple wlroots versions side-by-side
<ifreund>
there are plans to switch to that naming scheme in upstream wlroots as well
lbia has quit [Ping timeout: 252 seconds]
<novakane>
ifreund: yeah but wouldn't that works with wlroots for latest and then like wlroots-0.X?
<novakane>
althought if it done upstream then it wouldn't mess with river since we would use it in the build.zig
<ifreund>
There would always be a version in the pkg-config name for wlroots releases
<ifreund>
I don't know exactly what the plan for master branch would be, probably the unreleased version
<ifreund>
I'll probably tag 0.3.2 with Zig 0.12 compatibility shortly afterwards
angry_vincent has quit [Ping timeout: 240 seconds]
lbia has quit [Ping timeout: 264 seconds]
lbia has joined #river
Guest51 has joined #river
Guest51 has quit [Client Quit]
Dustee has joined #river
angry_vincent has joined #river
Guest93 has joined #river
Guest93 has quit [Client Quit]
<Dustee>
how do i reliably escape the bounds of a game with my cursor? riverctl focus_output only works half the time and half the time it moves the game view along with it
<Dustee>
ive also tried ydotool to move the cursor but it just simulates moving the mouse it doesnt make the cursor escape the bounds
angry_vincent has quit [Ping timeout: 260 seconds]
leopoldek has joined #river
Guest76 has joined #river
leopoldek has quit [Ping timeout: 240 seconds]
Guest76 has quit [Quit: Client closed]
waleee has joined #river
kotto has joined #river
<ifreund>
0.3.1 is tagged!
angry_vincent has joined #river
leopoldek has joined #river
waleee has quit [Ping timeout: 240 seconds]
Guest58 has joined #river
Guest58 has quit [Client Quit]
Dustee has quit [Ping timeout: 250 seconds]
<nmeum>
are there any plans regarding zig 0.12.0 support? in alpine we only package the most recent zig so we can't upgrade river right now. should I just cherry-pick the patches from the zig-next branch or is that a bad idea?
lbia has quit [Ping timeout: 260 seconds]
lbia has joined #river
Dustee has joined #river
belanthor_ has joined #river
belanthor has quit [Read error: Connection reset by peer]
pkap has quit [Ping timeout: 250 seconds]
angry_vincent has quit [Ping timeout: 240 seconds]
Dustee has quit [Quit: Client closed]
Dustee has joined #river
Szadek has quit [Quit: off]
Szadek has joined #river
<Dustee>
how can i type accented characters on river? it seems there is no compose key
waleee has joined #river
<vyivel>
Dustee: riverctl keyboard-layout -options <options>, it seems
<vyivel>
with <options> setting up the compose key