1
0
forked from extern/nix-config
donovanglover-nix-config/.config/wal/done.sh
Donovan Glover f19dc21649
Use symlinks with pywal templates
Instead of manually changing every instance where a program could run to
use the config in the cache directory, and instead of copying files
every time pywal is updated, it makes sense to create symbolic links for
these files instead.

This ensures that the right settings are used even without knowing the
passed parameters.
2018-10-18 11:16:15 -04:00

37 lines
1.0 KiB
Bash

#!/bin/sh
# ===================
# ====== bspwm ======
# ===================
# Source the colors from wal
source "${HOME}/.cache/wal/colors.sh"
# Set the border colors
bspc config normal_border_color "$color1"
bspc config active_border_color "$color2"
bspc config focused_border_color "$color15"
bspc config presel_feedback_color "$color1"
# =================================================
# Symlink config files so programs can be started
# without referencing the cache directly
#
# Includes: zathura, termite, dunst
# =================================================
mkdir -p "${HOME}/.config/zathura"
mkdir -p "${HOME}/.config/termite"
mkdir -p "${HOME}/.config/dunst"
ln -sf "${HOME}/.cache/wal/zathurarc" "${HOME}/.config/zathura/zathurarc"
ln -sf "${HOME}/.cache/wal/termite" "${HOME}/.config/termite/config"
ln -sf "${HOME}/.cache/wal/dunstrc" "${HOME}/.config/dunst/dunstrc"
# ===================
# ====== dunst ======
# ===================
# Restart dunst with the new color scheme
pkill dunst
dunst &