00:27 <rrix> could anyone provide guidance on running an onscreen keyboard like squeekboard within river?

00:28 <rrix> what other scaffold services are necessary? "nix run nixpkgs#squeekboard" reports some warnings that make me think I need to enable some more GNOME crap to get it to work, but i'd like to avoid pulling more of that stuff in if possible, perhaps someone could recommend another OSK, especially if it can be taught how to control river itself…

00:28 <rrix> > Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop

00:28 <rrix> > Could not register to session manager: Cannot invoke method; proxy is for the well-known name org.gnome.SessionManager without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag

00:29 <rrix> i have no idea how much of a "warning" those are rather than blocking errors…

00:32 <rrix> and ofc if anyone has any helper scripts for "riverctl map-switch tablet" that would be neat :)

00:36 <rrix> oh it was gsettings crap… rubber ducked myself!

00:36 <rrix> "gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true" from a 2 year old reddit thread

05:24 <rrix> i think i was confused/baffled before because squeekboard works when i run it in from within a gtk app like an emacs shell-mode but not a qt app or from river/systemd directly because of how nixos packages gnome/gtk apps to work with XDG_DATA_DIRS, nothing at all related to river or wayland … cheers

05:58 <leon-p> __toor__: I am reasonably sure most river users do make use of tags, I certainly do (although the ability to assign multiple tags to windows or activate multiple tags at once I basically never use)

06:00 <leon-p> __toor__: you could try a river layout that assigns the full size of the output to all windows. then you could use the next/prev focus commands to cycle through windows without having to remember the exact tag for each window

07:49 <NickH> __toor__: Yes, it sounds like what some people call a "monocle" layout. See https://codeberg.org/river/wiki/src/branch/master/pages/Community-Layouts.md

08:32 <Nickli> an option would be to use something like rofi/dmenu to send a window somewhere

08:46 <leon-p> that's not possible on river right now unfortunately

08:48 <Nickli> what prevents a script from using riverctl... ?

08:51 <ifreund> riverctl commands pretty much all act on the currently focused window

08:51 <ifreund> which makes non-interactive usage quite racy

08:53 <Nickli> i wasnt even thinking about having it point itself to $somewindow and move it to a tag

08:54 <Nickli> were still on premise i have this window focused, open up the launcher and have it move

08:55 <ifreund> sure, I don't think I understand why one wouldn't use a keybind to do that though

09:02 <Nickli> yeah it would be rare occasion usage

13:16 <Guest36> hi guys

13:18 <Guest36> i couldnt find much of anything about this online or in the manual so here is my issue

13:18 <Guest36> floating windows always get focused if the mouse has hovered over them, even if there is a floating window which should have focus instead

13:19 <Guest36> its hard to explain so heres an example:

13:21 <Guest36> i open an app floating and then go to the about page, which is usually also a floating window. as long as my mouse stays inside of the about window things are fine, but as soon as my mouse leaves the about window and goes into the window of the app, the about window is behind the main window and i cant access it anymore, i then have to move the

13:21 <Guest36> main window away

13:22 <Guest36> which is also sometimes difficult/almost impossible because i cant seem to be able to move windows past the bounds of the "compositor window"

13:22 <Guest36> are there settings for these two things"

13:24 <ifreund> Guest36: riverctl focus-follows-cursor disabled

13:26 <Guest36> thank you

13:27 <Guest36> although that disables cursor following completely sadly

13:27 <Guest36> and "normal" still has the issue

18:40 <mekeor> hello. i just plugged in another display output (beamer). how do make both my outputs show the same picture?

18:42 <vyivel> mekeor: maybe with https://github.com/Ferdi265/wl-mirror

18:45 <szgy> I wonder if setting the same screen 'coordinates' on kanshi for two outputs would mirror them? (I would say no...)

18:46 <mekeor> vyivel: huh, interesting. i was expecting something simple :D especially, i wasn't expecting a "view" on one output to show the content of the second output :D

18:48 <mekeor> there's this: https://github.com/cyclopsian/wdisplays

18:55 <mekeor> well, kanshi at least makes two monitors work :D

18:56 <mekeor> let's see how to mirror them :)

19:13 <mekeor> for the record: emersion pointed me to this issue: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/issues/101