Is it possible to use with non systemd system?

[a584-droid]

I have Artix with Dinit. I don't see the reason to use exclusively systemd service for the gui configuration. If you can band yeetmouse with sysvinit directory or whatever for use with every system. Like zapret2 does.

[AndyFilter]

Hey, I've never tried to install it on a non-systemd system. I use Ubuntu, and as such - my knowledge is limited to it. But the installation script does have a fallback when it doesn't detect systemd:

YeetMouse/install.sh

Lines 177 to 182 in ed4c939

	else
	echo "systemd not detected; installed driver and yeetmousectl, but did not enable a boot-time service."
	echo "To persist settings across reboot on this system, run:"
	echo " /usr/bin/yeetmousectl apply /etc/yeetmouse.conf"
	echo "from your init system's startup mechanism."
	fi

So, if everything does actually install correctly (check logs), then it should work. With one caveat that you'll have to enable persistent config on your own.

If - on the other hand - you have a non-systemd system and are willing to work on adding support for it, I can help you with the Yeetmouse side of things.

If I completely missed your question, than I'm sorry, I have no idea what "Artix", "Dinit" or "zapret2" are, and you're gonna have to explain it to me like to a Ubuntu user.

[a584-droid]

Hey, I don't get what did you do. It doesn't use config.h nor defaults.h (As I get it). It does use /etc/yeetmouse.conf but /etc/yeetmouse.conf uses defaults.h as the right file to get configuration from. It doesn't use config.h if was moved into Yeetmouse/driver in initial installation directory. gui program doesn't work with export and import - nothing happens.

[a584-droid]

And I gues somewhere in Artix's KDE an another system mouse acceleration is on that's why I have some kind of "reverberation" with it.

Anyway I don't like that you overcomplicate this program keeping instructions clearly as they were initially with few additions.
Please overshare then.

I don't think you should had add systemd service for reading config file at start. It was simply to Ctrl+R cd /Sources/Yeetmouse/gui and then type ./YeetMouseGui.

Why gui being accessible from anywhere in shell needs to have a systemd service with an unobvious configuration management and behaviour, to be applied?

Didn't there were any other workarounds?

[AndyFilter]

Hey, I don't get what did you do. It doesn't use config.h nor defaults.h (As I get it). It does use /etc/yeetmouse.conf but /etc/yeetmouse.conf uses defaults.h as the right file to get configuration from. It doesn't use config.h if was moved into Yeetmouse/driver in initial installation directory. gui program doesn't work with export and import - nothing happens.

I don't understand this. So I'll just say the following: defaults.h is not used during the runtime. The values are only read from there during the compilation. The default system configuration is pulled from this file: install_files/yeetmouse.conf.sample if everything goes according to plan, and this runs:

YeetMouse/install.sh

Lines 167 to 170 in ed4c939

	# Apply config immediately if present
	if [[ -f /etc/yeetmouse.conf ]]; then
	sudo /usr/bin/yeetmousectl apply /etc/yeetmouse.conf || true
	fi

And I gues somewhere in Artix's KDE an another system mouse acceleration is on that's why I have some kind of "reverberation" with it.

👍🏼

Anyway I don't like that you overcomplicate this program keeping instructions clearly as they were initially with few additions.
Please overshare then.

I have a brilliantly simple solution for you - use the program that you like using.

I don't think you should had add systemd service for reading config file at start.

I guess the first message wasn't enough. So let me expand the view.

"Since 2015, nearly all Linux distributions have adopted systemd."
~ Wikipedia

and

"Systemd is the dominant initialization (init) system in the Linux ecosystem, with an estimated 70% to over 90%"
~ Google search clanker

I'm sorry if you're using some niche Linux distribution, and it doesn't have systemd. I understand your frustration, but you have to consider that even though I've been working on this project for the past two years adding fixes and features that I personally will NEVER use, I can't - myself - add compatibility to systems that I don't have installed. That's just how things are - I can't write a non-systemd implementation push it, and hope that it works without testing it.
I have to depend on the work of insanely helpful people who also work absolutely for free to bring the compatibility to systems like NixOS. That's what I was asking of you earlier. There is nothing I can do about you not being able to run this on your own specific setup, unfortunately you'll have to figure it out on your own (or more likely now ask a clanker). And once you do, you can share your findings here as a PR so that people with similar setups to yours can fix their issues much faster. That's the reality of unpaid collaborative labour (OSS community).

Why gui being accessible from anywhere in shell needs to have a systemd service with an unobvious configuration management and behaviour, to be applied?

To be one-click install for majority of the users. And that very same majority of the users probably doesn't have the expertise required to manually fix problems when they occur, on the other hand - tech savy people (like you I assume) are every much able to tackle those problems and get the things working on their niche systems. Or at least that's my point of view.

Didn't there were any other workarounds?

Pretty sure I sent you the "workaround" in my first message. I unfortunately can't remotely log into your computer, install the software, fix everything and then leave. They don't pay me enough (the don't pay me at all...).

To answer the question again - you just have to make sure you apply the config (manually or otherwise) on boot. It's up to you how you do it, but you can base it on how it's done on systemd systems.

[OzymandiasUK]

I'm not really sure what OP is trying to get at here, the program works with non-systemd distros. I currently use Artix on OpenRC and it works fine. If you're referring to applying the config on startup, for me that hasn't been specifically and issue with systemd or non-systemd, but rather what I suspect to be an issue with wayland. When I first started using yeetmouse I was using CachyOS, which uses systemd, but the "Apply + Save" option didn't work. It was greyed out when I ran it as a normal user, and didn't persist across reboot when used as sudo. However I recently switched to Artix on OpenRC, I use KDE Plasma and I tried using the X11 version and when I used the "apply + save" option it persisted between reboots, however because I had other issues with X11 I switched back to wayland and "apply + save" no longer worked as intended. It also didn't work on CachyOS when I used wayland Plasma then either, though I never tried X11 Plasma on CachyOS.

I'd suggest trying to use an X11 DE/WM, or just get used to opening yeetmouse every boot and applying a saved config file, that's what I do and I only have to do it when I restart which isn't too often.