dotfiles/bin/executable_autostart

#!/usr/bin/env bash

systemctl --user import-environment WAYLAND_DISPLAY DISPLAY PATH

systemctl --user start gnome-keyring.service
systemctl --user start graphical-session.target

dbus-sway-environment
configure-gtk
thinkpad-dock

swaymsg workspace "4 "
swaymsg exec -- "emacsclient --create-frame -e '(org-agenda-list)'"
sleep 0.5
swaymsg workspace "2 "
swaymsg exec browser
sleep 2
swaymsg workspace "5 "
swaymsg exec foot -- bash -c "~/bin/somafm-picker"
sleep 0.3
swaymsg workspace "1 "
swaymsg exec foot
sleep 0.3
swaymsg workspace "3 "
swaymsg layout tabbed
swaymsg exec start-comms
[nix] Extract path changes from bin/ 2021-03-08 14:54:42 +01:00			`#!/usr/bin/env bash`
[bin] Get rid of no-longer used i3 switches & ifs 2020-02-22 18:51:41 +01:00
[bin] Re-Import WAYLAND_DISPLAY, DISPLAY and PATH upon start 2022-07-29 23:21:45 +02:00			`systemctl --user import-environment WAYLAND_DISPLAY DISPLAY PATH`

[bin] Clean up autostart to no longer include dbus hullabaloo 2022-06-09 08:26:10 +02:00			`systemctl --user start gnome-keyring.service`
[sway] Add both graphical-targets (-pre) to the autostart This should resolve my long running gripe with `gnome-keyring` not starting in time for the nextcloud-client to actually pick up the correct keyring. 2022-05-10 10:35:55 +02:00			`systemctl --user start graphical-session.target`
[bin] Rework autostart to accommodate dbus activation and clipman 2020-10-07 09:02:10 +02:00
[sway] Revert back to plain ol stable 22.11 with proper GL 2023-04-17 17:08:20 +02:00			`dbus-sway-environment`
			`configure-gtk`
[bin] Let the autostart script run thinkpad-dock as well 2023-05-05 21:44:24 +02:00			`thinkpad-dock`
[sway] Revert back to plain ol stable 22.11 with proper GL 2023-04-17 17:08:20 +02:00
[bin] Adapt autostart to new font symbols 2021-01-11 17:16:44 +01:00			`swaymsg workspace "4 "`
[bin] Clean up autostart to no longer include dbus hullabaloo 2022-06-09 08:26:10 +02:00			`swaymsg exec -- "emacsclient --create-frame -e '(org-agenda-list)'"`
[sway] Wait between start commands and auto-layout messaging screen 2020-03-26 13:06:29 +01:00			`sleep 0.5`
[bin] Adapt autostart to new font symbols 2021-01-11 17:16:44 +01:00			`swaymsg workspace "2 "`
[bin] Fix autostart to be less noisy on start 2022-02-11 20:05:17 +01:00			`swaymsg exec browser`
[bin] Rework autostart to accommodate dbus activation and clipman 2020-10-07 09:02:10 +02:00			`sleep 2`
[bin] Adapt autostart to new font symbols 2021-01-11 17:16:44 +01:00			`swaymsg workspace "5 "`
[sway] Fix sway startup to only keep gnome-keyring and nextcloud-client 2022-04-04 11:26:30 +02:00			`swaymsg exec foot -- bash -c "~/bin/somafm-picker"`
[bin] Rework autostart to accommodate dbus activation and clipman 2020-10-07 09:02:10 +02:00			`sleep 0.3`
[bin] Fix autostart terminal icon 2021-01-22 12:29:06 +01:00			`swaymsg workspace "1 "`
[terminal] Take `foot` terminal for a spin I've been seeing a lot of glitches with Alacritty since a few weeks now, especially when starting and resizing. Foot seems nice and quick. 2021-07-15 00:43:20 +02:00			`swaymsg exec foot`
[bin] Rework autostart to accommodate dbus activation and clipman 2020-10-07 09:02:10 +02:00			`sleep 0.3`
[bin] Adapt autostart to new font symbols 2021-01-11 17:16:44 +01:00			`swaymsg workspace "3 "`
[sway] Wait between start commands and auto-layout messaging screen 2020-03-26 13:06:29 +01:00			`swaymsg layout tabbed`
			`swaymsg exec start-comms`