extern/nix-config
1
0
Fork 1
mirror of https://github.com/donovanglover/nix-config.git synced 2025-01-26 23:58:38 +01:00
Code Issues Packages Projects Releases Wiki Activity
e5d9de3946
nix-config/.config/wal/bspwm_and_dunst.sh

20 lines
540 B
Bash
Raw Normal View History

Switch from base16 to pywal pywal (also known as wal) lets us change color schemes with a cache directory instead of editing config files directly. This helps us separate the dotfiles from the color schemes. This commit removes explicit color settings from my dotfiles, which are now managed by pywal. Dunst has been added to show any notifications that I may want to use in the future. The colors.Xresources file is used to prevent urxvt from using a depth of 32. My custom colors.vim file has been removed in favor of wal.vim, which solves some problems I had to manually resolve myself and should make things easier to maintain in the long term. Note that pywal also supports base16 color schemes, as well as any other color scheme you can think of.
2018-10-12 20:37:34 +02:00
#!/bin/sh
# Source the colors from wal
source "${HOME}/.cache/wal/colors.sh"
Make post-wal commands conditional This commit makes the post-wal script a bit more aware of its environment. This is only to support Plasma with bspwm, which needs the bspwm settings but not the dunst settings. Since bspwm with KDE settings performs exceptionally well, I may drop Plasma with bspwm support altogether and revert this commit at a later date. The overhead of wmctrl and grep may not be worth it. Additionally, the filename should probably be changed to a more generic one in order to support more software as needed.
2018-10-15 15:22:19 +02:00
# Set the border colors if bspwm is running
if [ -n "$(wmctrl -m | grep 'bspwm')" ]; then
bspc config normal_border_color "$color1"
bspc config active_border_color "$color2"
bspc config focused_border_color "$color15"
bspc config presel_feedback_color "$color1"
fi
Switch from base16 to pywal pywal (also known as wal) lets us change color schemes with a cache directory instead of editing config files directly. This helps us separate the dotfiles from the color schemes. This commit removes explicit color settings from my dotfiles, which are now managed by pywal. Dunst has been added to show any notifications that I may want to use in the future. The colors.Xresources file is used to prevent urxvt from using a depth of 32. My custom colors.vim file has been removed in favor of wal.vim, which solves some problems I had to manually resolve myself and should make things easier to maintain in the long term. Note that pywal also supports base16 color schemes, as well as any other color scheme you can think of.
2018-10-12 20:37:34 +02:00
Make post-wal commands conditional This commit makes the post-wal script a bit more aware of its environment. This is only to support Plasma with bspwm, which needs the bspwm settings but not the dunst settings. Since bspwm with KDE settings performs exceptionally well, I may drop Plasma with bspwm support altogether and revert this commit at a later date. The overhead of wmctrl and grep may not be worth it. Additionally, the filename should probably be changed to a more generic one in order to support more software as needed.
2018-10-15 15:22:19 +02:00
# Restart dunst with the new color scheme, only if
# we're not using Plasma
if ! [ "$DESKTOP_SESSION" == "Plasma" ]; then
pkill dunst
dunst -conf "${HOME}/.cache/wal/dunstrc"
fi
Reference in New Issue Copy Permalink