vincentbernat.i3wm-configur.../systemd/awesome@.service

[Unit]
Description=Awesome window manager for %I
PartOf=graphical-session@%i.target
After=autorandr@%i.service
After=compton@%i.service
After=xsettingsd@%i.service
After=tmux.service
Before=nm-applet@%i.service

[Service]
Environment=DISPLAY=%I
ExecStart=/usr/bin/awesome
ExecStopPost=/bin/systemctl --user stop graphical-session@%i.target
Restart=on-failure
systemd: tentative to manage session with systemd To me, I think it was cleaner to have a parameter with the current display. This way, the session is specific to the current display. It seems BindsTo doesn't think this way. 2020-01-19 18:36:36 +01:00			`[Unit]`
systemd: create our own graphical-session@.target graphical-session.target is an existing target for the system. While I don't use several X sessions, I prefer to have each service bound to the right display and therefore, I create my own graphical-session@.target for this purpose. Also, I don't like having to use `systemctl --user enable`, so I enable everything directly in graphical-session@.target. Other dependencies are ordered from awesome@.service. This seems good enough. 2020-01-19 20:28:04 +01:00			`Description=Awesome window manager for %I`
systemd: tentative to manage session with systemd To me, I think it was cleaner to have a parameter with the current display. This way, the session is specific to the current display. It seems BindsTo doesn't think this way. 2020-01-19 18:36:36 +01:00			`PartOf=graphical-session@%i.target`
systemd: create our own graphical-session@.target graphical-session.target is an existing target for the system. While I don't use several X sessions, I prefer to have each service bound to the right display and therefore, I create my own graphical-session@.target for this purpose. Also, I don't like having to use `systemctl --user enable`, so I enable everything directly in graphical-session@.target. Other dependencies are ordered from awesome@.service. This seems good enough. 2020-01-19 20:28:04 +01:00			`After=autorandr@%i.service`
			`After=compton@%i.service`
			`After=xsettingsd@%i.service`
systemd: use systemd to start tmux server 2020-01-29 05:45:38 +01:00			`After=tmux.service`
systemd: create our own graphical-session@.target graphical-session.target is an existing target for the system. While I don't use several X sessions, I prefer to have each service bound to the right display and therefore, I create my own graphical-session@.target for this purpose. Also, I don't like having to use `systemctl --user enable`, so I enable everything directly in graphical-session@.target. Other dependencies are ordered from awesome@.service. This seems good enough. 2020-01-19 20:28:04 +01:00			`Before=nm-applet@%i.service`
systemd: tentative to manage session with systemd To me, I think it was cleaner to have a parameter with the current display. This way, the session is specific to the current display. It seems BindsTo doesn't think this way. 2020-01-19 18:36:36 +01:00
			`[Service]`
			`Environment=DISPLAY=%I`
			`ExecStart=/usr/bin/awesome`
			`ExecStopPost=/bin/systemctl --user stop graphical-session@%i.target`
			`Restart=on-failure`