angry_vincent has quit [Remote host closed the connection]
linkert has quit [Ping timeout: 255 seconds]
<ifreund>
hryx: not yet, that's a pretty tricky thing to coordinate between N clients in the layout plus the layout generator. Its possible and will probably be implemented someday but there are higher priorities at the moment
linkert has joined #river
Ordoviz has joined #river
linkert has quit [Ping timeout: 252 seconds]
linkert has joined #river
Guest63 has joined #river
linkert has quit [Ping timeout: 246 seconds]
waleee has joined #river
Ordoviz has quit [Ping timeout: 248 seconds]
<pinpoxIRC>
I've noticed very slow startup of applications (~10s) sometimes in river, not been able to pin it down yet. Any idea what could cause this? Waybar e.g. takes for ever to start, same for wofi. Interestingly spawning a terminal is instant
<pinpoxIRC>
seems to happen on master aswell as on latest release and the delay is a quite random. Wofi (mapped to a key) just took ~30s to applear and ~3s the next time. CPU and RAM are both idling, nothing wild going on here
<waleee>
would that be thanks to icons in waybar or wofi?
* waleee
does barless on wayland
<ifreund>
waleee: waybar and wofi both use gtk :/
* waleee
double checks the spelling
<pinpoxIRC>
I have no icons in either of those applications. But i just recently set some portal options, let me revert those and check if that fixes anything
<waleee>
ifreund: ah, ok
<waleee>
pinpoxIRC: it 100% is the issue ifreund linked if waybar & wofi both uses gtk
<pinpoxIRC>
Hah! I fixed it by reverting my portal changes. Question is now, how do i get screenshare to work
<pinpoxIRC>
waleee: I'm reading through that issue, but I'm not sure what the proper fix is. OP seems to have resolved it by installing xdg-desktop-portal-wlr, this is actaually what *caused* the issue for me
waleee has quit [Ping timeout: 246 seconds]
Ordoviz has joined #river
Ordoviz has quit [Ping timeout: 255 seconds]
Guest63 has quit [Ping timeout: 260 seconds]
<pinpoxIRC>
Anyone here using signal-desktop on river/wayland and has occasional random freezes? Not sure if it's a river, wayland or signal problem. Every few minutes it locks up for about 30 seconds, then continues to work normally
<ifreund>
freezes of what exactly? signal or everything?
<ifreund>
If it only happens when using signal then its very likely a signal bug
<pinpoxIRC>
I havn't tried other electron apps, it's pretty mucht then only one I use. With freezing I mean signal-desktop doesn't accept any input such as typing or clicking and does not update
<pinpoxIRC>
I'll investigate further, do you use any electron apps that are known to work on river so I can compare?
<ifreund>
yeah, likely a signal problem then, a WAYLAND_DEBUG=1 log would be informative
<pinpoxIRC>
With WAYLAND_DEBUG=1 I see a few errors related to notifications while it's frozen:
<pinpoxIRC>
(signal-desktop:129791): libnotify-WARNING **: 15:34:00.672: Failed to connect to proxy
<pinpoxIRC>
[129791:0326/153425.698012:ERROR:libnotify_notification.cc(49)] notify_notification_show: domain=1237 code=24 message="Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached"
<pinpoxIRC>
Seems dunst has segfaulted, that explains it
Szadek has quit [Quit: WeeChat 3.8]
Szadek has joined #river
Ordoviz has joined #river
<dagle>
https://github.com/dagle/griver fairly untested but hopefully it should work for most programming languages that has introspection.
Szadek has quit [Ping timeout: 264 seconds]
Szadek has joined #river
upsala has joined #river
leopoldek has joined #river
taupiqueur has quit [Ping timeout: 256 seconds]
taupiqueur has joined #river
leopoldek has quit [Ping timeout: 250 seconds]
<akumar[m]>
So, this is not strictly related to river, however I wonder if anybody else experience some electron apps segfault
<akumar[m]>
The only workaround I've found is to run a X wm in another tty
angry_vincent has joined #river
angry_vincent has quit [Changing host]
angry_vincent has joined #river
<tleydxdy[m]>
are your electron apps running in X or wayland?
<akumar[m]>
Running on Wayland
<akumar[m]>
Segfaults if there's no x session but works fine if I launch let's say an openbox in the background
<akumar[m]>
eg. mongo db compass
Szadek has quit [Ping timeout: 250 seconds]
<pinpoxIRC>
akumar[m]: had that happen without xwayland support enabled. Are you running river with that enabled?
<pinpoxIRC>
There seem to be a lot of PR's that where closed, wanted to track progress
<tleydxdy[m]>
do you have Xwayland?
<leon-p>
pinpoxIRC: yes
<leon-p>
well, it's the MR for the WIP replacement for foreign-toplevel-management
<leon-p>
foreign-toplevel-management is supported in a afair amount of compositors right now, including river
<pinpoxIRC>
Okay, trying to read/understand trough that. But how would that help me know what tags belong to which windows?
<leon-p>
oh, that alone would not. However, there yould be a river-specific extension to that that allows getting tags
<leon-p>
that's what I meantw
<pinpoxIRC>
aaah ok
<pinpoxIRC>
I've been using my monocle mode for a few days now and keep forgetting I have windows behind.
<pinpoxIRC>
Anything I can do to speed up getting this feature?
<leon-p>
still, if you'd like to have a task-bar of sorts that also shows the currently focused window, that is possible with the current foreign-toplevel-management
<leon-p>
maybe I should preface that with the caveat that I am always speaking from the POV of a developer / implementor, not of a user
<pinpoxIRC>
leon-p: I actually need a task bar that shows the *not* focused windows on the tags.
<leon-p>
yeah, that is what I meant is possible
<leon-p>
it just can't know the tags of windows, other than that it will work fine
<pinpoxIRC>
But if i dont know the tags of the windows, how will i know which windows there are on the currently shown tags?
<leon-p>
you don't
<pinpoxIRC>
riverctl map normal Super Tab focus-view next
<pinpoxIRC>
To be more explicit: I currently have this binding:
<leon-p>
for that hypothetical task-bar, you have two options: 1) show only the currently focused window, 2) show all windows on the output, regardless of tag, highlighting the focused one
<pinpoxIRC>
If I go into "monoclemode", that binding cycles through various windows (i.e. makes them visible on the current output by bringing them to the front)
<pinpoxIRC>
I'm trying to make a taskbar with a list of the windows that this binding will cycle through
<leon-p>
that won't work
<pinpoxIRC>
Ok, then I understood correctly
<leon-p>
you either get all windows from an output, or just the focused one
<leon-p>
that's what I have been trying to explain
<leon-p>
what you could do, as an alternative, is modify the layout generator to include the amount of windows in the layout in the layout name
<leon-p>
if you then use a status bar that displays the layout name, you at least know how many windows there are
<leon-p>
even if you don't get their titles
<pinpoxIRC>
That is a workaround true, but titles would of course be nicer.
<pinpoxIRC>
Okay. And the changes required to make that behaviour possible would be foreign-toplevel-management + some river-specific extension, correct?
<leon-p>
there won't be a river extension for *-management, only for ext-foreign-toplevel-info, but yes
<leon-p>
or, alternatively wait until tags are no longer part of river but the layout generator, which bypasses this issue entirely
<leon-p>
no idea which will happen first :)
<leon-p>
welcome to pre 1.0 software
<pinpoxIRC>
So, my last question for now (sorry if i'm stealing your time): Can I do something to help work toward that issue or are the changes required so complex I shouldn't even try ?
Ordoviz has quit [Ping timeout: 276 seconds]
<leon-p>
possible, but complex
<leon-p>
the easiest way would probably to add a custom riverctl command that returns the titles of windows in focus order, line separated
<leon-p>
alternatively, modify the foreign-toplevel-implementation to only advertise windows that are active based on tags <- this would allow re-using already existing task-bars (no idea if any actually exists though :))
<leon-p>
ooor, don't use monocle, but a stack layout like in stacktile, which helps you see all windows while still maximizing their size
Ordoviz has joined #river
<pinpoxIRC>
stacktile is like master-stack layout?
leopoldek has joined #river
<pinpoxIRC>
e.g. big window left side of screen , all the others below each other on the right?
<leon-p>
kinda, it's a bit more powerful though
<leon-p>
you can re-create how rivertile works in stacktile, so it's a superset of it basically
<pinpoxIRC>
Ok, but I won't have one big window filling up the whole screen
<leon-p>
no, but something very similar
<leon-p>
wait, I can show you a screenshot ig you give me a minute
<pinpoxIRC>
I infered from that screenshot that this is how stacktile handles the layout, right?
<pinpoxIRC>
Pretty cool, idea <3
<leon-p>
yes, that's exactly it!
<leon-p>
I had that idea because I sometimes when writing code I go on a detour and open a new editor window. When you are like five detours deep, the non-main windows get a bit crammed. So I have a little overflow area that keeps them reasonable sized. Being able to use that layout for the entire screen is just a side-effect of stacktiles architecture
<pinpoxIRC>
Btw. I just thought about i3's "tabbed" layout and was wondering, are window decorations something that is possible in river?
<pinpoxIRC>
(not that I plan to use them, just wondering)
<leon-p>
not right now
<pinpoxIRC>
ok, i supposed
<pinpoxIRC>
With no generator running, river comes astonishingly close to being a normal/floating window manager. I bet if you had the bars on the windows you wouldnt even thing i can tile
<pinpoxIRC>
Anyway, thanks for the hint with the stacktaile layout. I'm excitid for the move of tags to the layout generator though
<leon-p>
that's intentional. river should be useful without a layout generator, f.e. when it crashes
<pinpoxIRC>
Was a blessing when playing with the lua code. I crashed it more than once :)
notzmv has joined #river
leopoldek has joined #river
<leon-p>
PSA for stacktile users: I removed the "per-tags" option and replaced it with the new "runtime-changes" option. Live layout adjustments can now be stored per-output, per-tag and per-dominant-tag. The last one is meant for people who often focus multiple tags and do not want their layout to get messed up when focusing an additional tag.