README (1668B)
1 dotfiles 2 ----- 3 4 my most recent dotfiles 5 contains configs for both my desktop and laptop. 6 7 usage 8 ----- 9 10 requires gnu stow 11 ./deploy [laptop|desktop] 12 13 how it works 14 ----- 15 16 sway's config allows the use of includes so i utilize that to maintain a master config 17 as well as seperate hardware configs located in the device-specific folder. the deploy script 18 will create the proper symlinks allowing me to easily edit my compositors config without 19 having to worry if something will break on different hardware. 20 21 similiar to sway my dwl config separates the hardware configs for ease of portability. 22 the 'dwl-hardware.h' from the device-specific folder is symlinked to the dwl dir as 'device.h'. 23 note that dwlb also includes 'device.h' in order to share font settings between the compositor 24 and the bar. i feel that will be useful if i ever need to spawn other programs with the same 25 font. but mainly i didn't want to symlink the same file twice ... it seemed "messier". 26 27 the river config is very similiar to sway as it justs symlinks a file based on the deployed device 28 and sources it in the main river init script. i want to explore writing the river config in something 29 more interesting than a shell script. 30 31 symlinks are also utilized for the i3status, and emacs configs. 32 33 the foot and sakura config is a bit more interesting as i dont want to maintain different configs for 34 different hardware. there are master templates located in the ./shared-configs/ directory 35 that have markers {FOOT_FONT} and {SAKURA_FONT} that are replaced with appropiate font in the deploy script. 36 37 maybe its better to just maintain seperate dotfiles for each device but this seemed like more fun :)