You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every effort which wants to make sway part of the end user-friendly solution (be it openSUSEway or MicroOS-based efforts like Greybeard/Moldavite) ends up requiring a shell script, which sets up the environment for running sway, see for example openSUSEway’s sway-run.sh or Moldavite’s sway.sh.
Wouldn’t it be better to put such script into the plain sway package (and/or eventually send it upstream)?
The text was updated successfully, but these errors were encountered:
On Thu Feb 1, 2024 at 12:13 PM CET, Krish Jain wrote:
Absolutely @denisok . Making it a systemd service seems like the best option. Systemd has a lot of nice features :)
(*tongue-in-cheek* except when one is an idiot and breaks dbus
user session, and doesn’t know how to fix it; which is my
situation right now)
Every effort which wants to make sway part of the end user-friendly solution (be it openSUSEway or MicroOS-based efforts like Greybeard/Moldavite) ends up requiring a shell script, which sets up the environment for running sway, see for example openSUSEway’s
sway-run.sh
or Moldavite’ssway.sh
.Wouldn’t it be better to put such script into the plain sway package (and/or eventually send it upstream)?
The text was updated successfully, but these errors were encountered: