1
0
forked from extern/nix-config
Commit Graph

7 Commits

Author SHA1 Message Date
Donovan Glover
93d7d54e76
dunst: Remove old shortcuts setting
This was removed in dunst 1.7.0.
2022-03-11 09:22:05 -05:00
Donovan Glover
1607d886b6
meta: Use normal dpi settings for now
Since the device we're using is normal DPI, we have to manually adjust
these two values. Note that the rest of the setup is mostly automated
when it comes to determining the size of things.
2021-11-15 12:55:40 -05:00
Donovan Glover
180f676bc8
Revert "Remove dunst"
I actually switch between bspwm, sway, and other desktop environments
depending on how I feel now, and use dunst for bspwm.
2021-11-14 11:27:28 -05:00
Donovan Glover
0662befeb2
Remove dunst
dunst actually has Wayland support but I'd like to try something else
for now, possibly something more "sway-like".
2021-05-12 20:25:40 -04:00
Donovan Glover
1c44cd55f6
wal: Modularize done.sh
Instead of trying to do everything at once, done.sh will instead call
other scripts for each individual program that needs to be manipulated.
2018-11-19 20:12:22 -05:00
Donovan Glover
5c04a58082
docs: Add READMEs for compton, dunst, and zathura
Since my dotfiles are now sorted by individual programs instead of in
groups, I'm trying a new README format. This format should provide more
useful information and be easier to read as well.
2018-11-18 13:27:37 -05:00
Donovan Glover
c4b7b69f66
stow: Split bspwm into separate packages
It turns out that placing similar config files (i.e. bspwm-related) in
the same directory is not the way to go about handling dotfiles since
each config file (or dotfile) *should* manipulate only a single program.

This was not the case back when I used urxvt (which would require the
old method of .Xresources), but now that I understand more about how
*modern* dotfiles work (with $XDG_CONFIG_HOME), separating dotfiles by
program became the obvious choice.
2018-11-17 14:58:13 -05:00