vincentbernat.i3wm-configur.../systemd/misc-x@.service

[Unit]
Description=Miscellaneous settings for X11 on %I
PartOf=graphical-session@%i.target

[Service]
Environment=DISPLAY=%I
ExecStart=/usr/bin/xset -b
ExecStart=/usr/bin/numlockx on
Type=oneshot
RemainAfterExit=false
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=Miscellaneous settings for X11 on %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`

			`[Service]`
			`Environment=DISPLAY=%I`
			`ExecStart=/usr/bin/xset -b`
systemd: fix location of numlockx 2020-01-19 22:45:33 +01:00			`ExecStart=/usr/bin/numlockx on`
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			`Type=oneshot`
			`RemainAfterExit=false`