sway/systemd/10-systemd

# should go to /etc/sway/config.d/10-systemd
#
exec systemctl --user import-environment
exec systemctl --user start sway-session.target
systemd --user support files * adds a sway-session.target that binds to graphical-session.target (see man systemd.special) * also adds a 10-systemd script that should (must?) be included from sway that starts imports the sway environment variables into the systemd --user instance, and then starts sway-session.target The idea is that, any --user units that are wanted by either sway-session.target or graphical-session.target will be started when sway runs, and will have the correct environment from sway too. 2019-01-21 23:56:52 +01:00			`# should go to /etc/sway/config.d/10-systemd`
			`#`
			`exec systemctl --user import-environment`
			`exec systemctl --user start sway-session.target`