I complete agree with your stance on ffm. FFM is totally ingrained into my work flows/habits since I started witn Unix in the 80s. Was my biggest initial peeve with Wayland. For a bunch of reasons I have mostly bailed on Wayland and have gone back to X11 while things stabilize/improve, so am not positive the instructions work with the current Wayland, in a fully updated Bookworm. Will take a look tonight and ensure that it still works.{rpi5/bookworm 64} Thank you for the clear simple steps, however... apparently I am even simpler.1. Download the extra plugins from https://voidlinux.pkgs.org/current/void ... .xbps.html
2. Find the plugin "libfollow-focus.so" and put it in /usr/lib/aarch64-linux-gnu/wayfire/
3. Find the config file "follow-focus.xml" and put it in /usr/share/wayfire/metadata/
4. Add "follow-focus" to the plugins list in /etc/wayfire/defaults.ini
5. Configure your usage of the plugin via changes to ~/.configs/wayfire.iniBasically you are avoiding having to compile the extra plugins, since focus-follows-mouse for some daft reason is not included in the base set of plugins. Downloading a precompiled set and then just harvesting the 2 files is easier than setting up a build environment and potentially breaking Wayfire entirely. Step 1 gets you the compiled files, steps 2 & 3 "install them" in the required place, step 4 enables the plugin and step 5 configures it.Code:
# config ffm - with no window raise[follow-focus]change_output=truechange_view=truefocus_delay=50raise_on_top=falsethreshold=10
I obtained the xbps file, extracted the .so & .xml you specify & copied them into the dirs you specify. Permissions match the previous inhabitants. I add the plugin name to /etc/wayfire/defaults.ini. I append the specified lines to the ~/.config/wayfire.ini file (note: not /.config_s_). Reboot. But I don't get the expected behavior & I don't find any new config controls added anywhere to enable the fnx.
What am I doing wrong?
(And why is this even a thing? I've used focus follows mouse for 30 years!)
Once I made the changes and rebooted ffm just worked. I am wondering if there is a version issue, since Wayland has had updates, and you are "harvesting" the required files from a different Wayland build. The versions matched & worked together when I originally did it. There are no new controls added anywhere, other than the plugin being available and configurable via wayfire.ini. If done right you should get the desired behaviour. If done wrong it tends to crash Wayfire which takes you back to a login prompt. I crashed Wayfire a lot when I was first mucking about with it.
The other alternative is download and build the optional plugin set. I made an attempt at that and getting the build system setup is not particularly trivial. Finding a precompiled build, with the right version and extracting the files is likely much simpler.
Statistics: Posted by bjtheone — Thu Jun 27, 2024 1:19 pm