02:27 <Jesu79> Hi! I'm trying to activate tap-to-click action on my laptop. riverctl list-inputs says that my touchpad is "pointer-2-7-SynPS/2_Synaptics_Touchpad". So I added this line to init: riverctl input pointer-2-7-SynPS/2_Synaptics_Touchpad tap enabled. However it doesn't seem to work. Is what I did correct or should I do it differently?

02:32 <Jesu79> Hmm, when i run riverctl list-input-configs it says tap enabled for the touchpad.

08:10 <TheAnachron> hello, does river support multiple displays already or is that still a todo?

08:11 <ifreund> it's supported multiple displays since before the first release :)

08:13 <TheAnachron> I mean monitor based tags?

08:14 <TheAnachron> For example: I go to monitor A, have tag 1 and 2 open there. Go to B and toggle tag 2 and it shows on B now and A only shows 1.

08:16 <TheAnachron> Also, how do river friends use river on multiple displays? Is there an example/workflow blog post/video somewhere? I daily drive it on a single monitor but think about getting a second one.

08:16 <ifreund> no, tags are not shared across outputs

08:17 <ifreund> #1100 will push tags outside of the compositor process eventually though and allow wms to do whatever they want there

08:28 <TheAnachron> Wait, so every output currently has its own tags?

08:28 <TheAnachron> how do I move my cursor to a specific monitor?

08:39 <ifreund> just move it out of your current monitor to an adjacent one?

08:51 <Nickli> Super , or . is the default i believe

08:56 <TheAnachron> Nickli but that sends the view to the next/prev output.

08:57 <TheAnachron> ifreund there is no command to send mouse to display (with name X/next/prev)?

08:57 <LarstiQ> there is

08:57 <LarstiQ> focus-output

08:58 <TheAnachron> Wow. How did I miss that.

08:58 <TheAnachron> Thanks!

08:58 <ifreund> TheAnachron: it only moves your cursor if you have cursor warp configured

08:59 <TheAnachron> I think I want to use cursor-warp on-focus-change in the future, so that makes sense. Thanks again! Sorry for the stupid question

10:11 <TheAnachron> novakane zelbar does not currently support displaying the same bar on multiple monitors?

10:16 <__toor__> Do I need xdg-desktop-portal AND xdg-desktop-portal-wlr to enable screen sharing?

10:17 <__toor__> specifically, to share screen via slack.com web application in firefox

10:18 <ifreund> yes

10:21 <__toor__> ok, thank you!

10:39 <novakane> TheAnachron: nope, well you could launch 2 bars with the same script and just change the output selected

10:41 <TheAnachron> would I need to handle output changing?

10:42 <TheAnachron> Or would zelbar just silently stop displaying a bar which output does not exist?

10:45 <novakane> you can chose an output to display the bar with the -o flag then it doesn't change anything else between both bars, and yes if there is no output the bar is destroyed

10:46 <TheAnachron> and the process finishes? Or just silently hides the bar?

10:47 <novakane> it should finish

10:48 <novakane> or maybe it goes on an other monitor if one exists, I don't remember what I did when I tried multiple monitors xD

10:52 <TheAnachron> okay, so I would need a service for each monitor.

10:53 <TheAnachron> I could then use kanshi to execute start/stop on services when output changes. :)

12:27 <TheAnachron> Welp, if I get a 2nd monitor I need to rethink my workflow and key bindings. :D

18:38 <lordmzte> How can I check if a surface is XWayland, or native wayland?

18:57 <novakane> lordmzte: xeyes is a fun and quick way to test

18:59 <lordmzte> haha neat