14:26 <msiedlaczekelsh4> hey, is it possible to somehow use lswt with bemenu/wofi to go to a specific window? that is search for a window, select it, and, say, toggle its tag and make it active? (I mean if it's possible with existing tools)

14:30 <ifreund> msiedlaczekelsh4: I believe lswt only allows printing information about toplevels not activating them currently.

14:30 <ifreund> the only CLI foreign toplevel management client I'm aware of that allows activation is the wlroots example client

14:31 <ifreund> https://github.com/swaywm/wlroots/blob/master/examples/foreign-toplevel.c

14:34 <msiedlaczekelsh4> ifreund: thanks, I'll give it a look

14:35 <leon-p> msiedlaczekelsh4: the problem with that `lswt | menu | progra-to-focus-window` pipeline is that there is no way to identify unique windows across wayland connections. You need to stay on a single connection, otherwise the window switcher will completely break if two or more windows share app-id and title.

14:39 <leon-p> until there are unique identifiers for windows, you can basically forget any pipeline based approach

14:49 <ifreund> well, you can use object ids and just ignore the race condition :P

15:07 <msiedlaczekelsh4> leon-p: I understand; out of curiosity, are these unique ids coming or not likely?

15:07 <msiedlaczekelsh4> also is that something lacking in wayland or river?

15:15 <novakane> msiedlaczekelsh4: there is an open issue for this so maybe https://github.com/ifreund/river/issues/428

15:17 <novakane> what if with the foreign toplevel protocol you make like an array with each app-id corresponding to the array index and you would focus the index, would that works for app with same app-id?

15:28 <leon-p> novakane: it would break as soon as windows were destroyed and new ones added

15:31 <leon-p> msiedlaczekelsh4: Wayland has no concept of "windows" at all, so the fault, if you want to call it one, lies either with the xdg-shell or the foreign toplevel protocol. But TBH I am not blaming anyone for not thinking about this use case.

15:33 <novakane> leon-p: it wouldn't be ideal but you could update the array each time a view map/unmap no?

15:34 <leon-p> novakane: but then old indexes get stale.

15:35 <leon-p> you need to guarantee that an index always points to a specific window and does not get re-used. And at that point you have unique IDs

15:36 <novakane> ah right

15:40 <msiedlaczekelsh4> thanks, obviously not looking to blame anyone, just trying to understand a little better ;)

17:56 <ecocode__> How does sway solve this?

18:02 <msiedlaczekelsh4> do they solve it? can you do that in sway?

18:11 <leon-p> sway implements i3 IPC protocol, which AFAIK has a unique ID for each window

18:11 <leon-p> ecocode__ msiedlaczekelsh4 ^

18:17 <ecocode__> swayr: An urgent-first/LRU window switcher for sway (https://sr.ht/~tsdh/swayr/)

18:20 <msiedlaczekelsh4> interesting. this was more or less what I was thinking of. I'm not sure if I would be using it much, but sometimes I know I opened some app somewhere, and would like to locate it quickly, and this would be nice to have. but for the most part I know which tags are used for what, so it's not that useful

18:22 <msiedlaczekelsh4> do any of you have a rough idea of how large sway community is relative to river? I imagine more people are working on that (not to mention it's been developed longer)

18:22 <leon-p> a window switcher menu for river is not impossible, you just need to keep it all to a single wayland conncetion, meaning all in a single program

18:25 <msiedlaczekelsh4> leon-p: right; I'd hack a quick bash script for that if it were possible, but I'm not motivated enough to learn wayland currently ;) sounds like a cool educational project, so maybe will look into it once have more spare time

18:31 <leon-p> msiedlaczekelsh4: well, pretty sure bash can connect to sockets, so... :P

18:31 <msiedlaczekelsh4> touche

18:31 <msiedlaczekelsh4> though it would be anything but quick hack I'm afraid :)