dotfiles/services/.config/systemd/user/dropdown-terminal.service

[Unit]
Description=Alacritty window hidden on i3 scratchpad
After=display-manager.service

[Service]
Type=simple
# workaround to allow relative executable invocation (i.e. current users' home dir)
ExecStart=/bin/bash -c 'alacritty --title "dropdown-terminal" --class Alacritty,scratchpad'
Restart=always
RestartSec=2

[Install]
WantedBy=default.target
services: Add autostarting dropdown-terminal 2020-07-29 07:21:46 +00:00			`[Unit]`
			`Description=Alacritty window hidden on i3 scratchpad`
services: Fix flashfocus startup Flashfocus did not start up correctly since it was not required for the `default.target` which is the only (?) valid target when systemd operates in user-mode. Instead of overwriting just part of the flashfocus service file, and subsequently having it enabled for default.target and a non-existent graphical.target user environment, we overwrite the whole file and set it to `default.target`. Additionally, the service should be restarted when it fails and slow down on its restart attempts (I kept 5 seconds for this one, since it is not as time critical as others -- no one cares if windows only flash 5 seconds after starting the machine.) Added (wishful) After components to many service units, in case I figure out one day how to make a useful target for the systemd user mode. 2020-09-21 07:07:38 +00:00			`After=display-manager.service`
services: Add autostarting dropdown-terminal 2020-07-29 07:21:46 +00:00
			`[Service]`
			`Type=simple`
			`# workaround to allow relative executable invocation (i.e. current users' home dir)`
			`ExecStart=/bin/bash -c 'alacritty --title "dropdown-terminal" --class Alacritty,scratchpad'`
			`Restart=always`
services: Lower restart time to 2 seconds Main issue the restart delay fixes is that services don't wait for X to be ready on startup (which is bad if the application being started requires X being ready to actually work.) I have still not found a way to work around waiting for X being ready other then the ugly delay hack (for systemd --user modules at least). However, the delay can be --- in most cases --- smaller than 5 seconds. All my machines start reasonably fast and have X up and running from pressing login to staring at the wallpaper in a couple seconds at most. If services don't start correctly and the error is X not being ready, increase the startup delay once again. 2020-09-12 15:37:43 +00:00			`RestartSec=2`
services: Add autostarting dropdown-terminal 2020-07-29 07:21:46 +00:00
			`[Install]`
			`WantedBy=default.target`